← All integrations

TwitterAPI.io

47 operations2 webhooks

Third-party X/Twitter data API for tweets, users, search, and social media analytics.

Supported operations

  • Webhooks.Add RuleWrite

    Create a new tweet filter rule for the webhook stream (inactive by default — call updateRule to activate)

  • Webhooks.Delete RuleDestructive

    Permanently delete a tweet filter rule

  • Webhooks.Get RulesRead-only

    List all existing tweet filter rules

  • Webhooks.Update RuleWrite

    Update a tweet filter rule, including activating or deactivating it

Supported triggers

  • Created

    A monitored user posted a new tweet

  • Filter Match

    A tweet matched a configured filter rule

FAQ

Install corsair and @corsair-dev/twitterapiio, add the TwitterAPI.io plugin, and connect with an API key. Then call methods like corsair.twitterapiio.api.api.webhooks.addRule() from your app. Corsair verifies webhooks, and syncs data per tenant.

Yes. TwitterAPI.io requires an API key from your TwitterAPI.io 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 TwitterAPI.io, GitHub, Notion, Stripe, and the rest. Trigger TwitterAPI.io from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for third-party x/twitter data api for tweets, users, search, and social media analytics. Common builds include sync jobs, admin tooling, and agents that call TwitterAPI.io APIs from your backend. Webhook handlers react to TwitterAPI.io events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced TwitterAPI.io 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 TwitterAPI.io 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/twitterapiio in the open repo. When TwitterAPI.io 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 TwitterAPI.io data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store TwitterAPI.io data on your behalf.