REST API Tester
Testing tool for REST API.
Request
Response
| Status | {{ status }} |
|---|---|
| Headers | {{ hkey }}: {{ hval }} |
* Cannot retrieve data unless the API add 'Access-Control-Allow-Origin' : * header. Please consider to use the below extension if you use Google Chrome.
https://chromewebstore.google.com/detail/cors-unblock/lfhmikememgdcahcdlaciloancbhjino
Tips
- Due to CORS restrictions, APIs without an
Access-Control-Allow-Originheader cannot be requested directly. Use public APIs or CORS-enabled APIs. - Set
Content-Type: application/jsonin the request headers to send a JSON body. - HTTP status codes at a glance: 2xx = success, 4xx = client error (401 = unauthorized, 404 = not found), 5xx = server error.
- For APIs requiring Bearer Token authentication, add
Authorization: Bearer {token}to the headers.
FAQ
Access-Control-Allow-Origin header, the browser will block it. Use a CORS-enabled or public API, or install a browser extension such as CORS Unblock.Content-Type: application/json to the request headers and enter a valid JSON string in the body field before submitting.Authorization: Bearer {your_token} to the request headers, replacing {your_token} with your actual token value.
Side Note — The Birth of REST: How Roy Fielding's Dissertation Changed Web Development
REST was proposed in 2000 by Roy Fielding in his doctoral dissertation "Architectural Styles and the Design of Network-based Software Architectures." Fielding was one of the principal co-authors of the HTTP/1.1 specification, and the REST concept emerged as he organized the design principles behind HTTP.
Twitter migrated from SOAP to REST API around 2010 and opened it to developers, triggering explosive adoption. Today, services like Stripe, GitHub, Slack, and OpenAI (ChatGPT) all offer REST APIs, forming what is often called the "API economy."
The original REST architecture includes a constraint called "Hypermedia as the Engine of Application State (HATEOAS)," yet very few real-world services implement it strictly. Debates about "what truly counts as REST" regularly heat up in web development communities, and the definition of "RESTful" remains contested.