Help
Support
Email us about bugs, wrong or missing documentation, endpoints you would like added, or anything else about the site.
Reporting a problem with the API
Include enough to repeat the request. A cURL command covers most of it.
- The method and full URL, including query parameters
- The request headers and body, with any real secrets removed
- The status code, headers and body you got back
- What you expected instead
- The time of the request, with your time zone
Common problems
6 answersMy data disappeared
Data is kept in memory and returns to the seed data when the server restarts. Create what you need at the start of each test run.
The first request is slow
If the server has been idle, the first response can take a few seconds. Later requests are fast. Check whether it is up with
GET https://api.testingapis.com/api/health.I get a 429 Too Many Requests
Only the Rate limit endpoints enforce a limit: 5 requests per 60 seconds per client. Wait for the number of seconds in
Retry-After, or send a new X-Client-Id header to start a fresh window.I get errors I didn't ask for
Check the URL for
?error= or ?delay=. Simulated errors carry the header X-Simulated: true. A response without it is a real error, and worth reporting.Authentication fails
The authentication endpoints accept only the fixed test credentials listed in the API reference. A 401 means the credentials are missing or wrong; a 403 means they are valid but not allowed on that endpoint.
I get 401 with sign_in_required or invalid_api_key
Endpoints outside the free tier (echo, HTTP methods, status codes, and the products, posts and todos resources are free) need a key from a free account. Create one on your API keys page and send it in the
X-TestingApis-Key header. sign_in_required means no key was sent; invalid_api_key means the key is wrong or was revoked. These errors carry the header X-TestingAPIs-Error, so you can tell them apart from the test credentials of the authentication endpoints, which an endpoint may also need.