API upgrade guide
This API upgrade guide explains the different types of API changes, and how to upgrade to the latest API version.
For a list of detailed backward-incompatible changes, see API upgrades.
For detailed backward-compatible changes, see v1 API Changelog.
Types of API changes
The Zuora v1 API is version-controlled. Zuora uses an API minor version to manage backward-incompatible changes.
By specifying a zuora-version
header in a request, you can set version-controlled parameters and get corresponding responses, regardless of future changes to the API.
A change to the API can be a backward-compatible or backward-incompatible change.
The following changes are backward-incompatible:
- Changing the URL format in the HTTP definition
- Removing and renaming API resources, parameters, properties, methods, or enum values
- Replacing HTTP bindings to a resource
- Changing the types of parameters and properties
- Changing HTTP response status codes
- Changing parameter validations
- Adding new required request parameters
Typical backward-compatible changes include:
- Adding API resources
- Adding new supported operations to an API resource
- Adding an HTTP binding to a resource
- Adding optional request parameters to existing API methods
- Adding new fields to existing API responses
- Changing the format or length of strings, such as error messages and object identifiers
- Adding a new enum value for a parameter
How to upgrade to the latest version
If you are using an older version of the API, you can upgrade to the latest version to take advantage of the latest features and enhancements. It will override the older version.
A version is introduced when we make any backward-incompatible change. The version is in the format of YYYY-MM-DD
, for example, 2024-05-20
. The legacy versions are in the numbered format such as 196.0
, which are still supported for backward compatibility.
To upgrade your API minor version, take the following steps:
- Log into the UI of your Zuora sandbox environment as an administrator. Only users with the administrator role can access the setting used to manage API versions. If you have the Multi-entity feature enabled, API versions are set at the entity level.
-
In the Zuora UI, navigate to
Admin Settings
>
API versioning
to identify your current API version and the latest version on the API Version page.
Note: By default, your requests are on version
186.0
unless you have used thezuora-version
header to override. -
Check for the changes between the version you are running on and the latest version that are documented in the
API upgrades
. For example, if you are running on version
186.0
, and the latest version is2024-05-20
, check all the changes between186.0
and2024-05-20
. - In your testing environment, update your code to incorporate the changes for each version incrementally.
- Once all backward-incompatible changes have been incorporated into the code, validate that your code works for the new version.
- After you have validated your changes in the testing environments, click Upgrade on the API Version page. Then your testing environment is upgraded to the latest version.
- Repeat Step 1-6 for your Production environments.