Request History

DocStar doesn't keep a running log of every request you send. Instead, you keep the requests that matter as saved endpoints, example requests and sample responses, so they stay with your docs and your team can see them.

#

What DocStar keeps

What How to keep it Where to find it
The request itself Click Save or press Ctrl+S (Cmd+S on Mac) The endpoint in the collection sidebar
A variation of the request, such as another body or params After Send, click Save as Example Request Under the endpoint in the sidebar
A response you want to show readers After Send, click Add to Sample Response The Sample Response tab, and the published docs
The last response Nothing to do The Response tab, until you send the request again
Script output from the last run Nothing to do The Console and Test Results tabs
#

Save a request for later

  1. Build and send the request. See Send and Test Requests.
  2. Click Save. The button changes to Saved when there's nothing new to save.
  3. To keep a different version without changing the main endpoint, click Save as Example Request in the response panel.

Example requests appear under their endpoint in the sidebar. Open one to resend it or compare it with the main request.

#

Rerun a saved request

  1. Open the endpoint or example request from the sidebar.
  2. Pick the right environment from the Select environment dropdown.
  3. Click Send.

Because values like tokens and base URLs come from the environment, a saved request keeps working when those values change.

#

Find what changed

The endpoint header shows who last updated it. Edits to a published endpoint stay in draft until you publish them, so readers don't see half-finished changes. To track changes to an endpoint's documentation over time:

  • Open Logs (Activity Logs) in the collection sidebar to see recent edits.
  • Export the collection (Settings > Collection Actions > Export Collection) to keep a copy you can compare later.
#

Tips

  • Give example requests clear names, such as Create order (invalid card), so teammates know what each one tests.
  • Write tests in a Post-Script so you can rerun a saved request and see at once if the API still behaves the same. See Scripts.
Built with DocStar