You can get details about your current API session with GET /v3/login/session. In the response, we have introduced PHONE_VERIFICATION as a new value for the mfaStatus field.
Your organization mfaStatus is set as PHONE_VERIFICATION when the organization does not use MFA. See GET /v3/login/session in the API reference for more information.
We have added a new recipe for showcasing the MFA sign in workflow with the v3 API. See MFA sign in the Recipes section for more information.
We have updated the webhooks events catalog to include the card-account.created event. You can now set up subscriptions to receive notifications for the new event.
See Card account notification payloads for more information.
We have introduced AP Card as a new funding account type for vendor payments with the v3 API.
The AP Card is a payment method that enables you to send fast payments with no transaction fees or annual fees. You can use the AP Card with any vendor who accepts credit card payments. See AP Card Frequently Asked Questions (FAQs) in the BILL Help to learn more about AP Cards.
When you create a vendor payment with POST /v3/payments, you can now set the AP_CARD as the funding account type.
See POST /v3/payments in the API reference for more information.
We have introduced GET /v3/funding-accounts/ap-cards for getting a list of AP Cards available in the current organization.
See GET /v3/funding-account/ap-cards in the API reference for more information.
The payment.updated webhook notification is available for the BANK_ACCOUNT, CARD_ACCOUNT, and WALLET funding type. We have now added notification capabilities for the AP_CARD funding account type.
See Payment notification payloads for more information.
When you create a vendor payment with a card account, we now require you to specify the card funding purpose for the payment. Set the card funding purpose as the vendor industry.
In your create payment request with POST /v3/payments, cardFundingPurpose is a new required body parameter for the CARD_ACCOUNT funding account type.
See POST /v3/payments in the API reference for more information.
In response to customer feedback, we have added check number information in the payments API response. When BILL processes your vendor payment as a check payment, the checkDisbursement object in the payments API response now includes the checkNumber field.
See POST /v3/payments in the API reference for more information.
In the bills API response, you now receive the total bill amount in addition to the existing bill line item amounts.
When you create any /v3/bills API request, you now see the amount field in the response. The amount value is the total bill amount. For a bill in an international currency (not USD), this value is in the local currency.
See Bills for more information.
We have added two new recipes for showcasing more workflows with the v3 API.
| Recipe | Description |
|---|---|
| Connect with a BILL network vendor | In this recipe, we search for and invite a network vendor. |
| Expense management with users, budgets, and virtual cards | In this recipe, we create a Spend & Expense user for a budget and then assign the user to a budget. In addition, we create a virtual card and assigned it to the budget user. |
When you create a bank account with the BILL v3 API, you can now enable bank account access to all users with the ADMINISTRATOR user role. Simply set accessToAdmins as true in your Create a bank account (POST /v3/funding-accounts/banks) or Update a bank account (PATCH /v3/funding-accounts/banks/{bankAccountId}) request.
See POST /v3/funding-accounts/banks and PATCH /v3/funding-accounts/banks/{bankAccountId} in the API reference for more information.
We have introduced a new Get API session details (GET /v3/login/session) endpoint. You can now get information about the current organization, current user, and MFA status of the organization.
See GET /v3/login/session in the API reference for more information.
