Admin Only - Reference guide for all configured secrets
Security Notice
Never commit secrets to version control. Rotate tokens regularly. Only share with authorized team members.
PURPOSE
Twitter OAuth 1.0a Consumer Key (API Key)
USAGE
Used for authenticating with Twitter API v1.1 endpoints
SOURCE
Twitter Developer Portal → App Keys and Tokens
PURPOSE
Twitter OAuth 1.0a Consumer Secret (API Secret)
USAGE
Used for signing OAuth 1.0a requests to Twitter API v1.1
SOURCE
Twitter Developer Portal → App Keys and Tokens (Keep secret!)
PURPOSE
Twitter OAuth 1.0a Access Token
USAGE
User authentication token for Twitter API v1.1 requests
SOURCE
Twitter Developer Portal → App Keys and Tokens (User context)
PURPOSE
Twitter OAuth 1.0a Access Token Secret
USAGE
User authentication secret for signing API v1.1 requests
SOURCE
Twitter Developer Portal → App Keys and Tokens (Keep secret!)
PURPOSE
Twitter OAuth 2.0 Client ID
USAGE
Used for initiating OAuth 2.0 authorization flow with Twitter API v2
SOURCE
Twitter Developer Portal → Authentication Tokens
PURPOSE
Twitter OAuth 2.0 Client Secret
USAGE
Used to exchange authorization code for access and refresh tokens
SOURCE
Twitter Developer Portal → Authentication Tokens (Keep secret!)
PURPOSE
Twitter OAuth 2.0 Refresh Token
USAGE
Used to obtain new access tokens when they expire
SOURCE
Obtained from Twitter OAuth 2.0 authorization flow
PURPOSE
Grok API Key for xAI
USAGE
Used in fetchBitcoinNews to fetch Bitcoin news from X with real-time search capabilities
SOURCE
https://console.x.ai/team/api-keys
OAuth 1.0a (4 secrets): Consumer Key & Secret + Access Token & Secret
Use for Twitter API v1.1 endpoints
OAuth 2.0 (3 secrets): Client ID & Secret + Refresh Token
Use for Twitter API v2 endpoints (recommended)
External APIs (1 secret): XAI_API_KEY for Grok
Used for real-time Bitcoin news fetching
Total: 8 active secrets configured