X (Twitter)

Install corsair and @corsair-dev/twitter, add the X (Twitter) plugin, and connect with OAuth. Then call methods like corsair.twitter.api.tweets.create() from your app. Corsair stores tokens, and syncs data per tenant.

Yes. X (Twitter) needs an OAuth app with scopes that match what you automate. Register the app in X (Twitter), configure redirect URLs, then connect through Corsair or managed OAuth in Hub.

Yes. One Corsair client can hit X (Twitter), GitHub, Notion, Stripe, and the rest. Trigger X (Twitter) from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for social media platform for posts, timelines, users, and public conversation data via x api. Common builds include sync jobs, admin tooling, and agents that call X (Twitter) APIs from your backend. Local DB entities let you query synced X (Twitter) 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 X (Twitter) 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/twitter in the open repo. When X (Twitter) 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 X (Twitter) data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store X (Twitter) data on your behalf.