Bill APIs
10 APIs310 Endpoints4 Categories
Categories
API Catalog
AP | Vendor management
Jentic publishes the only available OpenAPI specification for AP | Vendor management, keeping it validated and agent-ready. This BILL surface manages the vendors an organisation pays and the bank accounts attached to those vendors. Agents create, update, and bulk-load Vendor records, soft-delete or restore them to preserve audit trail, and add or remove the VendorBankAccount records that determine where ACH payments land. It is the prerequisite layer for every AP payment workflow.
16 endpointsAP | Vendor transactions
Jentic publishes the only available OpenAPI specification for AP | Vendor transactions, keeping it validated and agent-ready. This BILL surface runs the Accounts Payable side of the platform: agents create purchase orders, raise one-off and recurring bills, issue vendor credits, kick off payment runs, record AP payments, and pull the AP summary for cash-flow reporting. Endpoints also expose payment cancel, void, FX rate quotes, sent-pay records, BillPay items, and disbursement and check image data for downstream reconciliation.
45 endpointsAR | Customer transactions
Jentic publishes the only available OpenAPI specification for AR | Customer transactions, keeping it validated and agent-ready. The BILL Accounts Receivable API automates how an organisation invoices and collects payments from its customers. Agents can create one-off and recurring invoices, issue credit memos, send invoices by email or postal mail, charge authorised customers, and record received payments back into the BILL ledger. The API also surfaces invoice credits, received payments, processing fees, and an AR summary so agents can reconcile cash-flow positions against accounting records.
Connect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.