Saved Requests

You can keep Try-It requests for later, share them by link and save complete request/response interactions. This page covers all three.

Roles: Any signed-in user can save requests, share links and save interactions. They are private to the user who created them. These features are hidden without a session.

Saving a request#

The Save button next to Send stores the current form under a name. A saved request holds the Path, Query, timeouts, Body and the Headers table (as an ordered list, so duplicate names and row order survive). The selected environment is not saved, because it is its own remembered choice.

Saved requests appear in the Saved requests list in the same panel. The list is scoped to that exact endpoint (service, method and path). Selecting one replaces the form content instead of merging into it. The Manage saved requests button opens a dialog listing them with a delete button each and Delete all, both with confirmation.

Share opens the same dialog with a default name of Shared <date and time> and stores a standalone shared link that is not part of your saved list. The dialog shows a copyable link of the form <endpoint page>?tryit_shared=<id>.

  • One-time link is on by default. The link is deleted after it has been read successfully once, and a later visit gets 404. It is consumed only after the visitor's access to the service is confirmed, so an unauthorized visit cannot burn it.
  • With the toggle off, the link works any number of times.
  • Opening the link fills the Try-It form with the shared request. It never adds anything to the visitor's own saved list.
  • A visitor needs read access to the service. Without it the answer is an explicit 401 or 403.

Saved interactions#

After a request has run, successfully or not, the Response tab offers Save Interaction and Export Interaction. A saved interaction stores the request (parameters, headers, body, environment) and every response of a parallel run, with headers.

The dialog lets you choose whether the values of sensitive headers (Authorization, Cookie, Set-Cookie, API-key and token headers, in the request and the response) are replaced with ***. Masking happens on the server before anything is written. Bodies over 2 MB are cut and flagged as truncated.

Each interaction records a name, owner, endpoint, date, number of responses and an outcome: Success when every response is 2xx or 3xx, With Errors otherwise (network errors included).

The Interactions block below Try-It (collapsed by default) lists your interactions for the endpoint with copy-link, view, export to PDF and delete. A link of the form <endpoint page>?interaction=<id> works for any signed-in user who can read the service: it fills Try-It with the saved request and responses. The PDF contains the request, a ready curl command and all responses.

Next steps#

Screenshots

Last updated: