What is it?
The API Request Tester sends a request to a web address (an API) and shows you the reply, with nothing to install. You choose the method (GET, POST, PUT, PATCH or DELETE), add headers and a body if needed, and see the status code, how long it took, and the reply neatly formatted.
Who is it for?
Developers testing their own APIs, students learning REST, testers checking endpoints, and no-code users trying webhook and API services.
How to use it
- Choose the method and type the address.
- Add headers like
Content-Type: application/jsonandAuthorization: Bearer …, and a JSON body if needed. - Tap Send. Try a sample shows a working example.
Safety
Requests go from your browser straight to the API you enter. Don’t paste live production keys on shared computers, and prefer test keys when trying things out.
Errors and how to fix them
- No answer: …: usually CORS: the API doesn’t allow browser requests from other sites. Test it with curl or Postman, or enable CORS on your API.
- Header line … not understood: write headers as
Name: value, one per line. - 401 / 403: missing or wrong API key or token.
- 415 or 400: wrong Content-Type or invalid JSON body; check it with the JSON Validator.
Questions people ask
- Are my requests saved? No, they’re sent from your browser and not stored.
Open the tool: API Request Tester
Still stuck?
Contact support. Tell us which tool or page you were using, what you tapped, what you saw, and your phone or computer and browser (for example: Android phone, Chrome). We reply by email.






























Questions, or an error not listed here?
Tell us in the comments: what you were doing, the exact message you saw, and your device and browser. We read every comment and add new fixes to this article.