X Public Data API
Collect public profiles, follower and following relationships, posts, replies, quotes, retweeters, search results, and current trends. Use consistent results for research and monitoring.
Available X APIs
Choose the API that matches your starting point: a username, post URL, account list, search query, or known numeric WOEID.

x/profiles
Profiles0.6 credits / result

x/followers-list
Profiles0.5 credits / result

x/posts
Posts0.5 credits / result

x/post-retweeters
Profiles0.5 credits / result

x/user-posts
Posts0.5 credits / result

x/search
Search0.7 credits / result

x/following-list
Profiles0.5 credits / result

x/post-quotes
Posts0.5 credits / result

x/post-replies
Comments0.5 credits / result

x/trends
Search0.5 credits / result
What X data can you retrieve?
Build a dataset around account identity, known content, recent publishing activity, post discovery, or current location-keyed topics.
Public account profiles
Turn usernames into profile identity, biography, visual assets, account status, audience metrics, follower lists, following lists, and collection time.
Known post details
Resolve public status URLs into post details, replies, quote posts, retweeter profiles, media, relationships, and visible engagement.
Recent posts by account
Collect recent public posts, with replies excluded, for selected usernames and compare activity across an account list.
Post search and discovery
Search public posts with one query, choose latest or top ordering, and keep the query connected to every match.
Current trends by WOEID
Collect a location-keyed snapshot of trend names, source ranks, queries, descriptions, and observation times.
SocQ vs X developer products
SocQ is built for consistent public-data research workflows. X developer products support X-managed integrations under their own products and authorization requirements.
| Workflow | SocQ X endpoints | X developer products |
|---|---|---|
| Best fit | Profile enrichment, post research, monitoring, and public-topic discovery | X-managed application and account integrations |
| Starting input | Usernames, status URLs, account lists, a search expression, or known WOEIDs | Product-specific requests and authorized account context |
| Authentication | SocQ API key | X developer credentials and applicable authorization |
| Data shape | Normalized profile, post, and trend records | Product-specific native X responses |
| Processing model | Asynchronous task followed by result pagination | Product-specific request and response lifecycle |
How the X API works
All ten X APIs use the same submit, track, and retrieve pattern.
1. Submit your input
Send usernames, status URLs, an account list, a search query, or numeric WOEIDs to the matching API.
2. Track the task
Use task_id with /v1/tasks/{task_id} until processing is complete.
3. Retrieve the results
Read data.results.items and use next_cursor while has_more is true.
Authenticate with your SocQ API key and submit one or more X usernames. Posts, user posts, search, and trends follow the same task flow.
curl -X POST "https://api.socq.ai/v1/x/profiles" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"usernames":["nasa","@OpenAI"]}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is trueCommon X API use cases
Creator and partner research
Enrich known usernames, compare public account signals, and build consistent creator profiles.
Brand and market monitoring
Follow selected accounts, repeat stable searches, or capture trends for known WOEIDs to build timestamped datasets around brands, competitors, and topics.
Campaign content reporting
Resolve campaign post URLs and organize content, authors, media, relationships, and collection-time engagement.
Research and data products
Use consistent profile and post records in warehouses, classifiers, search indexes, review tools, and dashboards.
Limits and public-data policy
SocQ returns publicly accessible X data as it appears when the task runs.
- Profile counters and post engagement are snapshots anchored to collected_at.
- Search results follow the selected latest or top ordering at collection time.
- Trend ranks and descriptions come from the source and represent the requested WOEID at collection time.
- results_limit sets a maximum, but the number returned depends on eligible public records available during the task.
- The APIs read public data only and do not publish posts or manage X accounts.
X API frequently asked questions
What can I collect with the X API?
You can retrieve public profiles, follower and following lists, known posts, recent posts, replies, quote posts, retweeter profiles, search results, and current trends for known numeric WOEIDs.
Which X API should I choose?
Use Profiles, Followers List, or Following List for accounts; Posts, Post Replies, Post Quotes, or Post Retweeters for status URLs; User Posts for recent account activity; Search for query-based discovery; and Trends for known numeric WOEIDs.
How does task processing work?
Submit a POST request, poll /v1/tasks/{task_id}, then read data.results.items and continue with next_cursor while has_more is true.
What does each result include?
Results include the fields available for that API, such as profile identity, post content and media, or trend name, source rank, WOEID, query, description, and collection time.
Are X metrics real time?
No. Account counters, post engagement, and trend ranks are snapshots. Use collected_at as the observation time when comparing results.
How is X data collection priced?
Profiles cost 0.6 credits per result, direct posts, user posts, and trends cost 0.5, and search results cost 0.7.
Combine data across platforms for more complete business insights
Bring public profiles, content, and engagement data from different platforms into one workflow to track brands, creators, and topics and run cross-platform monitoring and analysis more efficiently.
Facebook API
Collect public Facebook Page profiles, posts, group posts, comments, keyword-matched events, and available video transcripts with normalized identity, content, source, format, place, media, reaction, attendance, and engagement fields.
Google Ad Library API
Discover public advertisers, collect creatives for a company, or retrieve one known Transparency Center creative by URL for research and review.
Google Maps API
Discover public places, retrieve normalized details for known Maps URLs, and collect public reviews with source-linked place and author context.
Kwai API
Retrieve public Kwai profiles, one page of account posts, or one known post with normalized identity, content, media, timestamps, and visible engagement.
Truth Social API
Retrieve public account details, collect one source page of account posts, or resolve one known post URL into normalized records.
LinkedIn API
Retrieve public LinkedIn profile, company, post, and job data from known URLs, with normalized identity, career, company, content, engagement, and job fields.