Free browser-based tool
API Request Tester
Send HTTP requests (GET, POST, PUT, DELETE, PATCH) from the browser and inspect status codes, response headers, and body instantly.
HTTP Methods
Fetches a resource. No body. Should have no side effects. Response may be cached.
Creates a new resource or submits data. Requires a body. Not cacheable by default.
Replaces entire resource with the provided body. Omitted fields are deleted or reset.
Updates only specified fields. Other fields remain unchanged. More efficient than PUT.
Deletes the specified resource. Usually no body required.
Common HTTP Status Codes
| Code | Status | Meaning |
|---|---|---|
| 200 | OK | Request succeeded |
| 201 | Created | Resource successfully created |
| 400 | Bad Request | Invalid or malformed request |
| 401 | Unauthorized | Missing or invalid authentication |
| 403 | Forbidden | Authenticated but not authorized |
| 404 | Not Found | Resource does not exist |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Internal Server Error | Server-side failure |
Authentication Headers
Most APIs require authentication. Add headers using the header editor:
Bearer Token (most common)
Key: Authorization
Value: Bearer your-token-here
API Key
Key: X-API-Key
Value: your-api-key
Basic Auth
Key: Authorization
Value: Basic base64(username:password)
Understanding CORS Errors
CORS (Cross-Origin Resource Sharing) is a browser security policy that restricts web pages from making requests to a different domain. If you see a CORS error, the target API must include Access-Control-Allow-Origin in its response headers.
⚠️ CORS is a server policy, not a tool issue
The API server must explicitly allow cross-origin requests. To test CORS-restricted APIs, use curl or a local proxy.