TinyFish

Cancel a Browser Context Profile setup session and permanently discard its unsaved cookies and browser storage.

Idempotently cancel one or up to 100 asynchronous or SSE runs. Active cancellation is irreversible; synchronous runs cannot be cancelled, and already-terminal runs are returned with their actual status.

Create an isolated TinyFish remote browser session and return its CDP connection URL. This action starts billable browser infrastructure: TinyFish meters Browser usage until the session ends or becomes inactive. You must call Terminate Browser Session with the returned session_id immediately after browser work finishes, including after failures, to stop further usage charges. Creation can return before startup navigation completes.

Create a reusable Browser Context Profile for cookies and browser storage; this changes persistent account state.

Permanently delete a Browser Context Profile and all browser state saved in it. This action cannot be undone.

Permanently remove saved cookies and browser storage for one domain from a Browser Context Profile. This action cannot be undone.

Render and extract content from 1-10 URLs in one provider-native batch. Always inspect both results and errors because HTTP 200 can contain successful pages and per-URL failures together.

Get one Browser Context Profile and its saved-domain metadata.

Get summary records for 1-100 TinyFish automation run IDs in one request. The response separately reports IDs that were not found or are not owned.

Get the TinyFish wallet balance, auto-reload and pending-top-up state, and current Agent and Browser rates. Monetary values are returned as exact decimal strings. Legacy-credit accounts report FEATURE_NOT_AVAILABLE rather than an authentication failure.

List Browser Context Profiles available to the connected TinyFish account. Use the returned IDs when attaching or managing reusable browser state.

List saved TinyFish research runs with optional status, query, date, and sort filters, returning one cursor-controlled page.

List automation runs with optional status, goal, date, and sort filters, returning one cursor-controlled page.

List one page of Search, Fetch, or Browser usage history. Search and Fetch usage reads are free; Browser usage requires the paid Browser service.

List display-safe metadata for password-manager vaults connected to TinyFish. Credentials and secret values are excluded.

List display-safe metadata for items synchronized from password-manager vaults connected to TinyFish. Secret field values are never returned.

Persist cookies and browser storage from a completed setup session into a Browser Context Profile, then clean up the temporary session. Persisted state and successful session cleanup cannot be undone. The response retains domain-level skips and failures plus cleanup status so partial success remains visible.

Search live web pages, news, or research papers with domain and time filters, optionally fetching result pages inline, and return exactly one caller-selected zero-based result page.

Start a billable temporary remote browser session for establishing login state in a Browser Context Profile. The returned browser state is not saved automatically: after setup, always call Save Profile Setup Session to persist it or Cancel Profile Setup Session to discard it and tear down the session.

Refresh display-safe item metadata from all password-manager vaults already connected to TinyFish. Synchronization can add, update, or remove mirrored items. Returns synchronization counts and allowlisted item metadata without credential or secret values.

Idempotently terminate a remote TinyFish browser session to stop further browser usage charges. Already-ended sessions are also successful.

Rename a Browser Context Profile or change its default and proxy-country settings. Omitted fields remain unchanged.

Upload cookies and local or session storage directly into a Browser Context Profile. This changes persistent login state and may transmit authentication secrets; call it only with the credential owner's explicit authorization. TinyFish provides no rollback endpoint, so restoring prior state requires a caller-held copy or deleting the affected domains.