API versioning allows Jobber to continuously evolve our platform and capabilities while offering third-party developers a predictable path for feature upgrades and deprecations.
To specify a version, you must use the X-JOBBER-GRAPHQL-VERSION
HTTP header
and set it to one of our
active versions. Specifying a version in
the header is required for all apps.
The response will include information about the API version your request is
making. Version information is found under the extensions
key.
If you are requesting a version that will become unsupported in the next 3
months, a warning
will be returned to indicate the expected unsupported date,
and a recommendation of the latest version to upgrade to.
"versioning": {
"version": "2022-04-29",
"warning": "Support for API version 2022-04-29 is scheduled to stop on May 13, 2023.
Upgrade to the latest version 2023-08-18 before that date.
For more information: https://developer.getjobber.com/docs/using_jobbers_api/api_versioning"
}
If you are requesting an unsupported version that hasn't been removed yet, a
warning
will be returned emphasizing that the version will be removed at any
time.
"versioning": {
"version": "2022-04-29",
"warning": "API Version 2022-04-29 is no longer supported, and will be removed at any time without warning.
Upgrade to the latest API version 2023-08-18 to ensure your app continues to function.
For more information: https://developer.getjobber.com/docs/using_jobbers_api/api_versioning"
}
If you are requesting a historic
version that has been removed, your request will be automatically upgraded to
the next supported version (oldest supported version). This version will be
returned under the version
key.
We recommend you use the most recent active API version to benefit from bug fixes and schema improvements.
To upgrade to a newer API version, consult the changelog to look for any breaking changes, which could impact your application. If you're using automatic code generation and type checking (such as with codegen), it could provide hints to what has broken.
In some cases, we will deprecate fields before they're removed and give alternate fields, which could satisfy your use case.
Once you've confirmed the new version works with your application (through
manual and automated testing), update the X-JOBBER-GRAPHQL-VERSION
header
value in your production environment.