Base URL
The Pingback API is built on REST principles. We enforce HTTPS in every request to improve data security, integrity, and privacy. The API does not support HTTP. All requests contain the following base URL:Authentication
The Pingback API uses API keys to authenticate requests. You can request and manage your API keys in API Key page. To authenticate you need to add an Authorization header with the contents of the header beingx-api-key: *** where *** is your API Key.
AES-256 encryption.
Response codes
Pingback uses standard HTTP codes to indicate the success or failure of your requests. In general,2xx HTTP codes correspond to success, 4xx codes are for user-related failures, and 5xx codes are for infrastructure issues.
| Status | Description |
|---|---|
| 200 | Successful request. |
| 201 | The resource was created. |
| 400 | Missing body data. |
| 403 | Forbidden. |
| 404 | Resource not found. |
| 409 | Conflict. |
| 422 | Invalid input. |
| 429 | Too many requests. |
| 500 | Indicates an error with Pingback servers. |
Rate limit
Pingback enforces rate limits to ensure fair usage of the API. If you exceed the rate limit, you will receive a429 status code.
The maximum number of requests that users can send is 5 requests per second.
The burst rate is 2 requests at a time.
To prevent this, we recommend reducing the rate at which you request the API. This can be done by introducing a queue mechanism or reducing the number of concurrent requests per second. If you have specific requirements, contact support team.