Quick access

Saved in this browser. Sign in to keep it on all your devices.

API Response Time Tester

Test API endpoints and measure response times.

About API Response Time Testing

Measure your API's performance by testing response times. Supports all HTTP methods, custom headers, and JSON request bodies.

Version 1.1 Updated What's new

Release notes

  1. v1.1 Latest
    • Added an in-depth guide below the tool, written from what the tool actually does.
    • Redirects are now shown in the response instead of being followed.

About the API Response Time Tester

The API tester sends HTTP requests to an endpoint and measures how long it takes to answer, along with the status code and response body.

How to use it

  1. 1 Enter the endpoint URL and choose the method.
  2. 2 Add headers or a body if needed.
  3. 3 Send the request and review the timing and response.

Frequently asked questions

What is a good API response time?

Under 200 ms feels instant for most users. Over 1 second starts to feel slow.

Why are the first requests slower?

The first request has to set up DNS, TCP, and TLS connections, and the server may also be warming its caches.

Can I test private or localhost APIs?

No. Requests are made from our server, which cannot reach private networks or your localhost.

What the timing includes

The number shown is the total time from just before our server sends the request until it has the full response. That covers the DNS lookup, the TCP and TLS connection, the wait for your server to process the request, and the download of the body.

The measurement is taken from our server’s location, so it reflects the network path from there. A user on another continent will see different numbers. Send the same request several times and look at the typical value, because the first attempt often includes a cold cache or a sleeping serverless function.

Reading the status code

  • 2xx means the request succeeded. 201 usually means something was created, and 204 means success with no body.
  • 3xx is a redirect. This tester shows the redirect and does not follow it, so check the Location header in the response.
  • 4xx means the request was refused or invalid. 401 is missing or bad credentials, 403 is not permitted, 404 is not found and 429 is too many requests.
  • 5xx means the server failed. 502 and 504 usually point at a proxy that could not get an answer from the application behind it.

What it can reach

Requests come from our server, so this avoids the browser CORS restrictions that block many API calls made directly from a web page. For safety, only public addresses on the standard http and https ports are allowed. Private networks, localhost and cloud metadata addresses are refused, and that check is repeated against the address the host name resolves to.

Responses over 1 MB are stopped, requests time out after 20 seconds, and each visitor is limited to 20 requests a minute.

Be careful with real credentials

Anything you type into the headers or body passes through our server on the way to the API. It is not stored, but as a habit use test keys or short-lived tokens on any online tool, and keep production secrets on your own machine. For those requests, build the command with the cURL Generator and run it locally.

Remember that POST, PUT, PATCH and DELETE do what they say on a live system. Point them at a staging environment unless you intend the change.