Build a request, send it straight from your browser, and inspect the response. Export the same request as cURL or JavaScript fetch() for your code or docs.
curl -X GET 'https://jsonplaceholder.typicode.com/posts/1' \ -H 'Accept: application/json'
const res = await fetch("https://jsonplaceholder.typicode.com/posts/1", {
method: "GET",
headers: {
"Accept": "application/json"
},
});
const data = await res.json();Pyalm builds APIs and integrations — connecting ERPs, payment gateways, WhatsApp and e-invoicing platforms — for businesses in India and the UAE.
Try an endpoint from the docs, check a webhook URL responds, or confirm an API key works — then copy the working request as cURL for your terminal or fetch() for your front end.
Requests are sent by your browser, so the API must allow cross-origin requests (CORS). Public APIs designed for browsers work; many server-to-server APIs don't. If a request is blocked, use the 'Copy as cURL' button and run it from your terminal — that never touches CORS.
📖 Read the full guide: How to Test a REST API: Methods, Status Codes, Headers and CORS
Format, validate, minify and syntax-highlight JSON — with exact error line and column.
Decode a JSON Web Token's header and payload and read its claims and expiry.
Percent-encode or decode URLs and query strings, and break a URL into its parts.
No. Requests go directly from your browser to the API you enter. Pyalm never sees your URLs, headers, keys or responses.
The API didn't include Access-Control-Allow-Origin headers for browser requests. The request may well work from a server or terminal — copy it as cURL and try it there.
Yes, if your local server allows CORS from https://www.pyalm.com. Some browsers also block requests from HTTPS pages to plain-HTTP addresses.