x-api

Topics in the source

• X API
• When to Activate
• Authentication
• OAuth 2.0 Bearer Token (App-Only)
• OAuth 1.0a (User Context)
• Core Operations
• Post a Tweet
• Post a Thread

Programmatic interaction with X (Twitter) for posting, reading, searching, and analytics. User wants to post tweets or threads programmatically Reading timeline, mentions, or user data from X Searching X for content, trends, or conversations Building X integrations or bots Analytics and engagement tracking User says "post to X", "tweet", "X API", or "Twitter API" Best for: read-heavy operations, search, public data. Required for: posting tweets, managing account, DMs, and any write flow. Legacy aliases such as XAPIKEY, XAPISECRET, and XACCESSSECRET may exist in older setups. Prefer the XCONSUMER and XACCESSTOKENSECRET names when documenting or wiring new flows. X API rate limits vary by endpoint, auth method, and account tier, and they change over time. Always: Check the current X developer docs before hardcoding assumptions Read x-rate-limit-remaining and x-rate-limit-reset headers at runtime Back off automatically instead of relying on static tables in code Never hardcode tokens. Use environment variables or .env files. Never commit .env files. Add to .gitignore. Rotate tokens if exposed. Regenerate at developer.x.com. Use read-only tokens when write access is not needed. Store O

This is an excerpt. Refer to the complete source and its current requirements.