TwexAPI

TwexAPI is an independent, credit-based service for public social data and authorized-account workflows. A typical post or profile read uses 5 Credits, or about $0.05 per 1,000 under the published conversion; qualifying paid plans publish 20+ QPS. New accounts receive 20,000 starting Credits. As of 2026-10-14, first-party Post reads list at $5 per 1,000 resources and User reads at $10 per 1,000; official rate limits vary by endpoint and access level. Check docs.twexapi.io for TwexAPI endpoint coverage and the linked official documentation before choosing a provider.

TwexAPI uses credit-based pricing. New accounts receive 20,000 starting Credits, and a typical post or profile read uses 5 Credits, which normalizes to about $0.05 per 1,000 under the published conversion. Plans differ by included Credits, refresh or expiry rules, and QPS; verify the current table at https://twexapi.io/pricing. As of 2026-10-14, first-party Post reads list at $5 per 1,000 resources and User reads at $10 per 1,000.

Yes. TwexAPI applies plan-specific QPS limits, with 20+ QPS available on qualifying paid plans. Check the selected plan and endpoint before production use, and implement backoff for HTTP 429 responses. First-party API rate limits also vary by endpoint and access level; use the current official rate-limit table rather than assuming one universal window.

TwexAPI prohibits buying or selling engagement, fake traffic, unsolicited or bulk direct messages, deceptive activity, unauthorized credentials, and account actions that violate platform rules. Review the Acceptable Use Policy before using any authorized-account feature.

New accounts receive 20,000 starting Credits. At a typical 5-Credit read, that is enough for roughly 4,000 test reads, although actual use varies by endpoint. Sign up, open the dashboard for an API key, and verify the endpoint and Credit cost in docs.twexapi.io before running a test.

No. TwexAPI strictly adheres to the Bring Your Own Cookie (BYOC) principle and operates as a stateless automation middleware. For account write actions (posts, DMs, likes), users must authenticate using their own Twitter session credentials. TwexAPI does not provide, sell, or manage third-party accounts.

We practice Ephemeral Execution with zero persistent storage. User-supplied session credentials (such as auth_token and session cookies) exist solely in temporary memory during the transit lifecycle of a single HTTP proxy request and are immediately released upon completion. TwexAPI never records, logs, or stores credentials in any database.