Frequently Asked Questions
Everything you need to know about XCROP API. Can't find the answer? Contact support or use the live chat.
Getting Started
XCROP is an X/Twitter Data Intelligence API Platform designed for real-time social data extraction and analysis, with a strong focus on crypto and DeFi communities. It provides 39 API endpoints covering user profiles, tweets, search, trending topics, and more.
Sign up for an account, grab your API key from the dashboard, and make your first request. The free Starter tier includes 5,000 credits per month with access to ALL endpoints (read, Write API, and Interaction Check) so you can test everything before subscribing. Paid plans just add more credits, higher rate limits, and cheaper per-credit pricing.
For API calls, use your API key as a Bearer token in the Authorization header. For the dashboard, sign in with a one-time email code, Google, or GitHub, no password needed. Two-factor authentication (2FA) is also supported.
Pricing & Credits
Each API call costs credits based on the data type. Tweet lookups cost 15 credits, profile lookups cost 18, follower listings cost just 1 per result, interaction checks cost 50, and write actions (tweet, like, follow, etc.) cost 100 credits each. Minimum charge is 10 credits per call. Credits reset at the start of each billing cycle.
We offer four options: Starter (free, 5,000 credits/month), Basic ($4.9/month, 700K credits), Pro ($9.9/month, 2M credits), and Pay as You Go (buy credit packs from $2.9, credits never expire). Higher tiers get increased rate limits and cheaper per-credit pricing.
You can upgrade your plan at any time from your dashboard. Upgrades take effect immediately with pro-rated billing. Downgrades take effect at the start of your next billing cycle; your current plan stays active until then.
We accept cryptocurrency: USDT (BEP-20), USDC (BEP-20), SOL (Solana), and POL (Polygon). Each crypto payment generates a unique wallet address with on-chain verification. Invoiced billing is available for business customers on request.
Rate Limits
Rate limits are per-minute and vary by plan. Higher tiers get more requests per minute. See the pricing page for the current limits of each plan, and the docs for rate limit response headers.
You receive a 429 Too Many Requests response. We recommend implementing exponential backoff in your client code. Our official SDKs handle this automatically with built-in retry logic.
Your dashboard shows real-time credit usage with daily and monthly breakdowns. You can also check usage programmatically via the dashboard API.
Data & Coverage
User profiles, tweets, followers/following, search (tweets and users), trending topics, Twitter lists, and interaction verification. The Write API also lets you create tweets, replies, likes, retweets, and manage follows.
Most endpoints return real-time data directly from X/Twitter. High-traffic endpoints like trending topics and popular profiles may be cached for 5-30 seconds for optimal performance.
The Write API lets you perform actions on X/Twitter: create tweets, post replies, quote tweets, like/unlike, retweet/unretweet, and follow/unfollow. Connect your X account first via the Account Connect endpoint, then use write endpoints with your API key.
Interaction Check endpoints verify whether a specific user has retweeted, replied to, or quoted a tweet. This is designed for airdrop and giveaway campaigns that require users to complete social actions before claiming rewards.
Security & Privacy
All credentials are encrypted using AES-256-GCM. Communication is HTTPS-only. We never store sensitive data in plaintext. Two-factor authentication and brute-force protection are available on all authentication endpoints.
When you connect your X account for the Write API, we only store encrypted session cookies and CSRF tokens, never your password. Credentials are encrypted with AES-256-GCM and can only be decrypted server-side.
Technical
Yes: official SDKs for JavaScript/TypeScript, Python, and Go. All include auto-pagination, retry on failure, and rate limit handling out of the box.
XCROP uses cursor-based pagination. Each paginated response includes a next_cursor field in the meta object. Pass this cursor as a query parameter in your next request. Continue until next_cursor is null.
CORS is restricted to xcrop.io by default. For your own applications, make API calls from your backend server and proxy the results to your frontend. Never expose your API key in client-side code.
Still have questions?
Guest