{jsonbody.com}

REST API Tester

Test REST APIs from your browser with GET, POST, PUT, PATCH and DELETE. Set headers and a JSON body, then inspect status, timing and the formatted response.

Send API requests from your browser

This REST client lets you try an endpoint without installing anything. Choose a method, enter a URL, add headers and a body, then press Send. You see the status code, response time, body size, the formatted response and the headers that the browser can read. It is useful for a quick check of a public API, a test of your own CORS setup, or a look at what an endpoint returns before you write code for it.

GET, POST, PUT, PATCH, DELETE, HEAD and OPTIONS are all supported. Once a request works, Copy as cURL gives you a command to share with a teammate or run on a server.

Example: create a record with POST

Press the POST JSON sample button to load a working request against a free public test API. It is the equivalent of this command:

The same request as a cURL command
curl -X POST 'https://jsonplaceholder.typicode.com/posts' \
  -H 'Content-Type: application/json' \
  -d '{ "title": "Hello", "userId": 1 }'

Why a request can fail here but work in Postman

Requests travel directly from your browser to the API and do not pass through jsonbody.com. That keeps your tokens private, but it also means browser security rules apply, which desktop clients do not have to follow.

  • CORS: the API must allow requests from other origins. If it does not, the browser hides the response even though the server received the request.
  • Mixed content: an https page cannot call a plain http URL, including many local servers.
  • Forbidden headers: browsers control Host, Cookie, Origin and a few others, so values you set for them are ignored or rejected.
  • Partial headers: only CORS-exposed response headers are visible, so the list can be shorter than what the server sent.

Method quick reference

  • GET reads data and has no body. HEAD does the same but returns only headers.
  • POST creates a resource or triggers an action.
  • PUT replaces a resource, and PATCH changes part of one.
  • DELETE removes a resource, and OPTIONS asks what is allowed.

Frequently Asked Questions

Is my API token sent to jsonbody.com?

No. The request goes straight from your browser to the URL you enter, and this site's cookies are not attached. Still, prefer test credentials over production ones in any web tool.

What does a CORS error mean?

The server did not send an Access-Control-Allow-Origin header that permits this page. Fix it on the server, or use the Copy as cURL button and run the request from a terminal, where CORS does not apply.

Can I test an API on localhost?

Only if your local server allows the origin and the browser permits the request. Many local servers run on plain http, which browsers may block from an https page.

Why are some response headers missing?

Browsers only reveal headers named in Access-Control-Expose-Headers, plus a small safe list. Use curl -i to see them all.