Can I react to BILL activity in real time?

Yes. The Connect Events API lets you subscribe to platform events such as approval state changes and customer updates, delivered as signed callbacks to your endpoint. You can verify a subscription with a test-event delivery and rotate the per-subscription security key as part of routine credential hygiene.

Which BILL API sets up the general ledger structure?

The Organization Accounts Tracking API manages the chart of accounts, accounting classes, departments, items, jobs, locations, and payment terms. These dimensions must exist before invoices and bills on the other APIs can be coded to the correct ledger account and cost centre.

BILL APIs for AI Agents

Q: Can an agent enforce approval controls before money moves?

Yes. The Approvals API defines approval policies and sets approvers on bills and vendor credits, and an item can be approved or denied before the vendor transactions API runs a payment batch. This lets a workflow gate payments behind the right routing rather than paying immediately.

FinanceAccountingContact ManagementJentic-Generated SpecsAPI keyAgent Ready

www.bill.com·Developer portal → developer.bill.com

BILL API Catalog

9 APIs across 4 product groups. All share one credential.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the BILL platform by hand means logging in for a session ID, pairing it with your developer key on every RPC-style POST, and shaping each bill, invoice, and record body yourself across nine separate surfaces. With Jentic you install Jentic One once, add the BILL APIs you need from the Jentic directory, store the credentials once, and your agent calls them.

Permission scoping

Most BILL operations carry their identifiers in the request body rather than the URL path, so you scope the agent by choosing which operations it may call. Your own rules in your Jentic One instance decide the set, so money-moving actions like PayBills, ChargeCustomer, or Approve are not reachable unless you include them.

Credential isolation

FAQs

Specific to using BILL APIs through Jentic.

Do all of BILL's APIs share one login?

Yes. You authenticate once against the BILL Authentication API with a developer key, organisation ID, username, and password to obtain a session ID, and that same session ID is carried on every other BILL v2 call across accounts payable, accounts receivable, organisation administration, and approvals. The Connect Events gateway uses the same BILL credential model.

Why does Jentic publish these specs when BILL does not?

BILL documents its v2 API in narrative form on its developer site but does not publish OpenAPI documents. Jentic generates and maintains a structured OpenAPI specification for each BILL surface so agents and developers can call them through tooling, and validates each one against the live API.

How do accounts payable and accounts receivable fit together here?

The vendor management and vendor transactions APIs cover the AP side, onboarding vendors and paying bills, while the customer management and customer transactions APIs cover the AR side, holding customer records and issuing invoices. The accounts tracking API supplies the shared chart of accounts and dimensions that both sides code transactions against.

Can an agent enforce approval controls before money moves?

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo

For Agents

APIs9 in catalogue

Endpoints270 indexed

AuthAPI key — 1 credential for all 9 APIs

ProvenanceJentic-generated specs

Across BILL's APIs an agent can log in for a session, onboard vendors and customers, raise vendor bills and run payment batches, issue customer invoices and collect payments, route items through approval policies, set up the chart of accounts and tracking dimensions, administer users and read bank balances, and subscribe to platform events. It covers the full accounts payable and accounts receivable loop from master data through to reconciliation.

BILL unifies accounts payable and accounts receivable on one platform, so vendors, customers, bills, invoices, approvals, and general-ledger coding all share a single session-based v2 API rather than living in separate systems. Its ACH payment runs and multi-stage approval routing suit B2B finance teams that need money movement and controls together, not just invoice generation.

Use for: Automating BILL accounts payable and accounts receivable: onboarding vendors and customers, raising and paying bills, issuing and collecting invoices, routing approvals, coding transactions to the general ledger, and subscribing to platform events.

Not supported: general ledger bookkeeping, bank feed reconciliation, payroll processing, expense report management, card issuing, tax filing

Credentials: One credential set covers all of these APIs: a developer key plus a session ID obtained from the BILL Authentication API, with the same session working across every other BILL v2 surface (the Connect Events gateway uses the same BILL credential model).

Which BILL API should I use?

I want to...	Use	Why
Record vendor bills, run payment batches, and reconcile AP	AP \| Vendor transactions	Vendor transactions raises bills and pays them; vendor management only holds the vendor master data those bills reference.
Onboard a vendor and attach bank account details	AP \| Vendor management	Vendor management creates the vendor and VendorBankAccount records that must exist before vendor transactions can bill or pay them.
Issue customer invoices, charge customers, and record AR payments	AR \| Customer transactions	Customer transactions runs the AR invoicing and collection flow; customer management only holds the customer, contact, and bank account records.
Create or update customer, contact, and bank account records	BILL Customer Management API	Customer management owns AR master data CRUD; customer transactions consumes those records when invoicing.
Set up the chart of accounts and cost-coding dimensions	Organization \| Accounts tracking	Accounts tracking defines the GL accounts, classes, and departments; basic operations handles users, documents, and bank balances instead.
Provision users, read bank balances, or fetch documents	Organization \| Basic operations	Basic operations administers the workspace itself; accounts tracking handles ledger dimensions, not user or bank administration.

Install Jentic One Beta

Connect the BILL APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BILL APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbill.com" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbill.com" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Once connected, ask your agent something like: “automate accounts payable and receivable in BILL”.

What AI Agents Can Do with BILL

Each workflow spans multiple BILL APIs. Jentic routes each operation to the right API automatically.

End-to-end vendor onboarding and payment

Onboard a vendor with its bank account details, then raise a bill and run the payment batch against it. The vendor and VendorBankAccount records are created first, then bills are recorded and paid, so ACH runs land at the right destination.

Example prompt:

Call Crud/Create/Vendor.json and Crud/Create/VendorBankAccount.json, then Crud/Create/Bill.json and PayBills.json for that vendor

APIs used

AP | Vendor management + AP | Vendor transactions

Approval-gated bill payment

Route a new bill through an approval policy before it is paid. Approvers are set on the bill, the item is approved, and only then is the payment run executed, keeping AP controls enforced end to end.

Example prompt:

Call Crud/Create/Bill.json, SetApprovers.json and Approve.json, then PayBills.json once the bill is approved

APIs used

AP | Vendor transactions + BILL Approvals API

CRM-to-AR invoicing

Sync a customer from an external CRM into BILL, then issue and collect an invoice against it. The customer and contact records are created first, then an invoice is raised, sent, and settled with a recorded AR payment.

Example prompt:

Call Crud/Create/Customer.json and Crud/Create/CustomerContact.json, then Crud/Create/Invoice.json, SendInvoice.json, and RecordARPayment.json

APIs used

BILL Customer Management API + AR | Customer transactions

Authenticated session with real-time event delivery

Establish a BILL session, then subscribe to platform events so downstream systems react as bills are approved or customers change. The login issues the session every other call needs, and a Connect Events subscription pushes signed callbacks.

Example prompt:

Call Login.json for a session, then POST /v3/subscriptions and POST /v3/subscriptions/{subscriptionId}/test to verify delivery

APIs used

BILL Authentication API + BILL Connect Events API

BILL APIs for AI Agents

BILL API Catalog

Finance6

CRM1

Developer Tools1

Identity Auth1

Why Jentic?

FAQs

Start Connecting APIs to Your AI Agents

Which BILL API should I use?

Connect the BILL APIs to your agent

What AI Agents Can Do with BILL

If you need a different Finance vendor