API Tester

Test REST APIs with various HTTP methods. Add custom headers, request bodies, and view formatted responses.

Try:

HTTP Methods

GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS - choose the appropriate method for your request.

Custom Headers

Add authentication tokens, content type headers, and any custom headers needed.

CORS Notice

Some APIs may block browser requests due to CORS. Use a proxy for those cases.

About the REST API Tester

This REST API tester sends GET, POST, PUT, DELETE and PATCH requests with custom headers and a request body, then shows the status code, response headers and formatted body — no install and no account.

A REST API tester lets you talk to an endpoint directly, without writing client code first. That separation is the point: when a request fails you want to know whether the API is wrong or your code is, and a hand-made request answers that immediately.

Custom headers are what make it usable against real APIs. Authorization for a bearer token or API key, Content-Type to declare a JSON body, Accept to request a particular representation — most endpoints do nothing useful without them.

The response headers deserve as much attention as the body. Rate limit counters, cache directives, CORS headers and the exact content type all live there, and they explain a large share of "it works in curl but not in the browser" problems.

How to use the REST API Tester

  1. Enter the URL and method. Set the endpoint and choose GET, POST, PUT, DELETE or PATCH.
  2. Add your headers. Set Authorization, Content-Type and anything else the API needs.
  3. Add a request body. Provide the JSON payload for POST, PUT or PATCH.
  4. Send and inspect. Read the status code, response headers and formatted body.

REST API Tester features

  • GET, POST, PUT, DELETE and PATCH methods
  • Custom request headers
  • JSON request body with formatting
  • Status code and response header inspection
  • Formatted response body
  • No install or account needed

Frequently asked questions

Which HTTP methods are supported?

GET, POST, PUT, DELETE and PATCH, each with custom headers and a request body where applicable.

Can I send an Authorization header?

Yes. Bearer tokens and API keys can be set as custom headers, which most real endpoints require.

Why does a request work in curl but fail here?

Usually CORS. A browser enforces cross-origin rules that curl does not, and the response headers show whether the API allows it.

Can I see the response headers?

Yes. Status code and all response headers are shown alongside the formatted body.

Are my API keys stored?

No. Request details are used for the request and not persisted or logged.