A JSON REST API over QuickBooks Desktop. Sandbox keys hit a hosted simulated company; live keys reach real company files through Intuit’s QuickBooks Web Connector. Base URL: https://ledgerwire.vibiz.app/v1
Send Authorization: Bearer <key>. The key decides the mode: lw_test_ keys only ever touch your sandbox; lw_live_ keys queue requests for a production connection. With several connections, name one with the LedgerWire-Connection: conn_… header. Responses carry LedgerWire-Mode (sandbox or production) and LedgerWire-Request-Id.
JSON conventions
JSON keys are the camelCase form of qbXML element names, so everything you know from the SDK carries over: CompanyName → companyName, BillAddress/Addr1 → billAddress.addr1. Ids: ListID, TxnID and TxnLineID become id; TimeCreated/TimeModified become createdAt/updatedAt. Refs stay refs: customerRef: { id, fullName }; send either field. Amounts are numbers.
Lists return { object: "list", data, hasMore, nextCursor }. Pass cursor=nextCursor for the next page; results are ordered by updatedAt, which makes updatedAfter incremental syncs simple.
Updates use QuickBooks optimistic locking: POST /v1/{resource}/{id} with the current editSequence. Only fields you send change. For transactions, send the full lines array (existing lines with their id, new lines without).
CompanyQuery and HostQuery in one call: company name, address, fiscal year, QuickBooks product and supported qbXML versions.
Raw qbXML
POST /v1/qbxml takes a full qbXML document (Content-Type: application/xml) and answers in qbXML, or as { qbxml, responses } JSON when you send Accept: application/json. It is validated first: malformed XML fails fast with the line and column (0x80040400) instead of failing on your customer’s PC. In production the document is passed through unchanged. The sandbox simulates Query/Add/Mod for the core objects, iterators and onError, and answers statusCode="3250" for messages it does not simulate. See the qbXML message reference.
Errors
Every error says what failed, why, and how to fix it, and carries the QuickBooks status code when there is one:
HTTP 409
{
"error": {
"type": "invalid_request_error",
"code": "edit_sequence_out_of_date",
"message": "The provided edit sequence \"1731000000\" is out-of-date (current is \"1731000123\").",
"why": "The provided edit sequence is out-of-date.",
"fix": "Someone changed this invoice after you read it. GET /v1/invoices/1F4-1731000000 again, re-apply your change and send the new editSequence.",
"qbStatusCode": "3200",
"field": "editSequence",
"docs": "/errors/3200"
}
}
Dashboard → Connections → New connection. One connection per company file.
Send your customer the hosted setup page (/connect/…). It walks them through opening the Web Connector, adding the .qwc file, granting access and entering the password, and shows “Connected” live.
On the first sync LedgerWire records the company name, QuickBooks edition and version. You get a connection.synced webhook and an email.
The .qwc schedules a run every minute. Each run, the Web Connector calls authenticate, then sendRequestXML / receiveResponseXML until the queue is empty.
No check-in for 24 hours marks the connection stale, sends a connection.stale webhook and an email with the usual fixes.
Need a .qwc for your own SOAP server instead? Use the free .qwc generator.
Jobs and 202s
Production calls are queued as jobs. LedgerWire holds the HTTP request open for up to 25 seconds; if the Web Connector answers in time you get the normal response. Otherwise you get 202 with a job: poll GET /v1/jobs/{id} or wait for the job.completed / job.failed webhook. Jobs left in flight by a broken Web Connector session are re-queued automatically.
Register endpoints in Dashboard → Webhooks. Events: job.completed, job.failed, connection.synced, connection.stale. Each delivery is a JSON POST signed with LedgerWire-Signature: t=<unix>,v1=<hex>, an HMAC-SHA256 of t + "." + body with your endpoint secret. Answer any 2xx within 8 seconds.
API explorer
Runs real calls against the shared demo sandbox (simulated sample data). Log in to use your own sandbox and try creates and updates.
Using the shared demo key: read-only and rate-limited (30 calls a minute).