BILL Approvals API

Name: BILL Approvals API
Brand: BILL Approvals API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey28 EndpointsREST

Install Jentic One Beta

Connect the BILL Approvals API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BILL Approvals API, 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://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.

Capabilities

What an agent can do with BILL Approvals API.

Create and update approval policies via /Crud/Create/ApprovalPolicy.json

Bulk-create or bulk-update approval policies in one call

Assign approvers to a policy through /Crud/Create/ApprovalPolicyApprover.json

GET STARTED

Start building with BILL Approvals API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use BILL Approvals API for, with concrete tasks.

★ Multi-Stage Bill Approval Routing

Finance teams enforce approval thresholds - junior approver under $5k, manager up to $25k, controller above. The Approvals API lets the integration codify this through ApprovalPolicy and ApprovalPolicyApprover records, then attach the right policy to each bill via /SetApprovers.json. Approvers act on items with /Approve.json or /Deny.json, and /ListUserApprovals.json powers an inbox view.

Call POST /SetApprovers.json with the bill objectId and ordered approver IDs, then notify each approver and surface /ListUserApprovals.json in their inbox

Approval Policy Bulk Maintenance

When the AP team reorganizes - new departments, role changes, or quarterly delegation updates - the integration syncs the new approver matrix without manual rework. /Bulk/Crud/Update/ApprovalPolicy.json and /Bulk/Crud/Update/ApprovalPolicyApprover.json apply the changes in single calls, while the Undelete endpoints recover policies that were retired prematurely.

Call POST /Bulk/Crud/Update/ApprovalPolicyApprover.json with the new approver list per policy after the org update

Approver Inbox Automation

Approvers want a one-screen view of everything waiting on their decision. /ListUserApprovals.json returns the pending items for the current session user, and /Approve.json or /Deny.json acts on each. Combined with /Crud/Read/BillApprover.json the integration can show full bill context including the policy that routed it before the user clicks approve.

Call /ListUserApprovals.json, render the items, and call /Approve.json with the chosen objectId on user click

Agent-Driven Approval Actions via Jentic

An AI controller-assistant connected through Jentic answers 'approve invoice INV-2207 for Acme' by searching for the approve action, loading the BILL /Approve.json operation, and executing it with the bill's objectId. Through Jentic the BILL session credentials sit in the vault, and the agent never sees the raw devKey or session ID. The same flow extends to deny and set-approver actions.

Search Jentic for 'approve a bill in BILL', load /Approve.json, execute with objectId for INV-2207

Key Endpoints

28 endpoints — jentic publishes the only available openapi specification for bill approvals api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/Crud/Create/ApprovalPolicy.json

Create an approval policy

POST

/Crud/Create/ApprovalPolicyApprover.json

Add an approver to a policy

POST

/SetApprovers.json

Set approver list on a bill or vendor credit

POST

/ClearApprovers.json

Clear approver list on a bill or vendor credit

POST

/Approve.json

Approve a pending item

POST

/Deny.json

Deny a pending item

POST

/ListUserApprovals.json

List approvals waiting on a user

POST

/GetAllBillApproverPolicy.json

List all bill approver policies

POST

/Crud/Create/ApprovalPolicy.json

Create an approval policy

POST

/Crud/Create/ApprovalPolicyApprover.json

Add an approver to a policy

POST

/SetApprovers.json

Set approver list on a bill or vendor credit

POST

/ClearApprovers.json

Clear approver list on a bill or vendor credit

POST

/Approve.json

Approve a pending item

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your BILL developer key and session id are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'set approvers on a bill' or 'list a user's approvals', and Jentic returns the matching BILL Approvals operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using BILL Approvals API through Jentic.

Why is there no official OpenAPI spec for BILL Approvals API?

BILL documents its v2 API in narrative form on developer.bill.com but does not publish the underlying OpenAPI document. Jentic generates and maintains a structured OpenAPI specification so AI agents and developers can call BILL Approvals API via tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the BILL Approvals API use?

BILL's v2 API uses a session-based scheme: callers authenticate against the BILL Authentication API to obtain a session ID, which is then passed alongside a developer key on each subsequent call. Through Jentic, the developer key and session lifecycle are managed inside the vault and auto-attached to outbound calls.

Can I approve or deny a bill through this API?

Yes. POST /Approve.json with the bill or vendor credit objectId moves it forward in the workflow, and POST /Deny.json rejects it. Use /SetApprovers.json beforehand to make sure the right routing is attached, and /ClearApprovers.json to reset routing when a bill is being reissued.

What are the rate limits for the BILL Approvals API?

BILL applies platform-wide rate limits at the v2 API gateway rather than per-endpoint, and the Approvals surface inherits those limits. For end-of-month pushes, prefer the bulk endpoints (/Bulk/Crud/Create/ApprovalPolicy.json, /Bulk/Crud/Update/ApprovalPolicyApprover.json) over single-item loops to stay well under the cap.

How do I approve a bill through Jentic?

Run `pip install jentic`, then `await client.search('approve a bill in BILL')`, `await client.load(...)` for /Approve.json, and `await client.execute(...)` with the bill objectId. Jentic injects the BILL devKey and session credentials from the vault.

How do I list everything waiting on the current user's approval?

POST /ListUserApprovals.json returns the items pending for the authenticated session user. Pair with /Crud/Read/BillApprover.json or /Crud/Read/VendorCreditApprover.json to enrich each item with the policy and approver chain that routed it.

Can I limit what my agent is allowed to do with the BILL Approvals API?

Yes. Because Jentic One is self-hosted, you decide which BILL Approvals operations your agent may call and which credentials it uses, and your own rules are enforced at execution time. Since the API identifies bills and policies in the request body of its RPC-style POST calls rather than in the URL, you scope access at the operation level, allowing only what the agent needs such as /ListUserApprovals.json or /SetApprovers.json. Approve.json and Deny.json stay out of reach unless you explicitly include them in the allowed set.

BILL Approvals API

Connect the BILL Approvals API to your agent

Capabilities

Start building with BILL Approvals API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs