All the API access is over HTTPS. The response format for all requests is a JSON object. Whether a request succeeded is indicated by the HTTP status code. A 2xx status code indicates success, otherwise failure. When a request fails, the response body is still JSON.
Authentication is done via HTTP headers, more information in the Authorization section.
The calls in this gist all authenticate doing a call to getApiData(), which retrieves a token from
POST /auth, and the list of api endpoints from
The request parameters must be sent through the request body using a JSON string in POST methods or through query string in GET methods. Authentication is done via HTTP headers. The Authorization header authenticates the endpoint (using the format Bearer your_access_token).
Check inbenta errors documentation to know about the error codes and their format.
Global Rate Limits
Global rate limits are applied inclusive of all API calls made by an app over the 30-minutes sliding window, regardless of the particular endpoint. Rate limits also apply to invalid or malformed requests. We also applied a limit of requests per second that may change depending on the use.
Endpoint-Specific Rate Limits
Endpoints used to publish (
DELETE) have rate limits that are applied on an per-endpoint basis.
Rate Limit Response Codes
If your app exceeds any of these rate limits, you will receive a response with an HTTP response code of 429 (Too Many Requests).