Skip to main content
Send zeroDataRetention: true and Stophy keeps nothing from that call: no stored copy of the page is read or made, and nothing from the call is logged. You set it on each call. There is nothing to switch on in your account.

Make a request

This request reads example.com with zero data retention.

Read the response

This real response is cut to a few fields.
The answer is the same shape as any scrape. cacheState is miss because no stored copy was read. The call cost $0.003: $0.001 for the page and $0.002 for zero data retention. To check that nothing was kept, read the result again. A normal scrape can be read for 24 hours with GET /v1/scrape/{id}. A zero-data-retention scrape answers 404.
The call is still billed, so it still shows in GET /v1/logs, with its endpoint, status and cost. This entry is cut to the fields it holds.

Where to send it

Monitors do not take it. A monitor keeps a snapshot of each page to compare with the next one, and a monitor with zeroDataRetention is refused.

What changes

  • Stored copies. No stored copy of the page is read or made, so every read is live.
  • Results. A zero-data-retention scrape is not kept, so GET /v1/scrape/{id} answers 404 and the scrape cannot be interacted with. Start a session with POST /v1/browser and open the page there.
  • Jobs. A crawl, a batch or an extract with zero data retention keeps its results for 1 hour after it finishes instead of 24 hours. After that they are gone, and so are their pages. A webhook delivery for such a job is recorded without its payload.
  • Agent. The prompt, the steps and the result are held for one hour at most.
  • Logs. Nothing from the call is logged except the bill: the endpoint, the time and the cost.
  • Browser sessions. A session has no replay. It cannot be recorded, and it cannot use a profile, because a profile keeps cookies.
  • Interact. Send zeroDataRetention on the first call. If the scrape’s session is already open without it, stop that session with DELETE /v1/scrape/{id}/interact and start again.
Your own app stays responsible for what it stores and logs from the answers.

Limits and errors