Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.alterauth.com/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Connect your users to Twitter (X) for reading tweets, posting content, managing follows, and accessing user data.
PropertyValue
Provider IDtwitter
CategorySocial
PKCERequired
Token refreshAutomatic
Redirect URIShown in Developer Portal

Step 1: Create a Twitter OAuth App

1

Go to the Twitter Developer Portal

Navigate to developer.x.com/en/portal/dashboard and sign in.
2

Create a new project and app

Click Add App (or create a new Project first), enter the app name, and select the use case.
3

Configure OAuth 2.0

In app settings, under User authentication settings, enable OAuth 2.0. Set the Type of App to Web App. Add the Alter callback URL from the Developer Portal to the Callback URI field.
4

Get your credentials

Copy the Client ID and Client Secret from the Keys and tokens tab.
Never share your Client Secret publicly. Store it securely and only enter it in the Alter Vault Developer Portal.

Step 2: Add to Alter Vault

1

Open the Developer Portal

Go to portal.alterauth.com and navigate to your app.
2

Add Twitter provider

Go to OAuth Providers > Add Provider > Twitter (X).
3

Enter credentials

  • Client ID: Paste your Twitter Client ID
  • Client Secret: Paste your Twitter Client Secret
4

Select scopes

Choose the scopes your app needs.
5

Save

Click Save. The provider is now active.

Available Scopes

ScopeDescription
tweet.readRead tweets and timelines
tweet.writeCreate and delete tweets
users.readRead user profile data
follows.readRead follows and followers
follows.writeFollow and unfollow accounts
like.readRead liked tweets
like.writeLike and unlike tweets
offline.accessObtain a refresh token for long-lived access
space.readRead Twitter Spaces
bookmark.readRead bookmarks
bookmark.writeAdd and remove bookmarks

Notes

  • Twitter OAuth 2.0 requires PKCE. Alter Vault handles this automatically.
  • Always include offline.access to receive a refresh token.
  • See the Twitter OAuth 2.0 documentation for more details.