In the Spend & Expense transactions API, we have added updatedTime and authorizedTime to the list of transaction filters. In the Get list of transactions (GET /v3/spend/transactions) request, you can now filter transactions with the updatedTime (transaction updated date and time) and authorizedTime (transaction authorized date and time) fields.

New fields you can filter with

Available operators

updatedTime

lte (Less than or equal)
gte (Greater than or equal)

authorizedTime

lte (Less than or equal)
gte (Greater than or equal)

In addition, we have introduced the parentBudgetUuid field in the transactions API response. In all the transactions API responses, you can now get the BILL-generated UUID of the parent budget linked with each transaction.

See GET /v3/spend/transactions in the API reference for more information.

We have introduced a new API endpoint for getting a list of login organizations.

You can now get a list of organizations you can access with your current API session. In the response, you get a list of organizations and console organizations. When a console organization is available in the response, this indicates that the console organization is a parent of the listed organization.

OperationAPI endpoint
Get list of login organizationsGET /v3/login/organizations

In the Vendors API, we have added address.country to the list of vendor filters. You can now filter vendors with the address.country field.

New field you can filter with

Available operators

address.country

eq (Equal)
ne (Not equal)

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

In the payments API, we have introduced a new exchangeRateBatchId field. BILL maintains all exchangeRate values in a batch. When a batch expires, a new batch ID is generated and all exchangeRate values are updated in the new batch.

In the Create a payment (POST /v3/payments) and Create a bulk payment (POST /v3/payments/bulk) API request, you can now set the exchangeRateBatchId field that is required for paying international vendors.

Get the current BILL exchange rate and exchange rate batch ID with GET /v3/payments/exchange-rate or POST /v3/payments/exchange-rate (for multiple international vendors).

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


We have introduced a new API endpoint for getting BILL exchange rates for multiple vendors.

You can now get the current BILL exchange rate and exchange rate batch ID for multiple international vendors with one API request. The exchange rate batch ID is required for creating a bulk payment with POST /v3/payments/bulk.

The BILL exchange rate changes periodically. Use this endpoint to get the current exchange rate based on the payment amount and vendor bill currency.

OperationAPI endpoint
Get BILL exchange rates for multiple vendorsPOST /v3/payments/exchange-rate

We have added a new developer tutorial video - BILL v3 API webhooks explained - in the BILL API Platform for developers YouTube playlist. In this video, we learn how to use the BILL v3 Webhooks API to build faster, smarter, and more efficient integrations. See the BILL API Platform for developers playlist for the complete set of developer tutorial videos.

BILL v3 API webhooks explained

In this tutorial, we learn how to use the BILL v3 Webhooks API to build faster, smarter, and more efficient integrations.

Features

Loading states in all widgets

We have added loading state indicators across all widgets. In addition, we have improved the consistency across all loading state experiences.

Bug fixes

Onboarding widget

We learned that the Terms of Service screen did not have the correct maximum width. We have fixed this issue.

Vendor setup widget

  • We learned that the vendor name field was not marked as a required field. We have fixed this issue.
  • We learned that the correct zip codes were not being displayed for Verified National Vendor addresses. We have fixed this issue. The correct zip code is now displayed.
  • We learned that no events were being fired in the vendor disconnection flow. We have fixed this issue. The vendorSetupSuccess event is correctly fired when the user action is completed successfully.

We have added a new developer tutorial - Bill approvals with the BILL v3 API - in the BILL API Platform for developers YouTube playlist. See the BILL API Platform for developers playlist for the complete set of developer tutorials.

Bill approvals with the BILL v3 API

In this tutorial, we walk through how to build and manage bill approval workflows using the BILL v3 API.


We have added a new Postman Notebook for the BILL AR workflow with the BILL v3 API. See the BILL AR Workflow Postman Notebook for details.

In this notebook, you build an API workflow that enables you to set up a customer record in your BILL organization, create an invoice for the customer, and then charge the customer to get paid for the invoice.

In all, we now have 4 published Postman Notebooks.

We have improved the table of contents in the BILL v3 API API reference section on developer.bill.com.

You now see dedicated sections for Accounts Payable (AP) and Accounts Receivable (AR) operations. Other operations that belong to your BILL organization are now in the new Organization Operations section. There is no change in any of the other sections in the API reference.

These improvements are also available in the BILL v3 API Postman Collection.