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}"}'
NOTEUse
POST https://api.divvy.co/de/rest/panin 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.
| Operation | API endpoint |
|---|---|
| Create a custom field | POST /v3/spend/custom-fields |
| Get list of custom fields | GET /v3/spend/custom-fields |
| Get custom field details | GET /v3/spend/custom-fields/{customFieldId} |
| Update a custom field | PATCH /v3/spend/custom-fields/{customFieldId} |
| Delete a custom field | DELETE /v3/spend/custom-fields/{customFieldId} |
| Create custom field values | POST /v3/spend/custom-fields/{customFieldId}/values |
| Get list of custom field values | GET /v3/spend/custom-fields/{customFieldId}/values |
| Get custom field value details | GET /v3/spend/custom-fields/{customFieldId}/values/{customFieldValueId} |
| Delete custom field values | DELETE /v3/spend/custom-fields/{customFieldId}/values |
| Update custom field and values for a transaction | PUT /v3/spend/transactions/{transactionId}/custom-fields |
| Get custom field details for a transaction | GET /v3/spend/transactions/{transactionId}/custom-fields |
| Get custom field value details for a transaction | GET /v3/spend/transactions/{transactionId}/custom-fields/{customFieldId}/values |
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.
| Operation | API endpoint |
|---|---|
| Get list of card accounts | GET /v3/funding-accounts/cards |
| Get card account details | GET /v3/funding-accounts/cards/{cardAccountId} |
The payment.updated webhook notification now includes more information.
Field | Description |
|---|---|
| Vendor information. This includes vendor |
| A payment object is created for each payment.
|
See Payment notification payloads for more information.
We have updated the webhooks events catalog to include the autopay.failed event. You can now set up subscriptions to receive notifications for the new event.
See Vendor auto-pay notification payloads for more information.
You can now create multiple vendors with a single POST /v3/vendors/bulk API call. You can create up to 20 vendors with one POST /v3/vendors/bulk request.
See POST /v3/vendors/bulk in the API reference for more information.
We have introduced a new MFA step-up for API session (POST /v3/mfa/step-up) endpoint.
Ideally, when you sign in with POST /v3/login, set rememberMeId and device in your request to generate an MFA-trusted API session.
In case you sign in without rememberMeId and device in your request, you can use this POST /v3/mfa/step-up endpoint to mark the current API session as MFA trusted.
NOTEIn addition, we have added a new field in the API login endpoint response. You now see a
trustedfield in the response. This field is set astrueif the current API session is MFA-trusted.
See POST /v3/mfa/step-up in the API reference for more information.