Egytag Web API Client
A professional REST API client with params, headers, auth, body and timing metrics, plus safe local request templates and advanced response inspection.
Build a request, send it safely, and inspect the response alongside its settings.
Network options: timeout and redirects
Variables
Use {{baseUrl}} in URL, params, headers or body.
Params
Headers
Auth
Body
Local history
Response assertions
Set optional conditions and send the request; checks run locally and are not stored in history.
Enter a public API URL and press Send. HTTP status, response body and timings will appear here.
Response comparison
Capture the current response temporarily, then send another request to compare. Only changed paths are shown; responses are not saved to device storage.
Saved requests and environmentsLocal to this device — expand to manage
Safe templates store the method and URL without query values, plus parameter/header names only. Auth values and request bodies are never saved.
Safe collection runnerUp to 5 read-only requests, sequentially
Choose saved requests, then click Run. POST/PUT/PATCH/DELETE are skipped. Headers, auth, body and query values are never sent; the server validates each URL.
The request is sent by the Egytag server to avoid CORS. URL, headers, auth and body never enter analytics. History, environments and the request collection stay local. History never stores auth, headers, bodies or query values, and saved templates strip sensitive values automatically. Private/local targets are blocked to prevent SSRF.
Usage and result interpretation
- Set method and a public URL, then headers/body as needed.
- Inspect status, response and timings; avoid secrets in sharable examples.
This check uses Egytag servers. Do not enter unnecessary secrets.
How to use Egytag Web API Client
Build an HTTP request with its method, URL, params, headers, authentication and body. Inspect the response code, timing and payload; bounded file uploads are supported.
Understanding results and limitations
Avoid sharing real credentials in example requests. The request service blocks private and internal destinations for server-side safety.