Skip to main content
Use Xquik as a Twitter API alternative for public reads and automated actions. Use it as an X API alternative across REST, SDKs, webhooks, and MCP. These Twitter API docs cover authentication, public reads, automated writes, and webhooks. Use this Twitter API documentation as a practical Twitter API for developers. It covers tweets, profiles, followers, replies, monitors, and media. Search tweets with the Twitter search API. Export user tweets, replies, followers, following, user profiles, timelines, communities, lists, and media. Post tweets and monitor accounts in real time. Deliver signed webhook events from the same API. Use the tweet scraping API to search recent and top tweets. Use the follower scraping API to export follower and following profiles. Use tweet reply scraping to retrieve conversations and authors. Use the Twitter webhook API to receive signed monitor events.
Public tweet, profile, follower, reply, timeline, community, and list reads need no connected X account. Every X write requires one. Private reads, including DMs and bookmarks, also require one. See Connect X account.

Choose a Twitter API Workflow

Start with the workflow that matches your search intent: Use the Twitter scraper API for tweet search and brand monitoring. Retrieve tweets, profiles, timelines, communities, lists, and media as structured JSON. The follower scraper exports follower and following profiles. The reply scraper returns replies and authors. Webhooks deliver new-tweet and profile-change events.

Monitors & Events

Create account and keyword monitors, retrieve events, manage webhooks

Draws & Extractions

Run tweet giveaway draws; extract tweets, replies, profiles, and followers

Tweets, Profiles & Followers

Search tweets, retrieve profiles, export followers, and download media

X Write Actions

Post tweets, like, retweet, follow, DM, profile updates

Account & Billing

Manage credits, API keys, drafts, styles, and subscriptions

Accountless Paid Reads

Stripe-funded guest keys for 33 eligible GET routes

Estimate Tweet Scraping Credits

Quote credits before scraping tweets, followers, replies, profiles, or timelines.

Review Twitter Scraping Jobs

List past tweet, follower, reply, profile, and timeline extraction jobs.

Check Account Monitor Status

Inspect one Twitter account monitor and its latest event activity.

Stop a Twitter Account Monitor

Delete an account monitor and stop its tweet and profile alerts.

Review Twitter Giveaway History

List past tweet giveaway draws, winners, eligibility rules, and rerolls.

Activate an Xquik Subscription

Create a hosted checkout for API access and recurring credits.

Twitter Community & Audience Scraping

Retrieve X Community Details

Read a community’s rules, member count, creator, moderators, and join policy.

Export X Community Members

Retrieve community member profiles, usernames, verification, and follower counts.

Export X Community Moderators

Retrieve moderator profiles, bios, verification, followers, and following.

Scrape X Community Tweets

Export recent community tweets, authors, replies, reposts, likes, and media.

Search Tweets in One Community

Filter one community’s tweets by keyword, recency, or top results.

Export a Twitter Account's Following

Retrieve profiles for every account one Twitter user follows.

Scrape Tweet Retweeters & Repost Users

Retrieve profiles for accounts that retweeted or reposted one tweet.

Base URL

All endpoints are served over HTTPS only. Always use the full HTTPS base URL.

OpenAPI spec

The full API specification is available as an OpenAPI 3.1 document:
YAML is also available at:
Use either format with OpenAPI tools or client generators. Xquik publishes the spec through RFC 9727 service discovery. API service discovery is published at:

Run in Postman

Fork the official Xquik collection into your Postman workspace. It includes safe starter requests for tweets, users, timelines, and trends. Run in Postman View the hosted collection documentation.

Authentication

Account API keys can use x-api-key:
Generate account keys from the API Keys dashboard. Xquik API keys also support Authorization: Bearer xq_your_api_key_here. OAuth 2.1 Bearer tokens keep their granted account scopes. Accountless guest keys use Authorization: Bearer. They have the fixed paid_reads scope. They work on the 33 eligible paid-read routes. A verified Stripe webhook activates each paid guest key. See Authentication for every method.

Machine Payments Protocol

Seven fixed-price GET operations accept anonymous MPP payments. The server returns 402 with a WWW-Authenticate: Payment challenge. The response can include a guest wallet action. Complete the MPP challenge or request explicit wallet confirmation. A failed request creates no checkout.

Accountless guest wallets

POST /api/v1/guest-wallets creates one Stripe-hosted Payment Link. It requires explicit user confirmation. The response returns a guest key and status URL. It requires no account, email, or dashboard. Verified payment activates paid reads for that key. Anonymous requests to 26 non-MPP paid reads return 401. They include WWW-Authenticate: Bearer and a guest wallet action. The 7 direct MPP reads return 402 with a Payment challenge. They include the same optional action. Neither response creates checkout. See Accountless guest wallets for creation, polling, top-ups, scope boundaries, and MCP behavior.

First request

Run this request to verify your API key:
Response:
Replace xq_your_api_key_here with your key. After 401, confirm the x-api-key header and xq_ prefix.

Production Integration

Use the X API integration checklist before launching a client, workflow, or agent. It covers authentication, pagination, billing, rate limits, and durable writes.

Rate limits

Read requests

The read bucket covers GET, HEAD, and OPTIONS. It allows 300 calls each second. Standard read throttles return Retry-After: 1.

Write requests

POST, PUT, and PATCH share a 120 per 60s user bucket. Throttled writes return Retry-After: 60.

Delete requests

DELETE requests use a separate 60 per 60s user bucket. Throttled deletes return Retry-After: 60.
Exceeding a bucket returns 429 rate_limit_exceeded with Retry-After and a JSON retryAfter field. See the Rate Limits guide for backoff implementations.

Response, Error & Event Contracts

Use these references while building production integrations:

Next steps

Error Handling

Handle errors gracefully with retries and fallbacks.

Rate Limits

Understand limits and implement backoff strategies.

Workflows

End-to-end examples: monitors, events, and webhooks.

Tweets, Profiles & Followers

User lookups, tweet search, trends, and media downloads.

X Write Actions

Create tweets, likes, retweets, follows, DMs, and profile updates.

Monitors

Check X accounts every second and receive signed webhook events.