2024-01-01. To lock your instance to a specific version, specify the api_version in your convoy.json. You can also make per-request calls by specifying the header: X-Convoy-Version in the request header.
Backwards-compatible changes
Convoy considers the following changes to be backwards-compatible:- Adding new API resources.
- Adding new optional request parameters to existing API methods.
- Adding new properties to existing API responses.
- Changing the order of properties in existing API responses.
- Changing the length or format of opaque strings, such as object IDs, error messages, and other human-readable strings.
- This includes adding or removing fixed prefixes (such as
en_on endpoint IDs). - Make sure that your integration can handle Convoy-generated object IDs, which can contain up to 255 characters. For example, if you’re using MySQL, store the IDs in a
VARCHAR(255) COLLATE utf8_bincolumn (theCOLLATEconfiguration provides case-sensitivity during lookups).
- This includes adding or removing fixed prefixes (such as
- Adding new event types
- Make sure that your webhook listener gracefully handles unfamiliar event types.
Compatibility Matrix
The table below shows the Convoy version we introduced new API versions.| Convoy Version | API Version |
|---|---|
v24.4.1 | 2024-04-01 |
v24.1.1 | 2024-01-01 |
Breaking Changes
2024-04-01
- changed endpoint
titletoname - changes endpoint
target_urltourl
2024-01-01
- Changed
http_timeoutandrate_limit_durationin endpoints from duration string to int. - Changed the default signature format from
simpletoadvanced. - Stripped out unnecessary fields from dynamic api endpoint.