captures resource on the Figranium Swift SDK 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.
main.swift
Methods
list
list
Returns all captures, including recordings and screenshots. Optionally filter by Each capture entry contains
runID.- HTTP endpoint:
GET /api/data/captures(withrunIdquery parameter when set) - Signature:
captures.list(runID: String? = nil, options: RequestOptions = .init()) async throws -> [Capture]
list_captures.swift
name, url, size, modified, and type ("recording" or "screenshot").screenshots
screenshots
Returns only screenshot captures, omitting recordings.
- HTTP endpoint:
GET /api/data/screenshots - Signature:
captures.screenshots(options: RequestOptions = .init()) async throws -> [Capture]
list_screenshots.swift
delete
delete
Delete a single capture by its name.
- HTTP endpoint:
DELETE /api/data/captures/{name} - Signature:
captures.delete(_ name: String, options: RequestOptions = .init()) async throws -> JSONObject
delete_capture.swift
clear
clear
Delete all screenshots at once.
- HTTP endpoint:
POST /api/data/clear-screenshots - Signature:
captures.clear(options: RequestOptions = .init()) async throws -> JSONObject
clear_screenshots.swift
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.swift
Model
Capture
Related resources
Request options
Pass custom headers and per-request timeouts.
Errors
Handle FigraniumError responses.
Executions
Start runs that produce captures.
Captures and storage
Learn how Figranium stores recordings and screenshots.
Session state
Understand how cookies and session state work in Figranium.