Bill AP | Vendor management
Browse all Bill APIs★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey16 EndpointsREST
For Agents
Onboard vendors, attach their bank account details, and keep vendor records in sync with the procurement system inside BILL.
Use for: I need to onboard a new vendor in BILL, I want to bulk-import vendors from our procurement system, Add a bank account to an existing vendor for ACH payments, Update a vendor's address and tax-ID details
Not supported: Does not handle bills, payment runs, or customer invoicing — use for vendor master data and vendor bank account setup only.
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.
Install Jentic One Beta
Connect the AP | Vendor management to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AP | Vendor management, 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.
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.
Capabilities
What an agent can do with AP | Vendor management API.
Create and update vendor records individually or in bulk batches
Soft-delete and undelete vendors to preserve historical AP audit trail
Attach vendor bank accounts that drive ACH payment routing
List vendors and vendor bank accounts for reconciliation against the master data source
Read individual vendor and vendor bank account records by ID for downstream automation
Use Cases
Patterns agents use AP | Vendor management API for, with concrete tasks.
★ Vendor onboarding from procurement
Sync new vendors from a procurement system into BILL the moment a master record is approved. The API exposes Crud/Create/Vendor and Bulk/Crud/Create/Vendor so an agent can mirror Coupa or NetSuite vendor data into BILL ahead of the first bill being raised. This removes the manual data-entry step that often delays vendor go-live.
Call Bulk/Crud/Create/Vendor.json with 20 vendor records exported from procurement, then call List/Vendor to confirm they are active
Vendor bank account attachment
Attach the correct bank account to each vendor so ACH payment runs land at the right destination. The API exposes Crud/Create/VendorBankAccount and Bulk/Crud/Create/VendorBankAccount for batch loads, plus Crud/Read and List variants for verification. Useful when finance ops needs to validate vendor banking before a payment run.
Call Crud/Create/VendorBankAccount.json for vendor ID 0vd01AAAAA with the routing and account numbers from the vendor portal, then verify with Crud/Read/VendorBankAccount
Vendor master data audit
Audit the full vendor list against an external source of truth such as the ERP. Calling List/Vendor returns active vendors and their key attributes, while List/VendorBankAccount returns the banking detail. An agent can flag mismatches and call Crud/Update/Vendor or Crud/Delete/Vendor to remediate.
Call List/Vendor and List/VendorBankAccount, then identify vendors whose banking detail is missing
Soft-delete and restoration
Retire vendors that are no longer active without breaking the AP audit trail. Crud/Delete/Vendor performs a soft delete that hides the vendor from new bill creation but preserves the historical record. Crud/Undelete/Vendor restores a vendor if a relationship resumes.
Call Crud/Delete/Vendor for vendor ID 0vd02AAAAA, then verify with Crud/Read/Vendor that the record is marked inactive
Agent-driven vendor onboarding via Jentic
An AI agent uses Jentic to discover vendor operations from intents like 'onboard a vendor in BILL'. Jentic returns the matching Crud/Create/Vendor operation, loads its schema, and executes with credentials from the vault. The agent can stand up a vendor record plus its bank account in two chained calls.
Search Jentic for 'onboard a vendor in bill.com', load the Crud/Create/Vendor schema, and execute it for vendor 'Acme Supplies Ltd'
Key Endpoints
16 endpoints — jentic publishes the only available openapi specification for ap | vendor management, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/Crud/Create/Vendor.json
Create a vendor record
POST
/Bulk/Crud/Create/Vendor.json
Bulk create vendor records
POST
/Crud/Update/Vendor.json
Update a vendor record
POST
/List/Vendor.json
List vendor records
POST
/Crud/Delete/Vendor.json
Soft-delete a vendor
POST
/Crud/Create/VendorBankAccount.json
Attach a bank account to a vendor
POST
/Crud/Read/VendorBankAccount.json
Read a vendor bank account
POST
/List/VendorBankAccount.json
List vendor bank accounts
POST
/Crud/Create/Vendor.json
Create a vendor record
POST
/Bulk/Crud/Create/Vendor.json
Bulk create vendor records
POST
/Crud/Update/Vendor.json
Update a vendor record
POST
/List/Vendor.json
List vendor records
POST
/Crud/Delete/Vendor.json
Soft-delete a vendor
POST
/Crud/Create/VendorBankAccount.json
Attach a bank account to a vendor
POST
/Crud/Read/VendorBankAccount.json
Read a vendor bank account
POST
/List/VendorBankAccount.json
List vendor bank accounts
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Vendor banking detail is sensitive data. 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 enumerate vendor bank accounts.
Intent-based discovery
Agents search intents like 'onboard a vendor' or 'add a vendor bank account' and Jentic returns the matching Crud/Create operation with its input schema, so the agent does not need to read BILL's developer portal.
Time to first call
Direct BILL integration: 1-2 days to model the vendor + bank account pair with bulk variants. Through Jentic: under 20 minutes to the first vendor created.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AP | Vendor management API through Jentic.
Why is there no official OpenAPI spec for AP | Vendor management?
BILL does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AP | Vendor management 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 Management API use?
BILL uses an API key plus session token model. Agents authenticate 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 to the agent.
Can I bulk-import vendors with this API?
Yes. POST /Bulk/Crud/Create/Vendor.json accepts a batch of vendor records in one call. POST /Bulk/Crud/Create/VendorBankAccount.json does the same for banking detail, which is faster than serial creates when migrating from another AP system.
How do I add a vendor bank account through Jentic?
Search Jentic for 'add a vendor bank account in bill.com'. Jentic returns the Crud/Create/VendorBankAccount operation, loads its schema, and your agent calls POST /Crud/Create/VendorBankAccount.json with the vendor ID, routing number, and account number.
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/Vendor.json over looped single-create calls during a vendor migration.
Is the AP Vendor Management 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.
GET STARTED