X (Twitter)
X (formerly Twitter) is fully supported in Outstand through the Bring Your Own Key (BYOK) model. This allows you to use your own X API credentials, giving you complete control over the OAuth flow and ensuring your customers never see Outstand branding during account connection.
Prerequisites
Before you begin, ensure you have:
- An X (Twitter) developer account with approved API access
- Basic or Essential access tier (free tier recommended for most use cases)
- Understanding of OAuth 2.0 flows
Note: You do not need a paid subscription to use X with Outstand. The free tier includes OAuth 2.0 with PKCE support. See X's pricing and tiers for details.
Step 1: Create an X Developer Account
If you don't already have one:
- Go to developer.x.com
- Click Sign up and follow the authentication flow
- Accept the Developer Agreement
- Complete your developer profile
- Create a new project or join an existing one
Step 2: Create an App
- Navigate to your project dashboard at developer.x.com/portal
- Click Create App or select your existing app
- Fill in the required information:
- App name: Your application name (e.g., "My Company Social Media Manager")
- App environment: Production (or Development for testing)
- App permissions: Select the permissions you need:
tweet.read- Read user tweets and timelinetweet.write- Create and publish tweetsusers.read- Read user profile informationoffline.access- Keep users signed in (required for Outstand)
Step 3: Configure OAuth 2.0
-
In your app settings, navigate to User authentication settings
-
Enable OAuth 2.0 as the authentication method
-
Configure the following settings:
- App permissions: Select the appropriate scopes (see above)
- Type of App: Web App
- Callback URL / Redirect URL:
- For production: Your Outstand OAuth callback URL (contact support for the correct URL)
- Website URL: Your application's website
- Privacy Policy URL: Your privacy policy page
- Terms of Service URL: Your terms of service page
-
Click Save to save your OAuth 2.0 settings
Step 4: Obtain Your Credentials
-
Navigate to your app's Keys and tokens tab
-
You'll find two crucial values:
- API Key (Client ID): This is your OAuth 2.0 Client ID
- API Secret (Client Secret): This is your OAuth 2.0 Client Secret
-
Click Generate if your keys haven't been generated yet
Security Note: Your API Secret is only shown once when first generated. Save it immediately in a secure location. If you lose it, you'll need to regenerate new keys from the X Developer Portal.
Step 5: Add Credentials to Outstand
Once you have your Client ID and Client Secret, you can add them to Outstand using either method:
Method 1: Using the Dashboard
- Log in to Outstand Dashboard
- Navigate to Settings → Social Networks
- Select X (Twitter) from the dropdown
- Enter your Client ID in the "Client ID / API Key" field
- Enter your Client Secret in the "Client Secret / API Secret" field
- Click Add Social Network
Method 2: Using the API
curl -X POST https://api.outstand.so/v1/social-networks \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"network": "x",
"client_key": "YOUR_CLIENT_ID_HERE",
"client_secret": "YOUR_CLIENT_SECRET_HERE"
}'Step 6: Connect Your X Account
After adding your credentials:
- Navigate to Accounts in your Outstand dashboard
- Click Connect Account
- Select X (Twitter)
- Complete the X authorization flow
- Your X account will appear in your connected accounts list
Troubleshooting
"Invalid client credentials"
- Verify you copied the Client ID and Client Secret correctly (no extra spaces)
- Ensure you haven't regenerated the keys without updating Outstand
- Check that your app has OAuth 2.0 enabled in the developer portal
"Redirect URI mismatch"
- Verify the callback URL in your X app settings matches the Outstand callback URL
- Contact support if you're unsure of the correct callback URL
"Insufficient permissions"
- Ensure your app has the required permissions enabled (
tweet.write,users.read,offline.access) - You may need to request elevated access for certain operations
Important Notes
-
Rate Limits: X API has rate limits that vary by endpoint and access tier. Read tweets have higher limits (10,000 requests/month) than write operations. See X's rate limits for your tier.
-
Premium Access: For high-volume use cases, you may need to apply for premium access tiers or Twitter API Enterprise.
-
Credential Security: Never commit your Client ID or Client Secret to version control. Use environment variables or secure credential management tools.
Next Steps
Once your X credentials are configured and accounts connected, you can: