What API2Cart Is Evaluating for BILL Integration
Candidate data flow
Commerce-related invoices and payment status shared with finance workflows. The final entity and method list will be based on verified vendor API capabilities rather than assumptions.
Operational outcome
The intended workflow is to coordinate receivables without confusing orders with settled payments. Record ownership and idempotency would be defined before write operations are enabled.
Accounting safeguards
The connector would need to preserve vendor, customer, approval, and remittance context. Orders, invoices, payments, refunds, settlements, and journal entries would not be treated as interchangeable records.
Develop Integrations Faster and Save Up to 9x on Costs
Trusted by
What We Know About BILL So Far
Based on BILL’s own documentation and API2Cart’s discovery process — not a promise of a release date.
API & Integration. BILL offers two API generations: v2 REST, now in long-term-support/legacy mode, authenticated via userName/password/orgId/devKey to obtain a sessionId used on subsequent calls; and v3 REST, which BILL recommends for all new builds and which uses a similar login-to-sessionId model (with a separate apiToken header scheme for the Spend & Expense API). Published limits include 20,000 requests/hour per developer key, a concurrent-request cap of 3 per organization, and a 200/hour cap on login calls; webhooks are supported across AP, AR, and spend events (up to 10 subscriptions per organization), and an isolated sandbox environment with synthetic data is available separate from production.
Is this integration live yet? No. BILL integration is not live yet. Authentication, entities, fields, write operations, webhooks, limits, regional availability, and release timing remain subject to technical discovery and customer demand.
What’s the integration challenge? Engineering discovery must review partner access, API eligibility, payment security, and webhook semantics. Unsupported objects or operations would remain outside the published scope.
How is a release decided? Roadmap evaluation includes API maturity, sandbox access, accounting correctness, customer demand, maintenance cost, data residency, rate limits, and overlap with existing connectors. The page records an integration candidate; it does not promise a release date.
Technical validation. Engineering discovery must review partner access, API eligibility, payment security, and webhook semantics. Unsupported objects or operations would remain outside the published scope.
Primary sources: Official history or company background · BILL official website · Official developer or product documentation
Related planned integrations: BlackLine integration · Deskera Books integration · ZipBooks integration · Patriot Accounting integration
Interested in BILL Integration?
Let us know you’re interested, and we’ll notify you as soon as BILL support becomes available.
