Online REST API Tester
Send GET, POST, PUT, PATCH, and DELETE requests from your browser and inspect the status, headers, body, and timing.
Requests go from your browser straight to the API you enter
Shortcuts
- Copy the output
- Alt + Shift + C
Your input is saved in this browser only. Reset clears it.
Request
Sample APIs
Response
Send a request to see the response
Try one of the sample APIs to get started
How to use the API Tester
-
Enter the endpoint URL and pick an HTTP method.
-
Add headers and a request body if the API needs them.
-
Send the request and inspect the response, or copy it as cURL or fetch() to run elsewhere.
Example: Creating a resource with a POST request
POST https://jsonplaceholder.typicode.com/posts
Content-Type: application/json
{
"title": "Hello",
"body": "From the API Tester",
"userId": 1
} 201 Created
{
"title": "Hello",
"body": "From the API Tester",
"userId": 1,
"id": 101
} 201 with the created resource is the usual answer to a successful POST. JSONPlaceholder is a fake API, so it always returns id 101 and stores nothing.
Frequently Asked Questions
Why does my request fail with "Failed to fetch"?
Almost always CORS: the API doesn't send an Access-Control-Allow-Origin header that permits requests from another website, so the browser blocks the response. The same request usually works from a terminal or your own backend. It can also mean the URL is wrong, the server is down, or an extension blocked the call.
Can I test APIs that need authentication?
Yes. Add an Authorization header (for example "Bearer <token>") or any API key header the service expects. Headers are kept in memory only: they're never saved to your browser's storage or added to shareable links, because they usually contain secrets.
Does my data pass through DevBottle's servers?
No. The request goes straight from your browser to the URL you enter, exactly like a request from your own frontend code. That's also why CORS rules apply.
How do I move a working request into my code?
Use Copy as cURL to run it in a terminal or share it with a colleague, or Copy as fetch() to get the JavaScript equivalent with the same method, headers, and body, ready to paste into your project.
About the API Tester
The API Tester is a powerful tool for testing, debugging, and exploring RESTful APIs directly in your browser. Whether you're developing your own API, integrating with third-party services, or just learning about APIs, this tool provides a simple yet powerful interface for making HTTP requests and analyzing responses.
How to Test a REST API Endpoint is a step-by-step routine covering headers, status codes, and CORS, and Postman Alternatives for Quick API Tests compares browser-based clients.
What is an API?
An API (Application Programming Interface) is a set of rules and protocols that allows different software applications to communicate with each other. RESTful APIs, which are the most common type on the web, use standard HTTP methods (GET, POST, PUT, DELETE, etc.) to perform operations on resources, typically returning data in JSON or XML format.
Features of Our API Tester
Multiple HTTP Methods
Support for all standard HTTP methods including GET, POST, PUT, PATCH, DELETE, and more. This allows you to test the full range of API endpoints and operations.
Request Headers
Add custom headers to your requests, such as authorization tokens, content types, or API keys. This is essential for working with secured APIs or specifying how your data should be processed.
Request Body Editor
A powerful editor for crafting request bodies in JSON, XML, or form data formats. Perfect for POST, PUT, and PATCH requests that need to send data to the server.
Response Formatting
Automatic formatting and syntax highlighting of JSON and XML responses, making it easy to read and understand the data returned by the API. The tool also displays response headers and status codes.
Request History
Save and reuse previous requests, making it easy to test the same endpoint multiple times or compare responses across different API calls.
Performance Metrics
View response times and other performance metrics to help identify potential bottlenecks or issues with API responsiveness.
Common API Testing Scenarios
- Authentication testing - Verify that your API correctly handles authentication tokens and permissions
- CRUD operations - Test Create, Read, Update, and Delete operations on your resources
- Error handling - Check how your API responds to invalid inputs or unauthorized requests
- Performance testing - Measure response times and identify potential bottlenecks
- Integration testing - Ensure that your application correctly interacts with third-party APIs
- Documentation verification - Confirm that an API behaves as described in its documentation
How to Use the API Tester
- Enter the URL of the API endpoint you want to test
- Select the appropriate HTTP method (GET, POST, PUT, DELETE, etc.)
- Add any required headers (e.g., Authorization, Content-Type)
- For POST, PUT, or PATCH requests, enter the request body in the editor
- Click "Send" to make the request
- View the formatted response, including status code, headers, and body
- Analyze the response to verify that the API is working as expected
Pro Tip
When testing APIs that require authentication, consider using environment variables or a secure storage mechanism for your API keys and tokens rather than hardcoding them in your requests. This helps prevent accidental exposure of sensitive credentials in your code or version control systems.