Developer tools

Instant Snap API

One row per capture your code made through the Instant Snap API. It is where you go when an integration is not producing what you expected.

What is recorded here

This screen covers the Instant Snap API only — every capture of a URL posted to it, including those an AI assistant made through the MCP server. Nothing else appears in it.

Value	Meaning
`Instant Snap API captures`	Recorded here, one row each.
`Scheduled captures`	Not here. They belong to their Auto Schedule and appear on its capture view.
`Quick Capture from the app`	Not here. Also on the schedule.
`Auto Schedule API triggers`	Not here either — they use their own kind of key, and the result belongs to the schedule that was fired, labelled there as QUICK CAPTURE API.

Instant Snap API only

Only captures made with a wsw_api_ key are listed on this screen. Auto Schedule API triggers show up as captures of the schedule they fired.

The list

Value	Meaning
`URL`	The page that was captured.
`Status`	See below.
`Type`	Output as category and format — for example Image · PNG.
`Delivery`	How the API answered: File, JSON, or Cloud Storage. Cloud Storage rows also show the upload state — Not started, Uploading, Uploaded or Upload failed.
`HTTP`	The status the captured page itself returned, colour-coded. A 200 with a blank-looking image is a rendering problem; a 404 is not.
`Size`	The file produced.
`Duration`	How long the capture took.
`Created`	When the call was made.

Every column sorts, newest first by default, and there is a search box that matches the URL.

Capture status

Value	Meaning
`Pending`	The capture is still being taken.
`Succeeded`	The capture was taken and the file was stored.
`Delivered`	The file was returned in the API response and not stored — this is what a request for the raw file looks like afterwards.
`Failed`	The capture could not be taken.
`Timed out`	The page took too long to render.
`Expired`	The 24 hour media retention has passed and the file is gone.

Delivered is not a failure

If you asked for the file itself rather than a JSON envelope, there was never a stored copy to keep. The row records that the call succeeded and the bytes went back to you.

The detail view

View Capture opens the whole record. While the media is still available it shows the capture itself — the image, the video or the PDF — with Open and Download, and a link to the page source when one was saved. Those links are made for that page view and expire shortly; reload the page for fresh ones.

URL, status and — for a failure — the error code and message the service returned
Type and delivery mode, with the wire value in brackets
For cloud deliveries: the upload state, the bucket, the object key, and any upload error
Dimensions, the page’s HTTP status, when it was captured, and how long the media remains available
The API key that made the call, and the spec version

Error codes are passed through exactly as the API returned them, so they match the error reference.

Media lasts 24 hours

Media from the Instant Snap API lives for at most 24 hours

A capture’s file is short-lived. After it expires the row remains as a record of the call and reads Expired, while the file itself is gone.

So treat this as a log, not an archive. If you need the file kept, take it at the time — either from the API response, or by having the API deliver straight to your own bucket.

API Request Logs

API Request Logs, linked from the top of the Instant Snap API page, lists every call made to the Instant Snap API with one of your keys — including the ones that were refused and never became a capture. Filter by Outcome, or search by URL, error code or message.

Value	Meaning
`Accepted`	The capture was accepted; it appears on the Instant Snap API page.
`Invalid request`	The request body was rejected before anything was captured.
`Not in plan`	The plan does not include the Instant Snap API.
`No allowance`	The subscription does not allow captures right now.
`Quota exhausted`	The plan's capture allowance is used up.
`Rate limited`	Too many calls in a short time; the call was refused with a retry delay.
`Failed`	The call failed inside the service; nothing was captured.

Calls to the Auto Schedule API have a log of their own, under Auto Schedules › API Request Logs.

Did this page answer your question?

Tell us what is missing