Developers
An accounting API you already know.
Request and response bodies follow the public QuickBooks Online v3 API shapes, so existing QBO client code maps over with little change.
GET /v3/company/{realmId}/invoice/1042
Authorization: Bearer <access token>
{
"Invoice": {
"Id": "1042",
"SyncToken": "0",
"CustomerRef": { "value": "58", "name": "Alder Street Market" },
"TotalAmt": 906.00,
"Balance": 906.00,
"Line": [ ... ]
}
}What you get
Familiar shapes. Stricter books.
QBO v3 conventions
PascalCase fields, value/name references, SyncToken, sparse updates, QueryResponse lists and Fault errors.
Core entities
Accounts, customers, items, invoices, payments and journal entries, plus reports such as the trial balance.
Integrity by default
Balanced, append-only journal entries and per-company isolation are enforced in the database, so a buggy integration cannot unbalance the books.
Endpoints
A clean, predictable surface.
Every endpoint lives under /v3/company/{realmId} and authenticates with a bearer token.
| Entity | Operations | Notes |
|---|---|---|
account | Create, read, sparse update, list | CurrentBalance comes from the ledger |
customer | Create, read, update, list | DisplayName is unique per company |
item | Create, read, update, list | Service and non-inventory items |
invoice | Create, read, update, void | Posts A/R and income; balance tracks payments |
payment | Create, read, void | Applies to invoices; the rest is customer credit |
journalentry | Create, read, reverse | Immutable once posted |
reports/TrialBalance | Read | As of any end date |
Building something cheery?
Tell us about your integration and we will help you get connected.