HTTP authoring guides

Preview a queued response and save its exact body

·

Use a delayed 202 response to review how an interface might display work that has been accepted and queued. The worked response includes a large numeric identifier so you can compare the body string in the fixture.

API Response Simulator

Preview the workshop response after 600 milliseconds

Load the example and inspect HTTP status 202 and Delay in milliseconds 600. Select Preview response. The waiting state appears before the response preview.

The response contains Retry-After 15 and X-Workshop-State queued, plus a Content-Type of application/json derived from Body media type. Retry-After describes a separate response header. The draft’s delay controls the local preview timer.

RFC 9110 — 202 AcceptedRFC 9110 — Retry-After

Compare the two views of the body

Check that the response preview shows jobId 9007199254740993. The simulator validates the JSON syntax and keeps the input body as written.

Select Download JSON. The envelope contains numeric status and delayMs fields, an ordered headers array, and the original body string with its newlines. Use that string when your test needs the exact representation.

Example body
{
  "jobId": 9007199254740993,
  "state": "queued"
}

Change the draft to 204 No Content

Change HTTP status to 204. Trying to preview with the JSON body selected reports that this status has no response body. Choose No body and preview again.

The new response has the configured headers and a null body in the JSON envelope. Change the delay to 0 to see the no-body preview immediately.

RFC 9110 — 204 No Content

Common questions

Does JSON body validation reformat my input?

The syntax check leaves the body string unchanged, including indentation and long integers.

Can I stop a delayed preview?

Select Cancel preview during the wait. Editing the draft also clears the pending result.

Sources

Put it into practice.

Related guides