TinyFish
28 operations3 webhooks
Web search, page fetch, cloud browser sessions, web automation agents, cited research, and reusable browser profiles behind one API key.
Supported operations
- Cancel RunWrite
Cancel a pending or running run
- Cancel RunsWrite
Cancel up to 100 runs in one request
- Get RunRead-only
Get one run with its steps, screenshots and HTML artifacts
- Get RunsRead-only
Get up to 100 runs by ID in one request
- Get Step HtmlRead-only
Get the full-page HTML snapshot captured at one step
- Get Step ScreenshotRead-only
Get the JPEG screenshot captured at one step of a run
- List RunsRead-only
List automation runs with status and date filters
- RunWrite
Automate a goal on a live website and wait for the result (billed per step)
- Run AsyncWrite
Queue a web automation run and return its run ID (billed per step)
- Run BatchWrite
Queue up to 100 automation runs in a single atomic request (billed per step)
Supported triggers
- Cancelled
A run reached CANCELLED
- Completed
A run reached COMPLETED with its results attached
- Failed
A run reached FAILED with its error attached
FAQ
Install corsair and @corsair-dev/tinyfish, add the TinyFish plugin, and connect with an API key. Then call methods like corsair.tinyfish.api.agent.cancelRun() from your app. Corsair verifies webhooks, and syncs data per tenant.
Yes. TinyFish requires an API key from your TinyFish account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit TinyFish, GitHub, Notion, Stripe, and the rest. Trigger TinyFish from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for web search, page fetch, cloud browser sessions, web automation agents, cited research, and reusable browser profiles behind one api key. Common builds include sync jobs, admin tooling, and agents that call TinyFish APIs from your backend. Webhook handlers react to TinyFish events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced TinyFish records without hitting the API on every read.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per TinyFish API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/tinyfish in the open repo. When TinyFish ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your TinyFish data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store TinyFish data on your behalf.