简体中文
EnglishWhat request options does REST test test support?
Updated
REST test test (resttesttest.com) is a browser-based HTTP client for poking around at an API. It supports six HTTP methods — GET, POST, OPTIONS, PUT, DELETE, and HEAD — plus optional authentication, custom headers, parameters, and file uploads. You configure everything on the page, then click Ajax Request to send it. The page requires a browser with HTML5 support.
Core request configuration
Two fields are mandatory before you can send anything: Method and Endpoint. The page states this directly — "Method and Endpoint are required."
| Option | What it does |
|---|---|
| Method | Selects the HTTP verb: GET, POST, OPTIONS, PUT, DELETE, or HEAD |
| Endpoint | The URL the request is sent to |
| Add parameter | Appends a name/value pair to the request |
| Add header | Adds a custom header via Header Name and Header Value |
| Add authentication | Supplies a Username and Password |
| Add file | Attaches a file to the request |
The page also notes you can "Click below to add additional parameters," so the parameter list is not fixed at one entry — you can stack as many name/value pairs as the request needs.
How the optional pieces work
Parameters
Each parameter is a name/value pair. Use Add parameter to create a new row, then fill in the Parameter Name and Parameter Value. Add as many rows as needed for the request.
Custom headers
Add header creates a Header Name / Header Value pair. This is the path for anything the method and endpoint fields don't cover — content types, API keys passed as headers, or other request metadata.
Authentication
Add authentication takes a Username and Password. This is the basic-auth style credential pair, entered as two separate fields rather than a pre-encoded header.
File uploads
Add file attaches a file to the request, which is what you'd reach for when testing an upload endpoint rather than a plain JSON or form POST.
What to check before you click Ajax Request
- Method and Endpoint are filled in. Missing either one blocks the request — the page flags them as required.
- Parameters, headers, auth, and files are only added if the endpoint needs them. They're all optional additions layered on top of the base method + endpoint pair.
- Your browser supports HTML5. The page calls this out explicitly, so an old or stripped-down browser may not run the request at all.
- You're pointed at an API you're allowed to poke at. The page frames itself as a way to "poke around at the API," so treat the endpoint as something you control or have permission to test.
The tool is deliberately minimal: one method selector, one endpoint field, and four optional add-ons. If your request needs something beyond those — OAuth flows, multipart boundaries you configure by hand, or response assertions — this page won't cover it, and you'd want a fuller client. For quick method/URL/parameter/header/auth/file checks against an API, it's enough.