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.
In February 2025, BILL introduced UUIDs in the Spend & Expense API for further improving its security standards. All API responses include both id and uuid values.
As of July 9, 2025, the Spend & Expense id values are being deprecated. Both id and uuid values will continue to be available in all API responses. We strongly recommend that you use uuid instead of id in all your Spend & Expense API operations.
BILL maintains an event history for each subscription. We have now upgraded the webhooks TTL from 90 days to 180 days. You can get the list of event notifications sent to you for a subscription with GET /v3/events/subscription/{subscription_id}. You can now get the list of events for the last 180 days.
See Webhook API notification rules for more information about the complete set of rules.
We have added the capability for filtering event notifications by an entity ID. For example, to get notifications for a specific bill, you can now filter with the ID of the bill.
In the Get list of event notifications (GET /v3/events/subscription/{subscription_id}) request, you can now filter event notifications with the entityId field.
| Field | Description |
|---|---|
entityId | BILL-generated ID of the entity, such as bill or vendor. For example, to filter notifications by a specific bill, set this value as the ID of the bill. |
See GET /v3/events/subscription/{subscriptionId} in the API reference for more information.
We have introduced a set of API endpoints for getting billing statement information for an organization. BILL generates a monthly billing invoice statement for all the billing activities in the organization.
| Operation | API endpoint |
|---|---|
| Get list of billing statements | GET /v3/organizations/{organizationId}/billing-statements |
| Get billing statement details | GET /v3/organizations/{organizationId}/billing-statements/{billingStatementId} |
See Organization billing statements for more information.
We have introduced a new API endpoint for recording an AP payment.
You can now record a bill payment made outside your BILL system. You can apply the recorded payment amount to one or more bills for a vendor.
| Operation | API endpoint |
|---|---|
| Record AP payment | POST /v3/bills/record-payment |
See Record AP payments for more information.
