REST API Client & Tester Pro
Browser-based API client with collections, environments, and authentication
Request Builder
Response Viewer
No response yet
Configure your request and click Send to see the response
How to test REST APIs online?
Send REST API requests right in your browser with collections, environments, authentication, and JSON response pretty-printing. Test endpoints, debug headers, and share collections as JSON.
Features
- All standard HTTP methods: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
- Authentication: Bearer token, Basic auth, API Key in custom header, OAuth 2.0 access-token paste
- Saved collections plus environments with variable substitution in URLs and headers
- JSON response pretty-printing with status, headers, size and response time
- Local request history (up to the last 100 requests)
- Export and import collections as JSON for easy sharing
How to use
- Enter your API endpoint URL and pick an HTTP method
- Add headers, query parameters, or a request body in the panels below
- Pick an authentication type and fill in the credentials, or leave it as None
- Click Send Request to fire the call and see the response
- View the response status, headers, size, timing, and pretty-printed body
- Click Save to add the request to a collection, then Export to share it as JSON
Tips & Best Practices
- Pick an active environment to make its variables expand into URLs and header values on Send.
- Browser CORS can't be bypassed client-side — production APIs may need a server-side client or a proxy.
- Auth tokens are kept in memory only; reloading the page clears them. Saved collections and environments persist in localStorage.
- Use Save and Collections to keep request templates around; export the collection JSON to share with teammates.
- Response status colour indicates 2xx (success) / 4xx (client error) / 5xx (server error); duration and size show next to it.
FAQ
What HTTP methods are supported?
All seven standard HTTP methods: GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS. The request-body editor is hidden for GET and HEAD where bodies are not used.
Can I save my API requests?
Yes. Click Save to add the current request to the Default collection. From the Collections tab you can Export each collection as JSON to back it up or share it.
How do environment variables work?
Create an environment, fill in variables like baseUrl or apiKey, and mark it active. Placeholders using the double-curly syntax in URLs and header values are substituted by the matching variable at send time.
What authentication methods are supported?
Bearer tokens, Basic auth (username + password, sent as base64), API keys in a custom header, and OAuth 2.0 in token-paste mode (paste an access token you obtained from your identity provider). Credentials are kept in memory only and are not persisted to localStorage.
Can I test APIs with CORS issues?
This client runs in your browser, so CORS rules apply. If a server doesn't send the right Access-Control-Allow-Origin header, the browser will block the response. For locked-down APIs you may need a proxy or a server-side client.
How do I organize my API requests?
Save requests into the Default collection. To group requests differently, click New Collection (each new collection gets its own card; the Save button currently writes to Default — pick the request from there and Export to share).
Can I test APIs with file uploads?
Not in this build. The Form Data body type accepts text key=value pairs (one per line) and sends them as multipart/form-data, but there is no file picker — file uploads would require a binary body editor.
Is my data secure?
All requests are sent directly from your browser to the target API; nothing is proxied through our servers. Saved collections, environments, and request history live in your browser's localStorage only. Authentication credentials are not persisted at all — they stay in memory for the active session and are cleared on reload.
Can I import Postman collections?
Not yet — the Import button accepts our own JSON format (the same format produced by Export). Postman's collection schema differs and is not converted.
How do I share API requests with my team?
Open the Collections tab, click Export on the collection you want to share, and send the downloaded JSON file. Recipients can drop it into the Import button on the same tab to load it.
What's the difference between environments and collections?
Environments hold variables (baseUrl, apiKey, version, etc.) that get substituted into requests at send time. Collections are groups of saved requests. You can swap environments without rewriting requests.
Can I test GraphQL APIs?
Yes. Use POST with Content-Type: application/json and a body like {"query":"…","variables":{…}}. The tool treats it as a regular JSON request.