In the Guides section documentation for creating an international vendor, we learned that there was a need for further explaining the use of paymentPurpose and regulatoryFields. These objects are required in your request for enabling payments to international vendors.

We have updated the documentation with examples of international vendor locations like Brazil and Austria with instructions for setting paymentPurpose and regulatoryFields.

See Creating an international vendor for more information.

We have introduced a set of document and attachment API endpoints. You can now upload documents for bills with the v3 API. In addition, you can upload supporting attachments for vendors, customers, and invoices.

OperationAPI endpoint
Upload customer attachmentPOST /v3/attachments/customers/{customerId}
Get list of customer attachmentsGET /v3/attachments/customers/{customerId}
Upload invoice attachmentPOST /v3/attachments/invoices/{invoiceId}
Get list of invoice attachmentsGET /v3/attachments/invoices/{invoiceId}
Upload vendor attachmentPOST /v3/attachments/vendors/{vendorId}
Get list of vendor attachmentsGET /v3/attachments/vendors/{vendorId}
Get attachment detailsGET /v3/attachments/{attachmentId}
Upload bill documentPOST /v3/documents/bills/{billId}
Get document upload statusGET /v3/documents/upload-status
Get document detailsGET /v3/documents/{documentId}
Get list of documentsGET /v3/documents/bills/{billId}

See Documents and attachments for more information.

The BILL partner API endpoints require sessionId as a header value that is generated with API partner login (POST /v3/partner/login). We learned that API login as user (POST /v3/partner/login-as-user) endpoint is the only BILL partner endpoint where sessionId is required as a body parameter.

For consistency across the BILL partner API endpoints, we now require sessionId as a header value for the API login as user endpoint. See API login as user in the API reference for more information.

When you create a bulk payment with POST /v3/payments/bulk, the error response now includes details about the error at the individual bill level.

See Payments for more information.

As a BILL partner, you can now set a user role when you create a user (POST /v3/partner/users) or update a user (PATCH /v3/partner/users/{userId}).

You can set roleId as the BILL-generated ID of the user role you want to assign. You can get the list of available user roles with GET /v3/partner/roles. If you do not set roleId in your POST /v3/partner/users request, the default ADMINISTRATOR user role is assigned to the created user.

See Users for BILL partners for more information.

As a BILL partner, you can now get partner name information when you create an organization with POST /v3/partner/organizations. In the API response, partnerName is now available for providing information about the partner name.

Note: This field is available only when select BILL partners create an organization. Partner name is part of the information that BILL uses to identify partners.

See Organizations for BILL partners for more information.

When you create a bank account (POST /v3/funding-accounts/banks) in the production environment, you must complete bank account verification (POST /v3/funding-accounts/banks/{bankAccountId}/verify) before the account can be used for other BILL operations.

In the sandbox environment, you can now set depositAmount as 0.50 to complete bank account verification.

See Bank account setup (v3 API) for more information.

We have improved navigation between the Guides and API Reference sections. When you are reviewing the API Reference documentation for an endpoint, you now find links to the relevant Guides sections for more information, sample requests, and responses.

We have updated the webhooks events catalog to include event types for bank accounts and BILL risk verification. You can now set up subscriptions to receive notifications for these new events.

New eventsRelated documentation
Bank account notification payloads
risk-verification.updatedRisk verification notification payloads

See Get events catalog in the API reference for more information.