In case the API returns
JSON fields that are not mentioned in the documentation, API clients shouldn't rely on those fields when building their functionalities. Same rules apply to API endpoints or other features.
Undocumented features are not supported because one of the following reasons (list not exhaustive):
- Feature is being deprecated or will be removed soon
- We are adding new features that will be first tested internally before stabilizing and being announced
Please contact support in case of any questions about undocumented features.
We do our best to synchronize with API clients to help them to migrate from deprecated features to new functionality.
In most cases we will support old versions for reasonable time to guarantee API clients can migrate without any downtime.
The API is served over HTTPS protocol. Please see Swagger for specific endpoints and URLs.
To use the API it is first needed to create their API key - it can be done via merchant dashboard. Merchants can create multiple API keys
At the moment we don't do any rate-limiting of incoming API calls.
The API uses HTTP Basic Authentication mechanism over HTTPS protocol.
You should set the username as the name of the API key and password as API key password which was generated when the key was created.