Skip to main content

Transaction IDs

Every Quickbook API response — successful or failed — carries a unique Transaction ID. Quote it whenever you contact support: it lets us find the exact request in our logs.

Where to find it​

The Transaction ID is returned as the x-transaction-id response header, and is echoed as reference_id inside error bodies:

HTTP/1.1 200 OK
x-transaction-id: b2f1c0a4-8e2d-4a71-9e0b-2f6c1a5d8e90
{
  "status": "400",
  "code": "BAD_REQUEST",
  "type": "Validation Error",
  "message": "The request could not be processed.",
  "reference_id": "b2f1c0a4-8e2d-4a71-9e0b-2f6c1a5d8e90"
}

Using it​

  • Log it. Persist the x-transaction-id alongside your own logs so you can correlate issues later.
  • Share it. Include it in any support ticket — see Errors for the full error format.

Don't confuse the Transaction ID (per HTTP request) with the booking identifiers:

  • request_id / quote_id — returned by a quote, used to book against it.
  • job_uuid / job_number — identify a booking for detail, amend, and cancel calls, and appear in every status webhook.

In the API Reference​

A Transaction ID is returned by every operation. Send a request from any endpoint in the API Reference and inspect the response headers to see one.