---
title: BILL API Integration on Truto
slug: bill
category: Spend Management
canonical: "https://truto.one/integrations/detail/bill/"
---

# BILL API Integration on Truto



**Category:** Spend Management  
**Status:** Beta

## MCP-ready AI tools

Truto exposes 312 tools for BILL that AI agents can call directly.

- **bill_session_login** — API login. Sign in to your BILL developer account. In the response, your API session is created and a BILL-generated sessionId is available. Use the sessionId in all subsequent API calls to confirm that you are in a signed-in session. Required: devKey, username, organizationId. The connector signs in with the connection's own username, password, organization ID and developer key (post_install, then every 28 minutes); a caller's body overrides them.
- **bill_session_get_info** — Get API session details. Get details about your current API session. This includes information about the current organization ID, user ID, and MFA status of the organization.
- **list_all_bill_organizations** — Get list of login organizations. Get a list of organizations you can access with your current API session. You get 100 results on one page of results. In the response, you get a list of organizations and console organizations. The connector pages with page (BILL's nextPage) (100 a page); records at results.organizations.
- **get_single_bill_organization_by_id** — Get organization details. Get details about an existing organization. The currently signed-in user must have the ADMINISTRATOR user role in the BILL organization to perform this operation. See Organizations and Users in the Guides section for more information, sample requests, and responses. Required: id.
- **update_a_bill_organization_by_id** — Update an organization. Update details about an existing organization. The currently signed-in user must have the ADMINISTRATOR user role in the BILL organization to perform this operation. See Organizations and Users in the Guides section for more information, sample requests, and responses. Required: id.
- **bill_health_check** — Check app health. Get app details, such as version and deployment location. Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials).
- **list_all_bill_bill_approval_policies** — Get list of bill approval policies. Get a list of bill approval policy objects.
- **create_a_bill_bill_approval_policy** — Create a bill approval policy. Create a new bill approval policy. In your request, set rules and approvers in the specified format. For example, to create a bill approval policy for all bills greater than or equal to $1000, set rules for BILL_AMOUNT. Required: policyName, rules, approvers.
- **update_a_bill_bill_approval_policy_by_id** — Update a bill approval policy. Update an existing bill approval policy. Required: id, policyName, rules, approvers.
- **delete_a_bill_bill_approval_policy_by_id** — Delete a bill approval policy. Delete an existing bill approval policy. A deleted approval policy cannot be restored. The deleted policy is not available in the list of approval policies. Required: id.
- **list_all_bill_bank_accounts** — Get list of bank accounts. Get a list of bank account objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **get_single_bill_bank_account_by_id** — Get bank account details. Get details about an existing bank account. Required: id.
- **bill_bank_accounts_archive** — Archive a bank account. Archive an existing bank account. In the response, the archived field is set as true. Archiving a bank account at BILL has a set of requirements. * Bank account status: The bank account status must be set as VERIFIED. Required: bank_account_id.
- **create_a_bill_bank_account** — Create a bank account. Create a new bank account. The currently signed-in user must have the ADMINISTRATOR user role in the BILL organization to perform this operation. BILL sends an email notification for informing you about changes to your funding accounts. Required: nameOnAccount, type, ownerType, bankName.
- **update_a_bill_bank_account_by_id** — Update a bank account. Update details about an existing bank account. This operation follows a set of rules. * Bank account status requirement: The bank account status must be set as VERIFIED before you can update any details about the bank account. Required: id.
- **bill_bank_accounts_verify** — Verify a bank account. Verify an existing bank account. When you create a bank account, BILL sends a test ACH payment to the bank account to confirm whether the account details are accurate. Enter the test amount as the depositAmount value in your POST /v3/funding-accounts/banks/{bankAccountId}/verify request. Required: bank_account_id, depositAmount.
- **list_all_bill_card_funding_purposes** — Get card funding purpose. Get a list of card funding purpose values based on the vendor and card brand. When you create a payment (POST /v3/payments or POST /v3/payments/bulk) with a CARD_ACCOUNT funding account type, BILL requires a vendor industry value for compliance. Required: vendorId, brand.
- **list_all_bill_bills** — Get list of bills. Get a list of bill objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **create_a_bill_bill** — Create a bill. Create a new bill. See Bills in the Guides section for more information, sample requests, and responses. Required: vendorId, dueDate, billLineItems, invoice.
- **get_single_bill_bill_by_id** — Get bill details. Get details about an existing bill. Required: id.
- **update_a_bill_bill_by_id** — Replace a bill. Update the number of line items in a bill. You can also update other bill details. You can use the PUT operation to add, remove, or replace the number of line items in a bill. A set of rules apply with the PUT operation. * When you add a new line item, a new line item id is generated in the bill. Required: id, vendorId, dueDate, billLineItems, invoice.
- **bill_bills_archive** — Archive a bill. Archive an existing bill. In the response, the archived field is set as true. You can restore an archived bill with POST /v3/bills/{billId}/restore. There is no change when you archive an archived bill. Required: bill_id.
- **bill_bills_restore** — Restore an archived bill. Restore an archived bill. In the response, the archived field is set as false. You can perform any valid BILL operation on restored bills. There is no change when you restore a restored bill. Required: bill_id.
- **bill_bills_record_payment** — Record AP payment. Record an offline AP payment made to a vendor. An offline payment is a payment made outside the BILL system. BILL simply applies the recorded payment amount to one or more bills for the vendor. Required: vendorId, processDate, toPrintCheck, payments.
- **bill_bills_bulk_create** — Create multiple bills. Create multiple bills with one API request. You can create up to 100 bills with one POST /v3/bills/bulk request. Bulk bill creation at BILL follow a set of rules. * Successful response: In your bulk bill creation request, all your bills must be successfully created for a successful response.
- **bill_bills_partial_update** — Update a bill. Update details about a bill line item. You can also update other bill details. You can use the PATCH operation to modify line item details, such as amount and description. The bill line item id does not change with a PATCH operation. PATCH beside the PUT update: the record id is a named query field (the connector passes {{id}} only to get / update / delete). Required: bill_id, paymentTermId.
- **list_all_bill_vendors** — Get list of vendors. Get a list of vendor objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **create_a_bill_vendor** — Create a vendor. Create a new vendor. ### Requirements for enabling vendor payments Vendor address details are required for paying a vendor by check or for inviting the vendor to join the BILL network. Required: name, address.
- **get_single_bill_vendor_by_id** — Get vendor details. Get details about an existing vendor. Required: id.
- **update_a_bill_vendor_by_id** — Update a vendor. Update details about an existing vendor. ### Requirements for enabling vendor payments Vendor address details are required for paying a vendor by check or for inviting the vendor to join the BILL network. Required: id.
- **bill_vendors_archive** — Archive a vendor. Archive an existing vendor. In the response, the archived field is set as true. You can restore an archived vendor with POST /v3/vendors/{vendorId}/restore. There is no change when you archive an archived vendor. Required: vendor_id.
- **bill_vendors_restore** — Restore an archived vendor. Restore an archived vendor. In the response, the archived field is set as false. You can perform any valid BILL operation on restored vendors. There is no change when you restore a restored vendor. Required: vendor_id.
- **bill_vendors_get_configuration** — Get vendor configuration. Get international payments (not USD) configuration after vendor creation. This configuration is required for compliance with international payment rules of a vendor country and vendor bank account. Required: vendor_id.
- **bill_vendors_get_intl_config** — Get international payments configuration. Get international payments (not USD) configuration that is required for compliance with international payment rules of a vendor country and vendor bank account. This information is based on vendor country, bill currency, and vendor account type. Required: country, billCurrency, accountType.
- **bill_vendors_bulk_create** — Create multiple vendors. Create multiple vendors with one API request. You can create up to 20 vendors with one POST /v3/vendors/bulk request. In your bulk vendor creation request, all your vendors must be successfully created for a successful response.
- **list_all_bill_customers** — Get list of customers. Get a list of customer objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **create_a_bill_customer** — Create a customer. Create a new customer. See Customers in the Guides section for more information, sample requests, and responses. Required: name, email.
- **get_single_bill_customer_by_id** — Get customer details. Get details about an existing customer. Required: id.
- **update_a_bill_customer_by_id** — Update a customer. Update details about an existing customer. Required: id.
- **bill_customers_archive** — Archive a customer. Archive an existing customer. In the response, the archived field is set as true. You can restore an archived customer with POST /v3/customers/{customerId}/restore. There is no change when you archive an archived customer. Required: customer_id.
- **bill_customers_restore** — Restore an archived customer. Restore an archived customer. In the response, the archived field is set as false. You can perform any valid BILL operation on restored customers. There is no change when you restore a restored customer. Required: customer_id.
- **bill_customers_set_charge_authorization** — Set charge customer authorization. Authorize your organization to charge a customer for invoices. By default, your organization is not authorized to charge a customer. The customer authorizedToCharge field must be set as true for you to charge the customer for invoices. Required: customer_id, authorizedToCharge.
- **list_all_bill_invoices** — Get list of invoices. Get a list of invoice objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **create_a_bill_invoice** — Create an invoice. Create a new invoice. See Invoices in the Guides section for more information, sample requests, and responses. Required: customer, invoiceLineItems.
- **get_single_bill_invoice_by_id** — Get invoice details. Get details about an existing invoice. Required: id.
- **update_a_bill_invoice_by_id** — Replace an invoice. Update the number of line items in an invoice. You can also update other invoice details. You can use the PUT operation to add, remove, or replace the number of line items in an invoice. A set of rules apply with the PUT operation. Required: id, customer, invoiceLineItems.
- **bill_invoices_archive** — Archive an invoice. Archive an existing invoice. In the response, the archived field is set as true. You can restore an archived invoice with POST /v3/invoices/{invoiceId}/restore. There is no change when you archive an archived invoice. Required: invoice_id.
- **bill_invoices_restore** — Restore an archived invoice. Restore an archived invoice. In the response, the archived field is set as false. You can perform any valid BILL operation on restored invoices. There is no change when you restore a restored invoice. Required: invoice_id.
- **bill_invoices_send** — Send an invoice. Send an invoice to a customer email address. You can send the invoice to multiple email addresses. See Invoices in the Guides section for more information, sample requests, and responses. Required: invoice_id, replyTo, recipient.
- **bill_invoices_get_payment_link** — Get invoice payment link. Get an invoice payment link. In the response, BILL sends you a payment link based on the provided invoice and customer information. You can send the invoice payment link to your customer for getting paid by the customer. Required: invoice_id, customerId, email.
- **bill_invoices_partial_update** — Update an invoice. Update details about an invoice line item. You can also update other invoice details. You can use the PATCH operation to modify line item details, such as amount, quantity, and description. The invoice line item id does not change with a PATCH operation. PATCH beside the PUT update: the record id is a named query field (the connector passes {{id}} only to get / update / delete). Required: invoice_id.
- **bill_invoices_record_payment** — Record AR payment. Record an offline AR payment received from a customer. An offline payment is a payment that you receive outside the BILL system. BILL simply applies the recorded payment amount to one or more invoices for the customer. Required: paymentDate, paymentType, amount, invoices.
- **list_all_bill_recurring_invoices** — Get list of recurring invoices. Get a list of recurring invoice objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **create_a_bill_recurring_invoice** — Create a recurring invoice. Create a recurring invoice. See Recurring invoices in the Guides section for more information, sample requests, and responses. Required: customerId, schedule, recurringInvoiceLineItems.
- **get_single_bill_recurring_invoice_by_id** — Get recurring invoice details. Get details about an existing recurring invoice. Required: id.
- **update_a_bill_recurring_invoice_by_id** — Replace a recurring invoice. Update the number of line items in a recurring invoice. You can also update other recurring invoice details. You can use the PUT operation to add, remove, or replace the number of line items in a recurring invoice. A set of rules apply with the PUT operation. Required: id, customerId, schedule, recurringInvoiceLineItems.
- **bill_recurring_invoices_archive** — Archive a recurring invoice. Archive a recurring invoice. In the response, the archived field is set as true. You can restore an archived recurring invoice with POST /v3/recurring-invoices/{recurringinvoiceId}/restore. There is no change when you archive an archived recurring invoice. Required: recurring_invoice_id.
- **bill_recurring_invoices_partial_update** — Update a recurring invoice. Update details about a recurring invoice line item. You can also update other recurring invoice details. You can use the PATCH operation to modify line item details, such as amount and description. The recurring invoice line item id does not change with a PATCH operation. PATCH beside the PUT update: the record id is a named query field (the connector passes {{id}} only to get / update / delete). Required: recurring_invoice_id.
- **bill_recurring_invoices_restore** — Restore a recurring invoice. Restore an archived recurring invoice. In the response, the archived field is set as false. You can perform any valid BILL operation on restored recurring invoices. There is no change when you restore a restored recurring invoice. Required: recurring_invoice_id.
- **list_all_bill_payments** — Get list of payments. Get a list of payment objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **create_a_bill_payment** — Create a payment. Create a payment. See Get list of vendor payment options to get details about vendor payment options and payment process dates. Note: Creating a payment requires an MFA-trusted API session. See MFA setup for information about the BILL MFA process. Required: fundingAccount, amount, processingOptions.
- **bill_payments_create_mass** — Create a mass payment. Create a mass payment request for up to 2000 bills. BILL processes each payment in the mass payment request asynchronously. In the response, a BILL-generated payment batch ID is available. Required: fundingAccount.
- **bill_payments_get_mass** — Get mass payment status. Get details about an existing mass payment batch. In the response, you get the status of each payment in the mass payment batch. Each payment is either scheduled, completed, or failed. In addition, you get the count for the total number of payments in the mass payments batch. Required: payment_batch_id.
- **bill_payments_list_options** — Get list of vendor payment options. 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 in the Guides section for more information, sample requests, and responses. Required: vendorId, amount.
- **bill_payments_get_exchange_rate** — Get BILL exchange rate. Get the current BILL exchange rate and exchange rate batch ID for paying an international vendor. When the vendor bill currency is not USD, the exchange rate batch ID is required for creating a payment with POST /v3/payments or POST /v3/payments/bulk. Required: vendorId, amount.
- **bill_payments_get_exchange_rates** — Get BILL exchange rates for multiple vendors. Get the current BILL exchange rate and exchange rate batch ID for multiple international vendors with one API request. When the vendor bill currency is not USD, the exchange rate batch ID is required for creating a payment with POST /v3/payments or POST /v3/payments/bulk.
- **get_single_bill_payment_by_id** — Get payment details. Get details about an existing payment. Required: id.
- **bill_payments_cancel** — Cancel a payment. Cancel an existing payment. You can cancel a payment only when the payment singleStatus is SCHEDULED. When BILL starts processing the payment, the payment singleStatus changes. At that point, you cannot cancel the payment. You can attempt to void the payment with POST /v3/payments/{paymentId}/void. Required: payment_id.
- **bill_payments_void** — Void a payment. Void an existing payment. Void a bill payment that has started processing and cannot be canceled (with POST /v3/payments/{paymentId}/cancel). You can attempt to void payments made both with BILL (online) and outside BILL (offline). Required: payment_id, type, reason.
- **bill_payments_get_check_image** — Get check image data. Get an image of an existing check sent to a vendor. The check image is available when the vendor bank processes the check payment. BILL checks in with the bank every 30 minutes to get the check image. The image file format is determined by the vendor bank. Required: payment_id.
- **bill_payments_bulk_create** — Create a bulk payment. Create a request for paying multiple bills. You can pay up to 50 bills with one POST /v3/payments/bulk request. Bulk payments at BILL follow a set of rules. * Successful response: In your bulk payment request, all your bill payments must be successful for a successful response. Required: fundingAccount.
- **list_all_bill_vendor_credits** — Get list of vendor credits. Get a list of vendor credit objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **create_a_bill_vendor_credit** — Create a vendor credit. Create a vendor credit. With a vendor credit, you can adjust the amount that you owe a vendor. See Vendor credits in the Guides section for more information, sample requests, and responses. Required: vendorId, referenceNumber, creditDate, vendorCreditLineItems.
- **get_single_bill_vendor_credit_by_id** — Get vendor credit details. Get details about an existing vendor credit. Required: id.
- **update_a_bill_vendor_credit_by_id** — Replace a vendor credit. Update the number of line items in a vendor credit. You can also update other vendor credit details. You can use the PUT operation to add, remove, or replace the number of line items in a vendor credit. A set of rules apply with the PUT operation. Required: id, vendorId, referenceNumber, creditDate, vendorCreditLineItems.
- **bill_vendor_credits_archive** — Archive a vendor credit. Archive an existing vendor credit. In the response, the archived field is set as true. An archived vendor credit cannot be restored. Required: vendor_credit_id.
- **bill_vendor_credits_partial_update** — Update a vendor credit. Update details about a vendor credit line item. You can also update other vendor credit line item details. You can use the PATCH operation to modify line item details, such as amount, quantity, and description. The vendor credit line item id does not change with a PATCH operation. PATCH beside the PUT update: the record id is a named query field (the connector passes {{id}} only to get / update / delete). Required: vendor_credit_id.
- **bill_vendor_credits_bulk_create** — Create multiple vendor credits. Create multiple vendor credits with one API request. You can create up to 50 vendor credits with one POST /v3/vendor-credits/bulk request.
- **bill_vendor_credits_bulk_replace** — Replace multiple vendor credits. Update the number of line items in multiple vendor credits with one API request. You can also update other details for each vendor credit. You can use the PUT operation to add, remove, or replace the number of line items in a vendor credit. A set of rules apply with the PUT operation.
- **bill_vendor_credits_bulk_update** — Update multiple vendor credits. Update details about line items in multiple vendor credits with one API request. You can also update other vendor credit details. You can use the PATCH operation to modify line item details, such as amount, quantity, and description.
- **bill_vendor_credits_bulk_archive** — Archive multiple vendor credits. Archive multiple vendor credits with one API request. In the response, the archived field for each object is set as true. An archived vendor credit cannot be restored. Required: ids.
- **list_all_bill_recurring_bills** — Get list of recurring bills. Get a list of recurring bill objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **create_a_bill_recurring_bill** — Create a recurring bill. Create a recurring bill. See Recurring bills in the Guides section for more information, sample requests, and responses. Required: vendorId, schedule, recurringBillLineItems.
- **get_single_bill_recurring_bill_by_id** — Get recurring bill details. Get details about an existing recurring bill. Required: id.
- **update_a_bill_recurring_bill_by_id** — Replace a recurring bill. Update the number of line items in a recurring bill. You can also update other recurring bill details. You can use the PUT operation to add, remove, or replace the number of line items in a recurring bill. A set of rules apply with the PUT operation. Required: id, vendorId, schedule, recurringBillLineItems.
- **bill_recurring_bills_archive** — Archive a recurring bill. Archive a recurring bill. In the response, the archived field is set as true. You can restore an archived recurring bill with POST /v3/recurringbills/{recurringbillId}/restore. There is no change when you archive an archived recurring bill. Required: recurring_bill_id.
- **bill_recurring_bills_restore** — Restore an archived recurring bill. Restore an archived recurring bill. In the response, the archived field is set as false. You can perform any valid BILL operation on restored recurring bills. There is no change when you restore a restored recurring bill. When a recurring bill is modified, all future bills are automatically changed. Required: recurring_bill_id.
- **bill_recurring_bills_partial_update** — Update a recurring bill. Update details about a recurring bill line item. You can also update other recurring bill details. You can use the PATCH operation to modify line item details, such as amount and description. The recurring bill line item id does not change with a PATCH operation. PATCH beside the PUT update: the record id is a named query field (the connector passes {{id}} only to get / update / delete). Required: recurring_bill_id.
- **create_a_bill_vendor_bank_account** — Create a vendor bank account. Create a vendor bank account for an existing vendor. Required: vendor_id, accountNumber.
- **list_all_bill_vendor_bank_accounts** — Get vendor bank account details. Get details about an existing vendor bank account. Required: vendor_id.
- **bill_vendor_bank_accounts_bulk_delete** — Delete a vendor bank account. Delete the existing vendor bank account for a vendor. Required: vendor_id.
- **list_all_bill_credit_memos** — Get list of credit memos. Get a list of credit memo objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **create_a_bill_credit_memo** — Create a credit memo. Create a new credit memo. With a credit memo, you can adjust the invoice amount owed by a customer. See Credit memos in the Guides section for more information, sample requests, and responses. Required: customerId, referenceNumber, creditDate, creditMemoLineItems.
- **get_single_bill_credit_memo_by_id** — Get credit memo details. Get details about an existing credit memo. Required: id.
- **bill_credit_memos_archive** — Archive a credit memo. Archive an existing credit memo. In the response, the archived field is set as true. You can restore an archived credit memo with POST /v3/credit-memos/{creditMemoId}/restore. There is no change when you archive an archived credit memo. Required: credit_memo_id.
- **bill_credit_memos_restore** — Restore a credit memo. Restore an archived credit memo. In the response, the archived field is set as false. You can perform any valid BILL operation on restored credit memos. There is no change when you restore a restored credit memo. Required: credit_memo_id.
- **update_a_bill_credit_memo_by_id** — Replace a credit memo. Update the number of line items in a credit memo. You can also update other credit memo details. You can use the PUT operation to add, remove, or replace the number of line items in a credit memo. A set of rules apply with the PUT operation. Required: id, customerId, referenceNumber, creditDate, creditMemoLineItems.
- **bill_credit_memos_bulk_create** — Create multiple credit memos. Create multiple credit memos with one API request. You can create up to 50 credit memos with one POST /v3/credit-memos/bulk request.
- **bill_credit_memos_bulk_replace** — Replace multiple credit memos. Update the number of line items in multiple credit memos with one API request. You can also update other details for each credit memo. You can use the PUT operation to add, remove, or replace the number of line items in a credit memo. A set of rules apply with the PUT operation.
- **bill_credit_memos_bulk_update** — Update multiple credit memos. Update details about line items in multiple credit memos with one API request. You can also update other credit memo details. You can use the PATCH operation to modify line item details, such as amount, quantity, and description. The credit memo line item id does not change with a PATCH operation.
- **bill_credit_memos_bulk_archive** — Archive multiple credit memos. Archive multiple credit memos with one API request. In the response, the archived field for each object is set as true. Required: ids.
- **bill_credit_memos_bulk_restore** — Restore multiple credit memos. Restore multiple credit memos with one API request. In the response, the archived field for each object is set as false. Required: ids.
- **bill_credit_memos_partial_update** — Update a credit memo. Update details about a credit memo line item. You can also update other credit memo line item details. You can use the PATCH operation to modify line item details, such as amount, quantity, and description. The credit memo line item id does not change with a PATCH operation. PATCH beside the PUT update: the record id is a named query field (the connector passes {{id}} only to get / update / delete). Required: credit_memo_id.
- **bill_mfa_generate_challenge** — Generate MFA challenge. Generate an MFA challenge ID for creating an MFA-trusted API sign in session. In the response, a challengeId is generated and a six-digit token is sent to the phone number that was registered with MFA setup.
- **bill_mfa_validate_challenge** — Validate MFA challenge. Validate the MFA challenge for creating an MFA-trusted API sign in session. This validation requires the challengeId and token from POST /v3/mfa/challenge. After the validation is complete, your API session is MFA trusted. There are two stages in the BILL MFA process. 1. Required: challengeId, token.
- **bill_mfa_list_phones** — Get list of MFA phone numbers. Get a list of phone numbers that have been added for setting up MFA in the current organization.
- **bill_mfa_setup** — Add phone for MFA setup. Add a valid phone number for setting up MFA in the current organization. In the response, a setupId is generated and a six-digit token is sent to the phone number. Required: phone, type.
- **bill_mfa_validate_setup** — Validate phone for MFA setup. Validate the phone number for setting up MFA in the current organization. This validation requires the setupId and token from POST /v3/mfa/setup. After the validation is complete, the phone number is registered for the MFA sign in operation. There are two stages in the BILL MFA process. 1. Required: setupId, type, token.
- **bill_mfa_step_up** — MFA step-up for API session. Set your current API session as MFA trusted. Ideally, when you sign in with POST /v3/login, set rememberMeId and device in your request to generate an MFA-trusted API session.
- **bill_bill_approvals_approve_deny** — Approve or deny a bill. Approve or deny a bill. Approved bills can be paid. In the request, create an array of objects, where each object represents a single bill along with its approval or denial status.
- **list_all_bill_payment_terms** — Get list of payment terms. Get a list of payment terms for the organization. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. Required: organization_id. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **get_single_bill_payment_term_by_id** — Get payment term details. Get details about an existing payment term. Required: id, organization_id.
- **create_a_bill_payment_term** — Create a payment term. Create a new payment term for the organization. Use payment terms to set the number of days the customer has to pay a vendor. You can set paymentTermId in bills and invoices. Required: organization_id, name, daysDue.
- **update_a_bill_payment_term_by_id** — Update a payment term. Update details about an existing payment term. Required: id, organization_id.
- **list_all_bill_billing_statements** — Get list of billing statements. Get a list of billing statements for the organization. BILL generates a monthly billing invoice statement for all the billing activities in the organization. In the request, set invoiceDateFrom and invoiceDateTo to get the billing invoice statements for the specified date range. Required: organization_id. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **get_single_bill_billing_statement_by_id** — Get billing statement details. Get details about a billing statement for the organization. BILL generates a monthly billing invoice statement for all the billing activities in the organization. From the response, use downloadLink in a GET request to download a billing statement. Required: id, organization_id.
- **list_all_bill_users** — Get list of users. Get a list of user objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **get_single_bill_user_by_id** — Get user details. Get details about an existing user. Required: id.
- **create_a_bill_user** — Create a user. Create a new user. The currently signed-in user must have the ADMINISTRATOR user role in the BILL organization to perform this operation. When you create a user, BILL sends an email to the user for them to complete their sign-up. Required: firstName, lastName, email, roleId, acceptTermsOfService.
- **bill_users_archive** — Archive a user. Archive an existing user. In the response, the archived field is set as true." You can restore an archived user with POST /v3/users/{userId}/restore. There is no change when you archive an archived user. Required: user_id.
- **bill_users_restore** — Restore an archived user. Restore an archived user. In the response, the archived field is set as false. You can perform any valid BILL operation on restored users. There is no change when you restore a restored user. Required: user_id.
- **update_a_bill_user_by_id** — Update a user. Update details about an existing user. Required: id.
- **list_all_bill_roles** — Get list of user roles. Get a list of user role objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **get_single_bill_role_by_id** — Get user role details. Get details about an existing user role. Required: id.
- **list_all_bill_chart_of_accounts** — Get list of chart of accounts. Get a list of chart of accounts objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **get_single_bill_chart_of_account_by_id** — Get chart of accounts details. Get details about an existing chart of accounts. Required: id.
- **create_a_bill_chart_of_account** — Create a chart of accounts. Create a new chart of accounts. Required: name.
- **update_a_bill_chart_of_account_by_id** — Update a chart of accounts. Update details about an existing chart of accounts. Required: id.
- **bill_chart_of_accounts_archive** — Archive a chart of accounts. Archive an existing chart of accounts. In the response, the archived field is set as true. Required: chart_of_account_id.
- **bill_chart_of_accounts_bulk_create** — Create multiple chart of accounts. Create multiple chart of accounts with one API request. You can create up to 50 chart of accounts with one POST /v3/classifications/chart-of-accounts/bulk request.
- **bill_chart_of_accounts_bulk_update** — Update multiple chart of accounts. Update details about multiple chart of accounts with one API request.
- **bill_chart_of_accounts_bulk_archive** — Archive multiple chart of accounts. Archive multiple chart of accounts with one API request. In the response, the archived field for each object is set as true. Required: ids.
- **bill_chart_of_accounts_bulk_restore** — Restore multiple chart of accounts. Restore multiple chart of accounts with one API request. In the response, the archived field for each object is set as false. Required: ids.
- **bill_chart_of_accounts_restore** — Restore an archived chart of accounts. Restore an archived chart of accounts. In the response, the archived field is set as false. Required: chart_of_account_id.
- **list_all_bill_departments** — Get list of departments. Get a list of department objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **get_single_bill_department_by_id** — Get department details. Get details about an existing department. Required: id.
- **create_a_bill_department** — Create a department. Create a new department. Required: name.
- **update_a_bill_department_by_id** — Update a department. Update details about an existing department. Required: id.
- **bill_departments_archive** — Archive a department. Archive an existing department. In the response, the archived field is set as true. Required: department_id.
- **bill_departments_bulk_archive** — Archive multiple departments. Archive multiple departments with one API request. In the response, the archived field is set as true. Required: ids.
- **bill_departments_bulk_create** — Create multiple departments. Create multiple departments with one API request. You can create up to 50 departments with one POST /v3/classifications/departments/bulk request.
- **bill_departments_bulk_restore** — Restore multiple departments. Restore multiple departments with one API request. In the response, the archived field is set as false. Required: ids.
- **bill_departments_bulk_update** — Update multiple departments. Update multiple departments with one API request.
- **bill_departments_restore** — Restore an archived department. Restore an archived department. In the response, the archived field is set as false. Required: department_id.
- **list_all_bill_locations** — Get list of locations. Get a list of location objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **get_single_bill_location_by_id** — Get location details. Get details about an existing location. Required: id.
- **create_a_bill_location** — Create a location. Create a new location. Required: name.
- **update_a_bill_location_by_id** — Update a location. Update details about an existing location. Required: id.
- **bill_locations_archive** — Archive a location. Archive an existing location. In the response, the archived field is set as true. Required: location_id.
- **bill_locations_bulk_create** — Create multiple locations. Create multiple locations with one API request. You can create up to 50 locations with one POST /v3/classifications/locations/bulk request.
- **bill_locations_bulk_archive** — Archive multiple locations. Archive multiple locations with one API request. In the response, the archived field for each object is set as true. Required: ids.
- **bill_locations_bulk_restore** — Restore multiple locations. Restore multiple locations with one API request. In the response, the archived field for each object is set as false. Required: ids.
- **bill_locations_bulk_update** — Update multiple locations. Update details about multiple locations with one API request.
- **bill_locations_restore** — Restore an archived location. Restore an archived location. In the response, the archived field is set as false. Required: location_id.
- **bill_risk_verifications_add_phone** — Add phone for risk verification. Add a phone number for the currently signed-in user. BILL requires the signed-in user to have a linked phone number for initiating risk verification for the organization. You can check whether a phone number has been added for the user with GET /v3/risk-verifications/phone. Required: phoneNumber, phoneType.
- **bill_risk_verifications_initiate** — Initiate risk verification for an organization. Initiate risk verification for an organization. The currently signed-in user must have the ADMINISTRATOR user role in the BILL organization to perform this operation.
- **list_all_bill_risk_verifications** — Get risk verification details. Get risk verification details for an existing organization.
- **create_a_bill_invoice_attachment** — Upload invoice attachment. Upload an attachment for an existing invoice. The file size limit is 6 MB. Note: When you upload an attachment, it takes a few minutes for BILL to complete the upload process. See Documents and attachments in the Guides section for more information, sample requests, and responses. Send the file's bytes as the request body with truto_body_passthrough=true (Content-Type application/octet-stream) and its file name in name. Required: invoice_id, name, file.
- **list_all_bill_invoice_attachments** — Get list of invoice attachments. Get a list of attachments associated with an invoice. From the response, use downloadLink in a GET request to download the attachment. curl '{downloadLink}' --header 'sessionId: {session_id}' --output {attachment_name}. Required: invoice_id. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **bill_accounting_classes_archive** — Archive an accounting class. Archive an existing accounting class. In the response, the archived field is set as true. Required: accounting_class_id.
- **bill_accounting_classes_bulk_archive** — Archive multiple accounting classes. Archive multiple accounting classes with one API request. In the response, the archived field for each object is set as true. Required: ids.
- **bill_accounting_classes_bulk_create** — Create multiple accounting classes. Create multiple accounting classes with one API request. You can create up to 50 accounting classes with one POST /v3/classifications/accounting-classes/bulk request.
- **bill_accounting_classes_bulk_restore** — Restore multiple accounting classes. Restore multiple accounting classes with one API request. In the response, the archived field for each object is set as false. Required: ids.
- **bill_accounting_classes_bulk_update** — Update multiple accounting classes. Update details about multiple accounting classes with one API request.
- **create_a_bill_accounting_class** — Create an accounting class. Create a new accounting class. Required: name.
- **get_single_bill_accounting_class_by_id** — Get accounting class details. Get details about an existing accounting class. Required: id.
- **list_all_bill_accounting_classes** — Get list of accounting classes. Get a list of accounting class objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **bill_accounting_classes_restore** — Restore an archived accounting class. Restore an archived accounting class. In the response, the archived field is set as false. Required: accounting_class_id.
- **update_a_bill_accounting_class_by_id** — Update an accounting class. Update details about an existing accounting class. Required: id.
- **list_all_bill_ap_cards** — Get list of AP Cards. Get a list of AP Card objects. With the AP Card, you can earn rewards simply by paying your bills. 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 virtual card payments.
- **delete_a_bill_attachment_by_id** — Delete an attachment. Delete the existing attachment. A deleted attachment cannot be restored. The deleted attachment is not available in the list of attachments. Required: id.
- **get_single_bill_attachment_by_id** — Get attachment details. Get details about an attachment. From the response, use downloadLink in a GET request to download the attachment. curl '{downloadLink}' --header 'sessionId: {session_id}' --output {attachment_name}. Required: id.
- **bill_bank_account_users_archive** — Archive a bank account user. Archive an existing bank account user. In the response, the archived field is set as true and the bank account user verificationStatus is set as UNVERIFIED. Required: bank_account_user_id.
- **list_all_bill_bank_account_users** — Get list of bank account users. Get a list of bank account user objects. In the response, if the bank account user verificationStatus is set as NOMINATED, user verification must be completed before the user can pay with the specified bank account. By default, you get 20 results on one page of results. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **bill_bank_account_users_nominate** — Nominate a bank account user. Nominate a bank account user. When you nominate a user, BILL performs a set of operations. * The bank account user verificationStatus is set as NOMINATED. * BILL sends the user an email asking them to sign in to the BILL web app and complete identity verification. Required: userId, bankAccountId.
- **create_a_bill_bill_document** — Upload bill document. Upload a document for an existing bill. The file size limit is 6 MB. When you upload a bill document, the uploaded document is available on the bill details page in the BILL web app. In the response, the name, createdTime, and downloadLink is available when the upload is complete. Send the file's bytes as the request body with truto_body_passthrough=true (Content-Type application/octet-stream) and its file name in name. Required: bill_id, name, file.
- **list_all_bill_bill_documents** — Get list of documents. Get a list of documents associated with a bill. From the response, use downloadLink in a GET request to download the document. curl '{downloadLink}' --header 'sessionId: {session_id}' --output {document_name}. Required: bill_id. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **list_all_bill_card_account_users** — Get list of card account users. Get a list of card account user objects. In the response, if the card account user verificationStatus is set as NOMINATED, user verification must be completed before the user can pay with the specified card account. By default, you get 20 results on one page of results. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **get_single_bill_card_account_by_id** — Get card account details. Get details about an existing card account. Required: id.
- **list_all_bill_card_accounts** — Get list of card accounts. Get a list of card account objects. Required: cardUserStatus.
- **create_a_bill_customer_attachment** — Upload customer attachment. Upload an attachment for an existing customer. The file size limit is 6 MB. Note: When you upload an attachment, it takes a few minutes for BILL to complete the upload process. See Documents and attachments in the Guides section for more information, sample requests, and responses. Send the file's bytes as the request body with truto_body_passthrough=true (Content-Type application/octet-stream) and its file name in name. Required: customer_id, name, file.
- **list_all_bill_customer_attachments** — Get list of customer attachments. Get a list of attachments associated with a customer. From the response, use downloadLink in a GET request to download the attachment. curl '{downloadLink}' --header 'sessionId: {session_id}' --output {attachment_name}. Required: customer_id. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **bill_customer_bank_accounts_archive** — Archive a customer bank account. Archive an existing customer bank account. In the response, the archived field is set as true. An archived customer bank account cannot be restored. Required: customer_id, bank_account_id.
- **create_a_bill_customer_bank_account** — Create a customer bank account. Create a new customer bank account. When you add customer bank account information, you can charge the customer for invoices. Creating a customer bank account follows a set of rules. Required: customer_id, nameOnAccount, routingNumber, accountNumber, type, ownerType.
- **get_single_bill_customer_bank_account_by_id** — Get customer bank account details. Get details about an existing customer bank account. Required: id, customer_id.
- **list_all_bill_customer_bank_accounts** — Get list of customer bank accounts. Get a list of customer bank account objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. Required: customer_id. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **update_a_bill_customer_bank_account_by_id** — Update a customer bank account. Update details about an existing customer bank account. You can update only the nickname and ownerType fields for a customer bank account. If you want to update any of the other fields, create a new customer bank account with POST /v3/customers/{customerId}/bank-accounts. Required: id, customer_id.
- **bill_customer_contacts_archive** — Archive a customer contact. Archive an existing customer contact. In the response, the archived field is set as true. You can restore an archived customer with POST /v3/customers/{customerId}/contacts/{contactId}/restore. There is no change when you archive an archived customer contact. Required: customer_id, contact_id.
- **create_a_bill_customer_contact** — Create a customer contact. Create a new customer contact. When you create a customer contact, BILL enables the customer to sign in to the BILL web app with the email value and a random password. The signed-in customer can view invoices, make payments, and manage their account. Required: customer_id, firstName, email.
- **get_single_bill_customer_contact_by_id** — Get customer contact details. Get details about an existing customer contact. Required: id, customer_id.
- **list_all_bill_customer_contacts** — Get list of customer contacts. Get a list of customer contact objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. Required: customer_id. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **bill_customer_contacts_restore** — Restore a customer contact. Restore an archived customer contact. In the response, the archived field is set as false. You can perform any valid BILL operation on restored customer contacts. There is no change when you restore a restored customer contact. Required: customer_id, contact_id.
- **update_a_bill_customer_contact_by_id** — Update a customer contact. Update details about an existing customer contact. Required: id, customer_id.
- **create_a_bill_customer_invitation** — Send connection request to a customer. Send a connection request to a customer organization in the BILL Network. BILL automatically connects the customer organization with the customer record in your BILL organization. Required: customer_id, networkId, networkType.
- **delete_a_bill_customer_invitation_by_id** — Delete customer connection. Delete an existing Network connection with a customer organization. Delete customer connection follows a set of rules. * No scheduled payments: There should be no scheduled payments. All scheduled payments must be canceled before you can disconnect. Required: id.
- **get_single_bill_customer_invitation_by_id** — Get customer connection request status. Get the status of an existing connection request sent with POST /v3/network/invitation/customer/{customerId}. When you send a connection request to a customer organization that has auto-connections enabled, BILL automatically connects you with the organization. Required: id.
- **list_all_bill_document_upload_statuses** — Get document upload status. Get status of a document upload. Use this endpoint to identify when a document upload is complete. * BILL generates an uploadId for the document when the upload is in progress (IN_PROGRESS). The value begins with 0du. Required: ids.
- **get_single_bill_document_by_id** — Get document details. Get details about a document associated with a bill. From the response, use downloadLink in a GET request to download the document. curl '{downloadLink}' --header 'sessionId: {session_id}' --output {document_name}. Required: id.
- **bill_employees_archive** — Archive an employee. Archive an existing employee. In the response, the archived field is set as true. Required: employee_id.
- **bill_employees_bulk_archive** — Archive multiple employees. Archive multiple employees with one API request. In the response, the archived field for each object is set as true. Required: ids.
- **bill_employees_bulk_create** — Create multiple employees. Create multiple employees with one API request. You can create up to 50 employees with one POST /v3/classifications/employees/bulk request.
- **bill_employees_bulk_restore** — Restore multiple employees. Restore multiple employees with one API request. In the response, the archived field for each object is set as false. Required: ids.
- **bill_employees_bulk_update** — Update multiple employees. Update details about multiple employees with one API request.
- **create_a_bill_employee** — Create an employee. Create a new employee. Required: firstName, lastName.
- **get_single_bill_employee_by_id** — Get employee details. Get details about an existing employee. Required: id.
- **list_all_bill_employees** — Get list of employees. Get a list of employee objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **bill_employees_restore** — Restore an archived employee. Restore an archived employee. In the response, the archived field is set as false. Required: employee_id.
- **update_a_bill_employee_by_id** — Update an employee. Update details about an existing employee. Required: id.
- **bill_exports_get_download_link** — Get exported record download URL. Get the download URL for an exported record file. From the response, use downloadLink in a GET request to download the file. curl '{downloadLink}' --output {file_name} See Export BILL records in the Guides section for more information, sample requests, and responses. Required: export_id.
- **list_all_bill_exports** — Get list of exported BILL records. Get a list of exported BILL records available for you to download. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **list_all_bill_funding_account_permissions** — Get funding account permissions. Get the funding account permissions available for the current organization and current organization user.
- **bill_items_archive** — Archive an item. Archive an existing item. In the response, the archived field is set as true. Required: item_id.
- **bill_items_bulk_archive** — Archive multiple items. Archive multiple items with one API request. In the response, the archived field for each object is set as true. Required: ids.
- **bill_items_bulk_create** — Create multiple items. Create multiple items with one API request. You can create up to 50 items with one POST /v3/classifications/items/bulk request.
- **bill_items_bulk_restore** — Restore multiple items. Restore multiple items with one API request. In the response, the archived field for each object is set as false. Required: ids.
- **bill_items_bulk_update** — Update multiple items. Update details about multiple items with one API request.
- **create_a_bill_item** — Create an item. Create a new item. Required: type, name.
- **get_single_bill_item_by_id** — Get item details. Get details about an existing item. Required: id.
- **list_all_bill_items** — Get list of items. Get a list of item objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **bill_items_restore** — Restore an archived item. Restore an archived item. In the response, the archived field is set as false. Required: item_id.
- **update_a_bill_item_by_id** — Update an item. Update details about an existing item. Required: id.
- **bill_jobs_archive** — Archive a job. Archive an existing job. In the response, the archived field is set as true. Required: job_id.
- **bill_jobs_bulk_archive** — Archive multiple jobs. Archive multiple jobs with one API request. In the response, the archived field for each object is set as true. Required: ids.
- **bill_jobs_bulk_create** — Create multiple jobs. Create multiple jobs with one API request. You can create up to 50 jobs with one POST /v3/classifications/jobs/bulk request.
- **bill_jobs_bulk_restore** — Restore multiple jobs. Restore multiple jobs with one API request. In the response, the archived field for each object is set as false. Required: ids.
- **bill_jobs_bulk_update** — Update multiple jobs. Update details about multiple jobs with one API request.
- **create_a_bill_job** — Create a job. Create a new job. Required: name.
- **get_single_bill_job_by_id** — Get job details. Get details about an existing job. Required: id.
- **list_all_bill_jobs** — Get list of jobs. Get a list of job objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **bill_jobs_restore** — Restore an archived job. Restore an archived job. In the response, the archived field is set as false. Required: job_id.
- **update_a_bill_job_by_id** — Update a job. Update details about an existing job. Required: id.
- **bill_network_invitations_accept** — Accept connection request. Accept a connection request sent by a vendor or customer. The organization receiving the connection request must have auto-connections disabled. If auto-connections are not disabled, BILL automatically connects the organizations in the BILL Network. Required: networkId, type.
- **list_all_bill_network_organizations** — Search for an organization in the BILL Network. Search for a customer, vendor, or verified national vendor organization. You can search in the BILL Network and verified national vendor (RPPS) network. When you search in the BILL Network, there are two name requirements for getting search results. Required: name.
- **list_all_bill_organization_industries** — Get list of organization industries. 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 or PATCH /v3/organizations/{organizationId} request.
- **get_single_bill_organization_price_plan_by_id** — Get organization price plan details. Get the BILL price plan details for an existing organization. The currently signed-in user must have the ADMINISTRATOR user role in the BILL organization to perform this operation. Required: id.
- **list_all_bill_pending_bill_approvals** — Get list of bills pending approval. Get a list of bills that are pending approval by a user. In the response, you get the list of bills that are pending approval for the currently signed-in user.
- **create_a_bill_receivable_payment** — Charge a customer. Charge a customer for one or more invoices. Charging a customer follows a set of rules. * Customer authorization: The customer authorizedToCharge field must be set as true for you to charge the customer for invoices. Required: customerId, fundingAccount, invoicePayments.
- **get_single_bill_receivable_payment_by_id** — Get received payment details. Get details about an existing received payment. Required: id.
- **list_all_bill_receivable_payments** — Get list of received payments. Get a list of received payment objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. See Search operations with lists in the Guides section for filtering, sorting, and pagination examples. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **list_all_bill_risk_verification_phone** — Get phone status for risk verification. Check whether a phone number has been added for the currently signed-in user. BILL requires the signed-in user to have a linked phone number for initiating risk verification for the organization.
- **bill_spend_budget_members_bulk_replace** — Update multiple budget members. Update details about multiple user members assigned to an existing budget. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: budget_id, members.
- **delete_a_bill_spend_budget_member_by_id** — Delete a budget member. Delete a user member from an existing budget. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id, budget_id.
- **get_single_bill_spend_budget_member_by_id** — Get budget member details. Get details about a user member assigned to an existing budget. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id, budget_id.
- **list_all_bill_spend_budget_members** — Get list of budget members. Get a list of user members assigned to an existing budget. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: budget_id. The connector pages with max / nextPage (limit = page size, up to 100); records at results.
- **update_a_bill_spend_budget_member_by_id** — Add or update a budget member. Add a new user member to an existing budget. You can also update details about an existing user member assigned to the budget. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id, budget_id.
- **create_a_bill_spend_budget** — Create a budget. Create a new budget for a company. See Budgets and Users in the Guides section for more information, sample requests, and responses. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: name, owners, recurringInterval.
- **delete_a_bill_spend_budget_by_id** — Delete a budget. Delete an existing budget. A deleted budget cannot be restored. The deleted budget is not available in the list of budgets. Note: * While you cannot restore a deleted budget with the API, you can unretire budgets in the BILL web app and mobile app. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **get_single_bill_spend_budget_by_id** — Get budget details. Get details about an existing budget. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **list_all_bill_spend_budgets** — Get list of budgets. Get a list of budget objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. The connector pages with max / nextPage (limit = page size, up to 100); records at results.
- **update_a_bill_spend_budget_by_id** — Update a budget. Update details about an existing budget. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **list_all_bill_spend_card_payments** — Get list of card payments. Get a list of payments made towards your card balance. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. The payments are for your company, which is determined by your authentication. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. The connector pages with max / nextPage (limit = page size, up to 100); records at results.
- **create_a_bill_spend_card** — Create a vendor card. Create a new vendor card. See Vendor cards in the Guides section for more information, sample requests, and responses. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: name, userId, budgetId.
- **delete_a_bill_spend_card_by_id** — Delete a vendor card. Delete an existing vendor card. A deleted card cannot be restored. The deleted card is not available in the list of cards. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **bill_spend_cards_freeze** — Freeze a vendor card. Freeze an existing vendor card. You can freeze virtual cards and physical cards. A frozen card cannot be used for payments. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: card_id.
- **get_single_bill_spend_card_by_id** — Get vendor card details. Get details about an existing vendor card. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **bill_spend_cards_get_pan_jwt** — Get a PAN JWT token. Get a JWT token for a vendor card. The JWT token for a card contains all the information required for retrieving details about the card (16-digit PAN, CVV, and expiration date). The JWT token lifespan is 5 minutes. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: card_id.
- **list_all_bill_spend_cards** — Get list of cards. Get a list of card objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. The connector pages with max / nextPage (limit = page size, up to 100); records at results.
- **bill_spend_cards_unfreeze** — Unfreeze a vendor card. Unfreeze an existing vendor card. You can unfreeze virtual cards and physical cards. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: card_id.
- **update_a_bill_spend_card_by_id** — Update a vendor card. Update details about an existing vendor card. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **list_all_bill_spend_credit_info** — Get credit info. Get the credit information of the current user's company. The response includes the total credit limit and, for each active card network program, the balance, the credit limit, and the available credit limit. All amounts are in dollars. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection.
- **list_all_bill_spend_current_user** — Get current user details. Get details about the current user. This is the user that generated the Spend & Expense API token. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection.
- **bill_spend_custom_field_values_bulk_delete** — Delete a custom field value. Delete an existing custom field value. A deleted value cannot be restored. The deleted value is not available in the list of custom field values. In addition, the deleted value cannot be assigned to current or future transactions. The deleted value will continue to be assigned to past transactions. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: custom_field_id, customFieldValueIds.
- **create_a_bill_spend_custom_field_value** — Create a custom field value. Create a new value for an existing custom field. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: custom_field_id, values.
- **get_single_bill_spend_custom_field_value_by_id** — Get custom field value details. Get details about an existing custom field value. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id, custom_field_id.
- **list_all_bill_spend_custom_field_values** — Get list of custom field values. Get a list of custom field value objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: custom_field_id. The connector pages with max / nextPage (limit = page size, up to 100); records at results.
- **create_a_bill_spend_custom_field** — Create a custom field. Create a new custom field. See Transactions in the Guides section for more information, sample requests, and responses. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: name, allowCustomValues.
- **delete_a_bill_spend_custom_field_by_id** — Delete a custom field. Delete an existing custom field. A deleted custom field cannot be restored. The deleted custom field is not available in the list of custom fields. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **get_single_bill_spend_custom_field_by_id** — Get custom field details. Get details about an existing custom field. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **list_all_bill_spend_custom_fields** — Get list of custom fields. Get a list of custom field objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. The connector pages with max / nextPage (limit = page size, up to 100); records at results.
- **update_a_bill_spend_custom_field_by_id** — Update a custom field. Update details about an existing custom field. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **create_a_bill_spend_reimbursement_receipt** — Add a reimbursement receipt. Add a receipt to an existing reimbursement. In the request, use the same upload url that you used to upload the receipt image. See Create a reimbursement upload URL to learn about creating a reimbursement image upload URL. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: reimbursement_id, url, filename.
- **delete_a_bill_spend_reimbursement_receipt_by_id** — Delete a reimbursement receipt. Delete a receipt from an existing reimbursement. A deleted receipt cannot be restored. The deleted receipt is not available in the reimbursement details. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id, reimbursement_id.
- **create_a_bill_spend_reimbursement_upload_url** — Create a reimbursement upload URL. Create a reimbursement image upload URL. From the response, use the upload url to upload a receipt image for the reimbursement. For example, to upload a JPEG image, use the following curl command. To upload a PNG image, set the content type as image/png. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection.
- **bill_spend_reimbursements_approve_deny** — Approve or deny a reimbursement. Approve or deny a reimbursement request. See Reimbursements in the Guides section for more information, sample requests, and responses. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: reimbursement_id, action.
- **create_a_bill_spend_reimbursement** — Create a reimbursement. Create a new reimbursement. See Reimbursements in the Guides section for more information, sample requests, and responses. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: userId, budgetId, amount, note, merchantName, occurredDate, receipts.
- **delete_a_bill_spend_reimbursement_by_id** — Delete a reimbursement. Delete an existing reimbursement. A deleted reimbursement cannot be restored. The deleted reimbursement is not available in the list of reimbursements. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **get_single_bill_spend_reimbursement_by_id** — Get reimbursement details. Get details about an existing reimbursement. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **list_all_bill_spend_reimbursements** — Get list of reimbursements. Get a list of reimbursement objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. The connector pages with max / nextPage (limit = page size, up to 100); records at results.
- **update_a_bill_spend_reimbursement_by_id** — Update a reimbursement. Update details about an existing reimbursement. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **list_all_bill_spend_transaction_custom_field_values** — Get list of transaction custom field values. Get a list of custom field value objects applied to an existing transaction. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: transaction_id, custom_field_id. The connector pages with max / nextPage (limit = page size, up to 100); records at results.
- **bill_spend_transaction_custom_fields_bulk_replace** — Update transaction custom fields. Update details about custom fields and their values applied to an existing transaction. You cannot update custom fields in a locked transaction. When a transaction is locked, isLocked is set as true. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: transaction_id, customFields.
- **list_all_bill_spend_transaction_custom_fields** — Get list of transaction custom fields. Get a list of custom field objects applied to an existing transaction. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: transaction_id.
- **create_a_bill_spend_transaction_receipt** — Add a transaction receipt. Add a receipt to an existing transaction. In the request, use the same upload url that you used to upload the receipt image. See Create a transaction upload URL to learn about creating a transaction image upload URL. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: transaction_id, url.
- **delete_a_bill_spend_transaction_receipt_by_id** — Delete a transaction receipt. Delete a receipt from an existing transaction. A deleted receipt cannot be restored. The deleted receipt is not available in the transaction details. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id, transaction_id.
- **create_a_bill_spend_transaction_upload_url** — Create a transaction upload URL. Create a transaction image upload URL. From the response, use the upload url to upload a receipt image for the transaction. For example, to upload a JPEG image, use the following curl command. To upload a PNG image, set the content type as image/png. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection.
- **get_single_bill_spend_transaction_by_id** — Get transaction details. Get details about an existing transaction. In the response, you get information about transactions, reversals, and refunds. * Transaction: For a standard transaction, the transactionType is set as AUTHORIZATION or DECLINE. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **list_all_bill_spend_transactions** — Get list of transactions. Get a list of transaction objects. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. In the response, you get information about transactions, reversals, and refunds. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. The connector pages with max / nextPage (limit = page size, up to 100); records at results.
- **bill_spend_transactions_respond_3_ds_challenge** — Accept or reject a transaction. Accept or reject a transaction 3D Secure (3DS) challenge. When a transaction is created, a 3DS challenge may trigger to verify the identity of the cardholder. Use this endpoint to approve or deny the transaction. The Spend & Expense user must have the ADMIN user role to perform this operation. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: acs_transaction_id, action.
- **update_a_bill_spend_transaction_by_id** — Update a transaction. Update the budget for an existing transaction. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id, budgetId.
- **create_a_bill_spend_user** — Create a user. Create a new user. See Budgets and Users in the Guides section for more information, sample requests, and responses. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: firstName, lastName, email, role.
- **delete_a_bill_spend_user_by_id** — Delete a user. Delete an existing user. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **get_single_bill_spend_user_by_id** — Get user details. Get details about an existing user. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **list_all_bill_spend_users** — Get list of users. Get a list of user objects in the current user's company. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. The connector pages with max / nextPage (limit = page size, up to 100); records at results.
- **update_a_bill_spend_user_by_id** — Update a user. Update details about an existing user. Spend & Expense: needs the OAuth client credentials connection, or a Spend & Expense API token on the username connection. Required: id.
- **create_a_bill_vendor_attachment** — Upload vendor attachment. Upload an attachment for an existing vendor. The file size limit is 6 MB. Note: When you upload an attachment, it takes a few minutes for BILL to complete the upload process. See Documents and attachments in the Guides section for more information, sample requests, and responses. Send the file's bytes as the request body with truto_body_passthrough=true (Content-Type application/octet-stream) and its file name in name. Required: vendor_id, name, file.
- **list_all_bill_vendor_attachments** — Get list of vendor attachments. Get a list of attachments associated with a vendor. From the response, use downloadLink in a GET request to download the attachment. curl '{downloadLink}' --header 'sessionId: {session_id}' --output {attachment_name}. Required: vendor_id. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **list_all_bill_vendor_audit_trail** — Get audit trail details for a vendor. Get audit trail details about changes made to a vendor object. The audit trail lists records for each create and edit operation. See Get audit trail details in the Guides section for more information, sample requests, and responses. Required: vendor_id. The connector pages with start / max (limit = page size, up to 100); records at the response array.
- **create_a_bill_vendor_invitation** — Send connection request to a vendor. Send a connection request to a vendor organization in the BILL Network. BILL automatically connects the vendor organization with the vendor record in your BILL organization. If the vendor organization has auto-connections disabled, BILL sends an invitation email to the vendor email address. Required: vendor_id, networkId, networkType.
- **delete_a_bill_vendor_invitation_by_id** — Delete vendor connection. Delete an existing Network connection with a vendor organization. Delete vendor connection follows a set of rules. * No scheduled payments: There should be no scheduled payments. All scheduled payments must be canceled before you can disconnect. Required: id.
- **get_single_bill_vendor_invitation_by_id** — Get vendor connection request status. Get the status of an existing connection request sent with POST /v3/network/invitation/vendor/{vendorId}. When you send a connection request to a vendor organization that has auto-connections enabled, BILL automatically connects you with the organization. Required: id.
- **bill_vendor_invitations_invite_by_email** — Send connection request to a vendor not in the BILL Network. Send a connection request to a vendor not in the BILL Network. BILL sends an invitation email to the provided vendor email address. When the vendor accepts the invitation and sets up a BILL account, BILL connects the vendor organization with the vendor record in your BILL organization. Required: vendor_id, email.
- **list_all_bill_webhook_event_catalog** — Get events catalog. Get the complete list of available events that you can subscribe to. See Webhooks in the Guides section for more information, sample requests, and notification payloads for BILL events. Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials).
- **list_all_bill_webhook_event_notifications** — Get list of event notifications. Get a list of event notifications sent to you for a subscription. You can use this endpoint to address any issues with notification retries. In the request, set createdTimeFrom and createdTimeTo to get event notifications for the specified time range. Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials). Required: subscription_id. The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **bill_webhook_event_notifications_resend** — Resend an event. Resend an existing event notification. Note: When an event notification fails, BILL tries to send the notification again with exponential backoff. See Webhooks in the Guides section for more information, sample requests, and notification payloads for BILL events. Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials). Required: subscription_id, event_id.
- **create_a_bill_webhook_subscription** — Create a subscription. Create a new event subscription. You can subscribe to multiple events with a single request. You can create up to 10 webhook subscriptions per organization. BILL provides a full catalog of all the events that you can subscribe to with GET /v3/events/catalog. Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials). Required: idempotent_key, name, status, events, notificationUrl.
- **bill_webhook_subscriptions_create_security_key** — Create a security key. Create a new security key for your subscription. When you create a new subscription, a one-time securityKey is one of the generated values in the response. All event notifications sent to your notificationUrl are signed with this key using the HMAC-SHA256 algorithm. Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials). Required: idempotent_key, subscription_id.
- **delete_a_bill_webhook_subscription_by_id** — Delete a subscription. Delete an existing subscription. Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials). Required: id.
- **get_single_bill_webhook_subscription_by_id** — Get subscription details. Get details about an existing subscription. Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials). Required: id.
- **list_all_bill_webhook_subscriptions** — Get list of subscriptions. Get a list of all your created subscriptions. By default, you get 20 results on one page of results. Set max in your request to get up to 100 results on one page. Note: In this list operation, pagination is available only in one direction. Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials). The connector pages with max / page (BILL's nextPage) (limit = page size, up to 100); records at results.
- **bill_webhook_subscriptions_partial_update** — Update a subscription. Update details about a subscription. You can use the PATCH operation to modify existing subscription details, such as name, status, and notificationUrl. PATCH beside the PUT update: the record id is a named query field (the connector passes {{id}} only to get / update / delete). Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials). Required: subscription_id.
- **bill_webhook_subscriptions_test** — Generate a test event notification. Generate a new test event notification. After you create a subscription, use this endpoint for BILL to send a test event notification to your specified notification URL. In your request, all the fields are optional. Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials). Required: subscription_id.
- **update_a_bill_webhook_subscription_by_id** — Replace a subscription. Update the events that you are subscribed to. You can use the PUT operation to add, remove, or replace events in a subscription. For example, you can replace the bill.created event with bill.updated in your subscription. Webhooks: BILL accepts only the username / developer key connection here (not OAuth client credentials). Required: id, name, status, events, notificationUrl.

## How it works

1. **Link your customer's BILL account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach BILL.** The Proxy API is a 1-to-1 mapping of the BILL API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Automate vendor payouts from your vertical SaaS platform** — If your platform manages workflows that end in paying vendors, contractors, or suppliers, integrating with Bill lets your users push approved payables directly into their Bill account for payment execution — no manual re-entry required.
- **Pull real-time AP data for cash flow forecasting** — FP&A and treasury tools need visibility into upcoming and outstanding payables. By reading Bills and Payments from your users' Bill accounts, you can power accurate cash burn forecasts and liquidity dashboards without asking users to export CSVs.
- **Sync procurement approvals into Bill for payment execution** — Procurement and spend intake platforms handle the request-and-approve workflow, but the actual money movement happens in Bill. Integrating lets your users seamlessly hand off fully coded bills to their finance team for final payment release.
- **Stage bills automatically from industry-specific workflows** — Practice management, construction, or property management SaaS platforms generate payable events as part of their core workflow. Pushing these as pre-coded Bills into your users' Bill accounts eliminates double-entry and accelerates payment cycles.
- **Issue invoices and track receivables through Bill's AR capabilities** — Subscription billing or usage-based billing platforms can create customer invoices in Bill's Accounts Receivable module, giving end users a low-friction ACH payment option and keeping AR data in sync with their general ledger.

## What you can build

- **One-click vendor creation and network lookup** — Automatically create vendors in your users' Bill accounts and leverage the Bill Network to skip manual bank detail collection when the vendor already exists.
- **Automated bill staging with document attachment** — Push fully coded bill line items along with the original invoice PDF into Bill so finance teams can review and approve without context-switching.
- **Payment status webhook listener** — Subscribe to Bill's payment status webhooks to reflect real-time statuses like Scheduled, Cleared, or Failed directly in your product's UI.
- **Accounts payable sync for cash flow dashboards** — Pull unpaid, scheduled, and historical bills and payments from Bill to build real-time cash position and burn rate visualizations.
- **Virtual card provisioning and budget controls** — Use Bill's Spend & Expense APIs to generate virtual cards for employees and enforce per-department or per-project spending limits from within your platform.
- **Embedded Bill workflows via Bill Elements** — Drop Bill's embeddable UI components into your product so users can complete approval and payment flows without leaving your application.

## FAQs

### What authentication method does the Bill API use?

Bill's v3 API uses OAuth 2.0 for authentication. Truto handles the full OAuth flow, token refresh, and credential storage so your team doesn't need to manage auth lifecycle per connected account.

### Is the Bill integration available as a prebuilt Unified API on Truto?

Bill is not yet mapped to a Truto Unified API. It is built on request — contact Truto to scope the integration, and the team will build and maintain the connector tailored to your use case.

### Does Bill support webhooks for real-time data updates?

Yes. Bill's v3 API supports webhooks for key events, most notably payment status changes (Scheduled, Cleared, Voided, Failed). This lets your application react in real time rather than polling.

### What are the core API objects available in Bill's v3 API?

The primary objects include Vendors, Bills, Payments, Documents, Customers, Invoices (AR), and Spend & Expense resources like virtual cards and budgets. These cover both AP and AR workflows.

### Are there rate limits on the Bill API?

Yes, Bill enforces rate limits on its v3 API. Truto manages request throttling, pagination, and retries on your behalf to ensure your integration stays within limits without dropped requests.

### Can I attach invoice documents when creating a Bill via the API?

Yes. Bill's v3 API has a dedicated documents endpoint that lets you upload PDFs or images and associate them with a Bill object, so finance teams see the source invoice alongside the coded payable.

## Related reading

- [Why Your Integration Bill Spikes with Connections, Records, and Compute Time](https://truto.one/blog/why-does-my-integration-platform-bill-spike-with-connections-records-and-compute-time/) — Diagnose why your integration infrastructure costs are scaling exponentially rather than linearly. Understand the hidden mechanics of usage-based pricing and stateful architectures.
- [Connect Bill to Claude: Manage Vendors, Invoices, and Audit Trails](https://truto.one/blog/connect-bill-to-claude-manage-vendors-invoices-and-audit-trails/) — Learn how to build a secure MCP server to connect Bill to Claude. Automate vendor onboarding, mass payments, and AP/AR workflows with AI agents.
- [Connect Bill to ChatGPT: Automate AP, AR, and Payment Approvals](https://truto.one/blog/connect-bill-to-chatgpt-automate-ap-ar-and-payment-approvals/) — Learn how to connect Bill to ChatGPT using a managed MCP server. Automate AP workflows, manage vendors, and execute mass payments securely via natural language.
- [Connect Bill to AI Agents: Sync Payments, Bills, and Financial Data](https://truto.one/blog/connect-bill-to-ai-agents-sync-payments-bills-and-financial-data/) — Learn how to connect Bill to AI agents using Truto's /tools endpoint. Build autonomous financial workflows to sync payments, manage bills, and automate AP/AR.
- [Connect DingConnect to ChatGPT: Automate Global Top-Ups & Bill Pay](https://truto.one/blog/connect-dingconnect-to-chatgpt-automate-global-top-ups-bill-pay/) — Learn how to build a production-ready DingConnect MCP server to connect ChatGPT to global top-up, bill payment, and telecom transfer APIs.
