How to Use the OpenTweet REST API

The OpenTweet REST API gives developers programmatic access to all core OpenTweet features: creating tweets, scheduling, publishing, managing the evergreen queue, and viewing analytics — all without a Twitter Developer account.

What is the API base URL?

All V1 API requests go to https://opentweet.io/api/v1. The API uses standard REST conventions with JSON request and response bodies. All endpoints require HTTPS. The V1 API is stable and versioned — future breaking changes will be introduced under a new version prefix.

How do I authenticate?

Include your OpenTweet API key in every request using the Authorization header: Authorization: Bearer ot_your_api_key. API keys are created in Settings → API Keys and use the ot_ prefix. Treat them like passwords — use them only in server-side code and environment variables, never in client-side JavaScript or public repositories.

What are the key endpoints?

Core endpoints: POST /api/v1/posts (create tweet), GET /api/v1/posts (list tweets with filters), POST /api/v1/posts/batch-schedule (batch-schedule multiple drafts at once), GET /api/v1/accounts (list connected X accounts), and a full suite of evergreen queue endpoints at /api/v1/evergreen/*. Full documentation with request/response schemas is at opentweet.io/docs/api.

What are the API rate limits?

Rate limits by plan: Pro allows 60 requests/minute and 1,000/day. Advanced allows 300 requests/minute and 10,000/day. Agency allows 600 requests/minute and 30,000/day. Exceeding limits returns HTTP 429. The daily limit resets at midnight UTC. Response headers include rate limit status: X-RateLimit-Remaining and X-RateLimit-Reset.

Where is the full documentation?

Full API documentation with endpoint details, request/response schemas, authentication examples, and code samples in curl, JavaScript, and Python is available at opentweet.io/docs/api. The documentation covers all V1 endpoints including posts, batch scheduling, accounts, and evergreen queue management.