We have introduced a new API endpoint for getting an invoice payment link.
You can now get a payment link based on the invoice and customer information you provide. You can send the invoice payment link to your customer for getting paid by the customer. With this link, the customer can complete the invoice payment without the need to set up a BILL account.
| Operation | API endpoint |
|---|---|
| Get an invoice payment link | POST /v3/invoices/{invoiceId}/payment-link |
We have introduced a set of API endpoints for received payment operations. You can now get and list payments that your BILL organization has received by customers.
| Operation | API endpoint |
|---|---|
| Get list of received payments | GET /v3/receivable-payments |
| Get received payment details | GET /v3/receivable-payments/{receivedPaymentId} |
We have introduced a set of API endpoints for credit memo operations. You can now create credit memos for adjusting the invoice amount owed by customers.
| Operation | API endpoint |
|---|---|
| Create a credit memo | POST /v3/credit-memos |
| Get list of credit memos | GET /v3/credit-memos |
| Get credit memo details | GET /v3/credit-memos/{creditMemoId} |
| Update a credit memo | PATCH /v3/credit-memos/{creditMemoId} |
| Replace a credit memo | PUT /v3/credit-memos/{creditMemoId} |
| Archive a credit memo | POST /v3/credit-memos/{creditMemoId}/archive |
| Restore a credit memo | POST /v3/credit-memos/{creditMemoId}/restore |
| Create multiple credit memos | POST /v3/credit-memos/bulk |
| Update multiple credit memos | PATCH v3/credit-memos/bulk |
| Replace multiple credit memos | PUT v3/credit-memos/bulk |
| Archive multiple credit memos | POST /v3/credit-memos/bulk/archive |
| Restore multiple credit memos | POST /v3/credit-memos/bulk/restore |
In addition, you can apply credit memo amounts to invoices. In the create and update invoice operations, you can now set the new creditAmount field in your request as the credit amount applied to an invoice.
The webhook notification payloads for all bill, vendor, bank account, and card account events now include all the response fields. For example, if you have subscribed to the vendor.created event, the payload for each related notification will now include the response fields for each created vendor.
All the webhook notification payload samples have been updated in the documentation.
In addition, the vendorName field is now available in all the bill webhooks. If you have subscribed to the bill.updated, bill.archived, or bill.restored events, the vendorName field is available in each payload.
When you create or update an item, you can now set the percentage field as the item tax percentage. You can set this field for a set of item type values.
DISCOUNTSALES_TAXOTHER_CHARGESee POST /v3/classifications/items in the API reference for more information.
In the Get list of bills (GET /v3/bills) and Get bills details (GET /v3/bills/{billId}) API response, we have introduced the vendorName field. You can now get the vendor name for each bill with these endpoints.
See GET /v3/bills in the API reference for more information.
We have added a set of API endpoints for the Spend & Expense transaction operations. You can now upload receipts for transactions.
| Operation | API endpoint |
|---|---|
| Generate an image upload URL for a transaction | POST /v3/spend/transactions/receipt-upload-url |
See Transactions for more information.
We have added a set of API endpoints for the Spend & Expense card operations. You can now manage cards by freezing and unfreezing cards.
| Operation | API endpoint |
|---|---|
| Freeze a card | POST /v3/spend/cards/{cardId}/freeze |
| Unfreeze a card | POST /v3/spend/cards/{cardId}/unfreeze |
See Vendor cards for more information.
You can now generate a developer key in the BILL web app to work with the BILL API. As an administrator of your test organization, you can generate up to 4 developer keys.
See Sandbox API sign up for more information.
The webhook notification payloads for all bill-related events now include all the response fields for the bill. For example, if you have subscribed to the bill.updated event, the payload for each related notification will now include all the response fields for the each updated bill.
See Bill notification payloads for more information.