QuantaAPIThe Test endpoint tab sends a real request to the mock route. It uses the collection key and the method from the endpoint configuration, so what you see here is what consumers get.
Send a request
- 01Fill in the bodyThe Body editor expects a JSON object. Leave it empty when the endpoint does not read a body.
- 02Add headersThe Header editor also expects a JSON object of header name to value pairs.
- 03Click Send RequestThe request is only sent when both editors contain valid JSON or are empty.
- 04Read the resultThe panel shows the status code, measured latency, response body, and any validation errors.
The method comes from ConfigurationThere is no method selector in the tester. Change the method on the Configuration tab and save it first.
What is sent
- URL
/endpoints/fetch+ endpoint path- Method
configuration.method- API key
x-collection-api-key— attached automatically- Body
- The parsed Body editor content
- Headers
- The parsed Header editor content
Reading the result
| OUTPUT | MEANING |
|---|---|
| Status | The real HTTP status returned by the mock route. |
| Latency | The configured delay, read from X-Response-Latency. |
| Body | The rendered response template, or the error response. |
| Validation errors | Parsed from X-Validation-Errors when the request is out of contract. |
Test requests are realThey are subject to latency and error simulation, and they are written to the request log exactly like external calls. A test with a 100% error ratio will fail too.
If Send Request stays disabled, the collection key could not be loaded or one of the editors contains invalid JSON. Both problems are reported above the editors.