We have introduced a new Get list of vendor payment options (GET /v3/payments/options) endpoint. You can now get a list of vendor payment options available based on the funding account options available in the signed-in user's BILL organization and on the payment methods accepted by a vendor.

See Vendor payment options for more information.

We have introduced a set of API endpoints for getting a list of bank account and card account users. In the response, if the funding account verificationStatus is set as NOMINATED, user verification must be completed before the user can pay with the specified funding account.

We have updated the webhooks events catalog to include the card-account.updated event. Notifications are triggered for this event when the card account expiration year or month is updated. You can now set up subscriptions to receive notifications for the new event.

See Card account notification payloads for more information.

We have introduced a new Get check image data (GET /v3/payments/{paymentId}/check-image) endpoint. You can now get images of an existing check sent to a vendor. From the response, use downloadLink in a GET request to download the front and back images of the check.

curl '{downloadLink}&sessionId={session_id}' \
--output {check_name}

See GET /v3/payments/{paymentId}/check-image in the API reference for more information.

We have introduced a new Get list of organization industries (GET /v3/organizations/industries) endpoint. You can now get a list of available values for the industry field for an organization. Use this information to set the industry field in your POST /v3/partner/organizations request.

See GET /v3/organizations/industries in the API reference for more information.

You can now set an invoice date in your create an invoice (POST /v3/invoices), replace an invoice (PUT /v3/invoices/{invoiceId}), and update an invoice (PATCH /v3/invoices/{invoiceId}) requests.

Set the invoiceDate field as the invoice creation date. This value is in the yyyy-MM-dd format. If you do not set this value, invoiceDate is set as the date when the invoice is created.

See POST /v3/invoices in the API reference for more information.

You can now convert a PAN JWT token (created with GET /v3/spend/cards/{cardId}/pan-jwt) to a Spend & Expense virtual card PAN in the sandbox environment.

curl --location --request POST 'https://app-dev-sandbox.divvy.co/de/rest/pan' \
--header 'Content-Type: application/json' \
--data-raw '{"token":"{JWT_token}"}'

📘

NOTE

Use POST https://api.divvy.co/de/rest/pan in the production environment.

See Virtual cards for more information.

We have added a new recipe for showcasing how you can set up a Spend & Expense custom field and then tag transactions with the created custom field. See Spend & Expense transaction management in the Recipes section for more information.

We have introduced a set of API endpoints for the Spend & Expense custom field operations. A custom field enables you to categorize transactions in a budget based on policies and projects in your organization.

We have introduced a set of API endpoints for getting card account information. With these new endpoints, you can get details about the card accounts that have been set up as funding accounts in your organization.