Centra has a few different APIs used for different purposes. This documentation explains all the different APIs used to connect to Centra.
From one developer to another, we’re here to help you!
Building an experience on Centra’s APIs? Sign up to become a partner in order to enter the certification path, be invited to webinars and get direct Slack channel support with Centra after you are certified.
What are you waiting for? Get in touch to get going with Centra.
Each API has its own plugin. Some of the APIs need activation from Centra, such as the subscription API, but the other ones can be easily enabled by adding a new plugin to your store.
To enable a plugin in Centra, go to
SYSTEM, then select
STORES. Select what store you want your API to connect to and select the API in the list of plugins. You will need administration rights to have access to
Every API installed in Centra gets its own API-endpoint. This endpoint will then be the prefix of every API-call. In the documentation, this value is called
For authentication we use the API key, which is a shared secret generated in the Plugin settings of the API. You can use the
API-authorization: foo header with the token. The overview section of each API Reference might also define other rules of how to authenticate.
curl -H "API-Authorization foo" <base>/orders
Rate limiting is a mechanism which protects our APIs and underlaying servers from being overloaded. We try to detect both sudden bursts of requests, which can overflow our receive queues, as well as prolonged increased series of API requests, threatening to overload our internal server resources over longer period of time. Monitoring of those rate limits can also give Centra a good idea of how much resources your integration needs, and how scalable it will be in the future.
For now, rate limits are only introduced to our GraphQL API. In the future, we will introduce them in other APIs as well.
Types of rate limits introduced:
- Total number of requests - to avoid too many requests to the server, we limit their number
- Sum of query complexities of those requests - more complex query generally requires more time and resources to be processed
- Total number of mutations among those requests - another layer of complexity that can’t be calculated, so we limit their number
Each of those will be calculated within two timeframes:
- 10 seconds - ensures that there is no sudden short-term burst that can overwhelm the server
- 1 hour - ensures that there is no prolonged pressure on the server
You have 6 months to test the rate limits in QA. It will be enabled in all Production environments on 2023-09-04.