Skip to content

Core Features

Managing Endpoints

Rename an endpoint, extend an eligible address or delete captured requests. Understand owner access, confirmations and the difference between deletion and expiry.

On this page

Rename an endpoint

Open an endpoint you can manage. Choose Rename endpoint from its actions, enter a useful label such as “Synthetic orders”, then save. The receiving URL and captured data stay the same.

Extend an active endpoint

Sign in as the owning account and open Settings → Extend endpoint before expiration. Guest, disabled and expired endpoints are not eligible.

The new deadline is the later of the existing deadline and the operation time plus the current extension window. Extensions do not accumulate days, revive expired addresses or change the receiving URL. The original request retention period remains unchanged; signing in alone does not extend anything.

Delete one request

Select the captured request and use its Delete request action. Review and confirm the deletion in the dialog. The selected record is removed from the active database; the receiving address continues working.

Deletion cannot be undone through the workspace. Download a synthetic record first only if you need a local test artifact.

Delete captured requests

Open Endpoint actions → Delete captured requests. Review the confirmation: this removes all captured requests for the endpoint, including records hidden by filters. Confirm only when that is intended.

The active database history is cleared. The endpoint and its response configuration remain, so a later delivery can create a new capture.

Delete an endpoint

Open Endpoint actions → Delete endpoint and confirm. This stops the receiving address and removes its captured requests from the active database. Update or disable the sender to stop delivery to the old address.

Infrastructure backups are separate; see the Privacy Policy. Account deletion has different retention behavior and must not be treated as deleting every captured payload.