Skip to main content

Versioning

The Quickbook API is versioned in the URL path. This documentation covers Quickbook API v3 (QB3), and the order endpoints are served under a /v1 resource prefix — for example, POST /v1/quote/price.

We add backward-compatible changes to the current version and reserve a new version number for breaking changes.

What counts as backward compatible​

We may make these changes without bumping the version:

  • Adding new endpoints or optional request parameters.
  • Adding new fields to existing responses.
  • Adding new enum values (including new booking status values in webhooks).

Write your integration to ignore unknown fields so these additions never break you.

Breaking changes​

Breaking changes ship under a new version. The previous version keeps working during the announced deprecation window so you can migrate on your own schedule.

In the API Reference​

The active base URL — including the version prefix — is shown in the servers block of the API Reference.