API Toolkit

API Tester

All tools

Fire a quick HTTP request and read the full response without installing a client.

How it works

Four simple steps

1

Choose method and URL

Select GET, POST, PUT, PATCH, DELETE or HEAD.

2

Add headers and body

One Key: Value header per line; JSON or text body.

3

Send it

The browser calls the endpoint directly.

4

Read the response

Status, timing, headers and body appear together.

API Tester

About API Tester

You are on a locked-down work laptop where installing Postman is not an option, and you need to confirm that a public endpoint returns what the docs promise. A request sent straight from a browser tab answers that in seconds.

Pick a method, enter the URL, add headers as Key: Value lines and, for POST, PUT or PATCH, a body. If you do not set them yourself, an Accept header asking for JSON or text is added, and Content-Type defaults to application/json whenever a body is present. Press Send and the response panel shows the status code and text, the time taken in milliseconds, the response headers and the raw body, which you can copy in one click.

The request goes directly from your browser to the API, so the browser's CORS rules apply. Many APIs do not send Access-Control-Allow-Origin for other sites, and the request then fails with a network error even though curl would succeed. Browsers also hide response headers the server has not listed in Access-Control-Expose-Headers, so the header list can be shorter than in a terminal. For those endpoints, run curl -I and paste the output into the HTTP headers parser, and look up unfamiliar codes in the status code reference. To tidy a JSON body before sending, use the JSON formatter.

Requests travel from your browser straight to the endpoint you enter; OneDevToolkit does not proxy or record them.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

The API does not allow cross-origin requests from this site, so the browser blocks the response. That is a CORS restriction rather than a problem with your request. Use curl or a desktop client for those endpoints.

No. A body is only attached for POST, PUT and PATCH. If your API expects a DELETE body, test it with curl instead.

Yes. Add a header written exactly as Content-Type: application/x-www-form-urlencoded and type the body as key=value pairs joined with &. Keep that capitalization, because a lowercase header name is not recognized and the JSON default gets added as well.

View more FAQs

Related tools

View all

Webhook HMAC Signer

Sign and verify GitHub, Stripe, and Slack webhook signatures locally.

Open

Webhook Replay Diff Lab

Compare webhook payload timelines, re-check HMAC digests, and spot idempotency gaps locally.

Open

JSONPath Playground

Query JSON with JSONPath and JMESPath-style paths side by side.

Open

GraphQL Studio

Format, validate, and cost-estimate GraphQL documents with cURL export.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools