For any question, we are one click away

Contact us

API Versions


API version defines the behavior of your API, including mandatory parameters in requests, the body of reponses, the objects returned by webhooks. The API constantly evolves by adding new functionality, improving responses, etc. We recommend you to upgrade your API version regularly to take advantage of those changes.

If a change in API breaks backward compatibility, the new API version is released (see the details here).

Each API version is named by the date when it was issued, e.g., "2023-10-31".

Below are the main rules of using and managing API versions.

API version in request and response

The API version is not specified in the URL of an API request. Instead, you can optionally pass the API version in the request header in the Version parameter. For example:

curl -X GET "" \
-H "Authorization: Bearer 6HUXQFbeomV1zf5i8cgm5W8KfncENVEa5uh8RngB" \
-H "X-Version: 2023-10-31" \

By default, the current version is used. To use another API version, specify it in API requests.

API response header always contains the version in X-Version parameter (format: 2023-11-15).

If the API version was not passed in the request, then the response contains the default API version.

API version compatibility

A new API version is released after adding changes that break backward compatibility. Such changes become available only in a new version.

Backward-compatible changes are available in every version and don’t require a version re-release. The examples of backward-compatible changes:

eCommerce API V2
Search results