SocialMati
SocialOAuth 2.0 with PKCE — Client ID + Client secret (+ app bearer token for listening)Pricing verified 2026-10-06

X (Twitter)

Publish posts with images, read replies and mentions, and monitor keywords for social listening.

AProvider definition

Provider
X (Twitter)
What it does
Publish posts with images, read replies/mentions, and monitor keywords (social listening).
Why we need it
Publish posts with images, read replies and mentions, and monitor keywords for social listening.
Used in
Social (publish, replies) · Social listening

BAccount requirements

Account type
X developer account with a Project and App
Prerequisites
  • X account
  • Payment method for pay-per-use API credits

CConnection method

Authentication
OAuth 2.0 with PKCE — Client ID + Client secret (+ app bearer token for listening)
Where to enter it
  • Your workspace: App → Integrations → Providers & API keysWorkspace owner or admin. Keys added here are used only by your workspace (AI keys here don't use plan credits).
  • Per brand: App → Integrations → Connected accountsAnyone who manages the brand. Each brand connects its own accounts.

Setup steps

  1. 1developer.x.com → create a Project and App.
  2. 2User authentication settings: OAuth 2.0, type “Web App”, permissions Read and write; add the Callback URI shown below and your website URL.
  3. 3Copy the OAuth 2.0 Client ID and Client secret (and the Bearer token for listening).
  4. 4Buy API credits in the developer console.
  5. 5Enter them in the application and connect your X account.

DPermissions & API scopes

Scope / permissionWhy it's neededRequested by
tweet.readRead your posts and replies.X connection
tweet.writePublish posts.X connection
users.readIdentify the connected account.X connection
offline.accessKeep the connection without signing in again (refresh token).X connection
media.writeUpload images attached to posts.X connection

This list is generated from the scopes the application's code requests.

EFree vs paid

Free account / free API access
No — the free tier was discontinued for new developers.
Card or billing account required?
Yes — pay-per-use credits.
Paid plan / costs
Pay-per-use per post created and per post read (roughly $0.015 per post created, more with links; $0.005 per post read), capped at a monthly read volume before Enterprise.
Quota and usage limits
Per-endpoint rate limits; monthly read cap on pay-per-use.
Production restrictions
Legacy Basic/Pro subscriptions were migrated to pay-per-use in 2026.
Checked against official/current sources on 2026-10-06. Provider pricing changes often — re-check before publishing.

FSetup screenshots

Capture each step with real values masked. Save images as public/docs/integrations/x/1.png … 10.png and they appear here automatically.

  1. Screenshot to add
    1. Account login / creation
    The provider's sign-in or sign-up page.
  2. Screenshot to add
    2. Developer console
    The developer console or dashboard home.
  3. Screenshot to add
    3. Project / app creation
    Creating the app or project used for this integration.
  4. Screenshot to add
    4. API enablement
    The API or product enabled for the project.
  5. Screenshot to add
    5. OAuth configuration
    Consent screen / OAuth settings with the redirect URIs.
  6. Screenshot to add
    6. API key / credentials creation
    Creating the key, secret or token (mask the value).
  7. Screenshot to add
    7. Permissions / scopes
    The scopes or permissions requested or approved.
  8. Screenshot to add
    8. Billing / quota settings
    Billing, credits or quota page.
  9. Screenshot to add
    9. Application connection
    The provider card in our application with fields filled (secrets masked).
  10. Screenshot to add
    10. Successful connection
    The green Test result or the connected account listed.

GApplication configuration

Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.

FieldRequiredExample / defaultNotes
OAuth 2.0 client IDYes—
OAuth 2.0 client secretYes••••••••Stored encrypted; shown masked after saving.
App bearer tokenOptional••••••••Used for social listening (recent search).

Paste these into the provider's console

Callback URI
https://api.socialmati.com/api/oauth/x/callback

HTesting

  1. 1Connect the account and publish a test post.
  2. 2Social → Listening: add a keyword and check results appear (needs the bearer token).

ITroubleshooting

ProblemWhat to do
402 / CreditsDepletedAdd API credits in the developer console.
Callback URL not approvedThe callback URI must match exactly in User authentication settings.
Invalid credentialsCheck the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure.
Missing permissionsReconnect and accept every permission on the consent screen. If a permission is missing from the list, add it to the app (and get it approved).
OAuth failureSign-in was cancelled, the app is in development/testing mode, or the user isn't allowed to use it yet. Add the user as a tester or publish the app.
Redirect URI mismatchCopy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings.
API not enabledEnable the API/product for the project or app in the provider console and wait a few minutes.
Quota exceededWait for the quota window to reset (see section E) or request a higher quota / add credits.
Account not eligibleCheck the account requirements in section B (e.g. business/professional account, verified property, registered organisation).
App review requiredPermissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions.
Billing requiredAdd a payment method or prepaid credits on the provider account (see section E).

JDisconnect & security

Revoke access at the provider
x.com → Settings → Security and account access → Apps and sessions → revoke. Regenerate the Client secret in the developer portal.
Disconnect in the application
App → Integrations → Providers & API keys or App → Integrations → Connected accounts → open the card → Remove / Disconnect. Connected accounts can be disconnected per brand.
Rotate credentials
Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
How credentials are stored
Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
What data the application can access
The connected account's posts, replies and mentions; public posts matching listening keywords.

Other Social providers

Start Free