Bill APIs

10 APIs310 Endpoints4 Categories

API Catalog(7 of 10)

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 endpoints

AP | 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 endpoints

AR | 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.

40 endpoints

AR | Customer transactions

Jentic publishes the only available OpenAPI specification for AR | Customer transactions, keeping it validated and agent-ready. The BILL main bundle exposes the Accounts Receivable surface that automates how an organisation invoices customers and collects what is owed. 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. Invoice credits, received payments, conversion fees, and a top-line AR summary are also exposed for reconciliation.

40 endpoints

BILL Approvals API

Jentic publishes the only available OpenAPI specification for BILL Approvals API, keeping it validated and agent-ready. The Approvals API on BILL's accounts payable platform models approval policies and approver assignments for bills and vendor credits, exposing single and bulk CRUD plus dedicated approve, deny, set-approvers, and clear-approvers actions. Endpoints are POST-style /Crud and /List operations consistent with the v2 BILL API. Use it to codify multi-stage approval routing for accounts payable workflows.

28 endpoints

Organization | Accounts tracking

Jentic publishes the only available OpenAPI specification for Organization | Accounts tracking, keeping it validated and agent-ready. This BILL surface manages the accounting dimensions an organisation uses to classify every transaction: chart of accounts, accounting classes, departments, employees, items, jobs, locations, and payment terms. Agents create, update, and bulk-load these tracking entities so that invoices, bills, and payments downstream can be coded against the correct ledger, cost centre, and project. Without this layer, AR and AP records cannot be reconciled to the underlying accounting system.

74 endpoints

Organization | Basic operations

Jentic publishes the only available OpenAPI specification for Organization | Basic operations, keeping it validated and agent-ready. This BILL surface manages the foundational records of an organisation: the organisation itself, its users and profiles, attached documents, internal messages, bank accounts, money-movement records, and card accounts. Agents use it to provision users, read profiles and permissions, fetch documents attached to transactions, and inspect bank balances and money-movement history. It is the administrative spine that supports every AP and AR workflow.

25 endpoints

Connect Your Agent

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 | sh

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 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.