Use BILL webhooks to subscribe to and receive real time notifications for events, such as create a vendor, update a bill, or create a payment. When you get the events catalog and create subscriptions, set the required header values based on the events you want to subscribe to.
| Event | Header values |
|---|---|
| Organization-level AP & AR events | devKey and sessionId |
| Partner-level AP & AR events | appKey and sessionId |
| Spend & Expense events | apiToken |
In your Create a subscription (POST /v3/spend/subscriptions) request, the X-Idempotent-Key header value must be in the UUID4 format. In addition, you can use an online service for generating a test notificationUrl value. For example, webhook.site.
fundingAddSuccess event is emitted when the user successfully adds a new funding payment method. We have added the defaultBilling field to the bankData payload. This field is set as true if the bank account is set a default for billing and payments.{
bankData: {
status: string;
accountNumber: string;
userVerificationRequired: boolean;
id: string;
nameOnAccount: string;
defaultBilling: boolean;
}
}We have replaced overlay spinners with loading buttons across all the widget screens. This is a user experience improvement.
We have introduced a new feature for accepting or rejecting a Spend & Expense transaction in response to a 3D Secure challenge triggered to verify the identity of the cardholder.
We have updated the webhooks events catalog to include the spend.three-ds-challenge.created event. Notifications are triggered for this event when a 3D Secure challenge is triggered for a Spend & Expense transaction. You can now set up subscriptions to receive notifications for the new event.
See Spend & Expense 3D Secure challenge notification payload for more information.
We have a new API endpoint for responding to 3D Secure challenges for Spend & Expense transactions. With the Accept or reject a transaction (POST /v3/spend/transactions/{acsTransactionId}/3ds-challenge) request, you can respond to a webhook notification you receive when a 3D Secure challenge is generated for a transaction.
See POST /v3/spend/transactions/{acsTransactionId}/3ds-challenge in the API reference for more information.
The BILL v3 API Postman collection is another way for you to test with the BILL v3 API. Simply fork the collection from the Postman API Network and begin testing with different BILL v3 API workflows.
See BILL v3 API Postman collection for more information.
BILL v3 API Postman collection
In the Record AP payment endpoint, we have introduced the capability of adding vendor credits. In the Record AP payment (POST /v3/bills/record-payment) request, you can now add vendor credits in the vendorCredits object.
| Field | Description |
|---|---|
id | BILL-generated ID of the vendor credit applied to the bill payment. The value begins with vcr. |
amount | Credit amount |
See POST /v3/bills/record-payment in the API reference for more information.
The Add vendor widget enables users to add and manage vendors in the organization. With saved vendor information and vendor bank account information, users can pay vendors and bills. Users can also add and manage international vendors with this widget.
The Add vendor widget provides a set of features.
Feature | Description |
|---|---|
Vendor management | Add and manage (edit or delete) vendor information in the organization. This includes international vendors. When a user enters vendor information, BILL searches the entire BILL network for the vendor and provides the list of vendors that match. When the user selects a vendor from the list of results, BILL saves the selected vendor in the organization. In addition, BILL automatically enables payments from the user to the vendor. Optionally, the user can manually add a vendor. |
Vendor bank account management | When the user manually adds a new vendor, a vendor bank account is required for enabling electronic payments from the user to the vendor. The user can add a new vendor bank account information for a new vendor or for an existing vendor. BILL takes up to 2 business days to verify the added vendor bank account before enabling payments to the vendor bank account. |
Vendor search | The user can search for vendors from the list of vendors added in the organization. A set of filters are available in the widget for search. |
In the bills API endpoints, we have introduced the purchaseOrderNumber field. You can now set this field as a purchase order number linked with the bill.
See POST /v3/bills in the API reference for more information.
The vendor webhook notifications now include the shortName field. This field is the vendor short name. When you receive notifications for the vendor.created, vendor.updated, vendor.archived, or vendor.restored events, the notifications now include the shortName field.
See Vendor notification payloads for more information.
The bill webhook notifications now include the purchaseOrderNumber field. This field is the purchase order number linked with the bill. When you receive notifications for the bill.created, bill.updated, bill.archived, or bill.restored events, the notifications now include the purchaseOrderNumber field.
See Bill notification payloads for more information.
On the MFA setup screen, when the user enters and international (not US) phone number and selects Voice call to receive a verification code, we have ensured that the correct information banner is displayed on the screen.