Terms of Service

The rules and guidelines for using TwitterAPIs. Please read them before using our service.

1. Acceptance of Terms

By accessing or using TwitterAPIs (the "Service"), you agree to be bound by these Terms of Service. If you do not agree, do not use the Service. We may update these terms from time to time, continued use after changes constitutes acceptance.

2. Service Description

TwitterAPIs provides API access to publicly available Twitter/X data. The Service includes GET endpoints (search, user info, tweets, followers, etc.) and POST endpoints (DMs, tweets, likes, etc.) that require your own Twitter/X authentication tokens.

3. Account & API Keys

You must create an account to use the Service, except the free MCP endpoint described in section 3A. You are responsible for keeping your API keys confidential. Do not share your API keys with others. We reserve the right to revoke keys that are misused or compromised.

3A. Free MCP Endpoint (No Account)

We offer a limited, read-only MCP endpoint at https://api.twitterapis.com/mcp/free that needs no account or API key. Sending any request to it means you accept these Terms. Its first successful response each day (or, if that call is refused, the refusal) states the current terms version and gives an acceptance value; your client must send that value back (accept_terms) with each later call that day, and doing so confirms your acceptance. Calls are limited to 10 per caller per hour and 30 per caller per day, with further per-network and overall daily limits. We may change these limits, throttle the endpoint or withdraw it at any time without notice. It is provided as is, for evaluation. Section 4 (Acceptable Use) applies to it in full, trying to get around its limits is prohibited, and you remain solely responsible for complying with Twitter/X's rules when you use any data it returns. Our record of your acceptance holds a one-way hash of the calling address, the terms version and the time, not the address itself. Like every request to our API, calls to it also pass through our standard server logs.

4. Acceptable Use

You agree not to: (a) use the Service to spam, harass, or abuse others on Twitter/X; (b) scrape or collect data in violation of Twitter/X's terms; (c) resell API access to third parties without permission; (d) attempt to reverse-engineer, overload, or disrupt the Service; (e) use the Service for any unlawful purpose.

5. Credits & Payments

The Service operates on a pay-per-use credit system. Credits are non-refundable once purchased. Pricing is listed on our pricing page and may change with notice. Free credits provided at sign-up are for evaluation purposes and cannot be transferred.

6. Rate Limits & Fair Use

API usage is subject to rate limits. Excessive or abusive usage patterns may result in temporary throttling or account suspension. We aim to provide fair access to all users.

7. Data & Privacy

For your account we store only your email and name. For POST endpoints, your Twitter/X credentials passed per request are not stored; credentials you register against an API key are stored encrypted at rest until you replace them. For full details, see our Privacy & Data Handling page.

8. Availability & Uptime

We strive to maintain high availability but do not guarantee 100% uptime. The Service may be temporarily unavailable for maintenance or due to factors beyond our control. We are not liable for any losses caused by downtime.

9. Limitation of Liability

The Service is provided "as is" without warranties of any kind. TwitterAPIs is not liable for any indirect, incidental, or consequential damages arising from your use of the Service. Our total liability is limited to the amount you paid in the 30 days preceding the claim.

10. Termination

We may suspend or terminate your account at any time for violation of these terms or for any reason with reasonable notice. You may stop using the Service at any time. Upon termination, unused credits are forfeited.

11. Contact

For questions about these terms, email emma@twitterapis.com or visit our contact page.

Have questions about our terms?

Email us

Next read

Continue exploring related pages:

Twitter API security and key safety

How keys, write credentials, and data are secured: Bearer auth, TLS 1.2+, and credentials used per request or encrypted at rest.

TwitterAPIs pricing

Brand pricing page with endpoint-level costs and quick totals.

Twitter API use cases

14 use cases from sentiment analysis to lead generation.

How to get a Twitter (X) API key

Step-by-step walkthrough of the X developer console, plus a 30-second alternative with $0.50 in free credits.

Last updated: October 2026