AP | Vendor transactions

Name: AP | Vendor transactions API
Brand: AP | Vendor transactions
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey45 EndpointsREST

For Agents

Raise vendor bills, run payment batches, record and reconcile AP payments, and pull the AP summary inside BILL.

Quickstart

Get started with AP | Vendor transactions in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"pay open bills in bill.com"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AP | Vendor transactions API.

Create purchase orders, one-off bills, and recurring bills with bulk variants for batch loads

Issue, read, and list vendor credits to offset future payments

Run vendor payment batches via PayBills and record, cancel, or void AP payments

Fetch FX rate quotes for cross-currency payment runs

GET STARTED

Start building with AP | Vendor transactions API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AP | Vendor transactions, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use AP | Vendor transactions API for, with concrete tasks.

★ Automated AP payment runs

Batch up approved bills and pay them in one operation while keeping the ledger in sync. The API exposes Crud/Create/Bill for raising bills, PayBills for the run itself, and RecordAPPayment to mark each bill paid. CancelAPPayment and VoidAPPayment cover the exception paths when a payment must be reversed before it clears.

Call PayBills.json with an array of bill IDs and the source bank account, then call RecordAPPayment for each returned payment confirmation

Recurring bill scheduling

Set up RecurringBill schedules for predictable expenses such as rent, SaaS subscriptions, and retainers. Crud/Create/RecurringBill creates the schedule, Crud/Update/RecurringBill changes the cadence or amount, and List/RecurringBill enumerates active schedules. Each cycle generates a Bill that the agent can pay via PayBills.

Create a RecurringBill for vendor 0vd01AAAAA at $2,500 monthly with a 12-month duration, then list active RecurringBills to confirm the schedule

Vendor credit and cancellation handling

Issue vendor credits when an overpayment, return, or pricing correction occurs and reverse mistaken payments before they clear. The API exposes Crud/Create/VendorCredit and List/BillCredit for credit handling, plus CancelAPPayment and VoidAPPayment to abort an in-flight payment. This keeps the AP ledger accurate without manual UI rework.

Issue a $150 VendorCredit against vendor 0vd01AAAAA, then call CancelAPPayment for a pending payment that referenced the disputed bill

AP reporting and reconciliation

Pull the AP summary, sent-pay history, and check image data into a finance dashboard. GetAPSummary returns aggregate open balances, ListPayments and List/SentPay enumerate completed disbursements, and GetCheckImageData and GetDisbursementData support audit drill-downs. Useful for finance agents producing weekly cash-flow briefs.

Call GetAPSummary and ListPayments for the last 30 days, then return a list of payments over $10,000 with their disbursement IDs

Agent-driven AP automation via Jentic

An AI agent uses Jentic to discover vendor-transaction operations from intents like 'pay our open bills' or 'record a vendor invoice'. Jentic returns the matching operation, loads its schema, and executes with credentials from the vault. The agent can chain Create/Bill + PayBills + RecordAPPayment without ever holding raw BILL session tokens.

Search Jentic for 'pay open bills in bill.com', load the PayBills schema, and execute it for the three open bills due this week

Key Endpoints

45 endpoints — jentic publishes the only available openapi specification for ap | vendor transactions, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/Crud/Create/Bill.json

Create a vendor bill

POST

/Bulk/Crud/Create/Bill.json

Bulk create vendor bills

POST

/Crud/Create/RecurringBill.json

Create a recurring bill schedule

POST

/PayBills.json

Run a vendor payment batch

POST

/RecordAPPayment.json

Record an AP payment

POST

/CancelAPPayment.json

Cancel a pending AP payment

POST

/Crud/Create/VendorCredit.json

Issue a vendor credit

POST

/GetAPSummary.json

Retrieve consolidated AP summary

POST

/Crud/Create/Bill.json

Create a vendor bill

POST

/Bulk/Crud/Create/Bill.json

Bulk create vendor bills

POST

/Crud/Create/RecurringBill.json

Create a recurring bill schedule

POST

/PayBills.json

Run a vendor payment batch

POST

/RecordAPPayment.json

Record an AP payment

Why though Jentic?

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

Credential isolation

This API can move money via PayBills, so credential handling matters more than usual. Jentic keeps the BILL session token encrypted in the vault and only releases a scoped reference at execution time, so a leaked agent context cannot drain a payment account.

Intent-based discovery

Agents search intents like 'pay our open bills' or 'record a vendor invoice' and Jentic returns the matching operation with its input schema, removing the need to read BILL's developer portal.

Time to first call

Direct BILL integration: 4-7 days to handle bill creation, payment runs, error handling, and the cancel/void flows. Through Jentic: under 90 minutes to the first bill paid.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

BILL AP Vendor Management

Vendors must exist in BILL before bills can be raised against them.

Use vendor-management to onboard the vendor and bank account first; then use vendor-transactions to bill and pay.

Alternative

Xero Accounting

Xero handles AP at the ledger level for smaller businesses.

Choose Xero when the books are the system of record and bills are simple; choose BILL when ACH payment runs and approval workflows matter.

Complementary

BILL Organization Accounts Tracking

Tracking dimensions code each bill to the GL.

Use accounts-tracking to ensure GL accounts and departments exist before raising bills coded against them.

FAQs

Specific to using AP | Vendor transactions API through Jentic.

Why is there no official OpenAPI spec for AP | Vendor transactions?

BILL does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AP | Vendor transactions via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Vendor Transactions API use?

BILL uses an API key plus session token model. Agents log in once to obtain a session token and pass it on each call alongside the developer key. Jentic stores both encrypted in the vault and exposes only a scoped reference, which matters because this API can move money via PayBills.

Can I run a vendor payment batch through this API?

Yes. Call POST /PayBills.json with the array of bill IDs and the source bank account. Pair with POST /RecordAPPayment.json to mark each bill paid in BILL, and POST /CancelAPPayment.json or POST /VoidAPPayment.json to reverse a payment before it clears.

How do I record a new bill through Jentic?

Search Jentic for 'record a vendor bill in bill.com'. Jentic returns the Crud/Create/Bill operation, loads its schema, and your agent calls POST /Crud/Create/Bill.json with the vendor ID, line items, and due date. Use POST /Bulk/Crud/Create/Bill.json for batch loads from an OCR pipeline.

What rate limits apply to this API?

BILL applies per-organisation throttling. Specific quotas are not exposed in the spec, so prefer POST /Bulk/Crud/Create/Bill.json over looped single-creates and batch bill IDs into one POST /PayBills.json call instead of calling once per bill.

Is the AP Vendor Transactions API free?

API access is bundled with paid BILL plans rather than a separate free tier. You need an active BILL organisation and a developer key. Jentic does not add usage charges on top.