CapturesResource gives you access to recordings, screenshots, and browser cookies produced during task executions. You can list captures for a specific run, delete individual files, inspect stored cookies, and bulk-clear screenshots or cookies when you need to reclaim space or reset state.
Methods
list
list
Returns all captures, including recordings and screenshots. Optionally filter by
runId.- HTTP endpoint:
GET /api/data/captures(withrunIdquery parameter when set) - Signature:
captures.list(input: { runId?: string } = {}, options?: RequestOptions) - Returns:
{ captures: Capture[] }
Capture has the following shape:list-captures.ts
screenshots
screenshots
Returns only screenshot captures, omitting recordings.
- HTTP endpoint:
GET /api/data/screenshots - Signature:
captures.screenshots(options?: RequestOptions) - Returns:
{ screenshots: Capture[] }
list-screenshots.ts
delete
delete
Delete a single capture by its name.
- HTTP endpoint:
DELETE /api/data/captures/:name - Signature:
captures.delete(name: string, options?: RequestOptions) - Returns:
{ success: boolean }
delete-capture.ts
clear
clear
Delete all screenshots at once.
- HTTP endpoint:
POST /api/data/clear-screenshots - Signature:
captures.clear(options?: RequestOptions) - Returns:
{ success: boolean }
clear-screenshots.ts
Working example: list captures for a run and delete cookies
This example combineslist and deleteCookie to clean up after a run: it lists captures for a specific run, then removes a session cookie for the target domain.
cleanup-after-run.ts
Related resources
Request options
Pass
signal, timeoutMs, and custom headers.Errors
Handle
FigraniumError responses.Executions
Start runs that produce captures.