X public data

X Public Data API

Collect public profiles and posts from usernames, status URLs, account lists, or a search query. Use consistent results for creator research, brand monitoring, and content analysis.

Available X APIs

Choose the API that matches your starting point: a username, a post URL, a list of accounts, or a search query.

x/profiles

Profiles0.6 credits / result

x/posts

Posts0.5 credits / result

x/user-posts

Posts0.5 credits / result

x/search

Search0.7 credits / result

What X data can you retrieve?

Build a dataset around account identity, known content, recent publishing activity, or topic discovery.

Public account profiles

Turn usernames into profile identity, biography, visual assets, account status, audience metrics, and collection time.

Known post details

Resolve public x.com or twitter.com status URLs into text, author, media, entities, relationships, and visible engagement.

Post search and discovery

Search public posts with one query, choose latest or top ordering, and keep the query connected to every match.

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 discovery	X-managed application and account integrations
Starting input	Usernames, status URLs, account lists, or one search expression	Product-specific requests and authorized account context
Authentication	SocQ API key	X developer credentials and applicable authorization
Data shape	Normalized profile and post 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 four X APIs use the same submit, track, and retrieve pattern.

1. Submit your input
Send usernames, status URLs, an account list, or one search query 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.

Start with one API request

Authenticate with your SocQ API key and submit one or more X usernames. Posts, user posts, and search 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 true

Common 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 or repeat stable searches 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.
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, resolve known posts, collect recent posts for selected accounts, and search public posts with one query.

Which X API should I choose?

Use Profiles for usernames, Posts for status URLs, User Posts for account lists, and Search for query-based discovery.

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 profile or post fields available for that API, such as identity, content, media, entities, relationships, visible metrics, and collection time.

Are X metrics real time?

No. Account counters and post engagement 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 and user posts cost 0.5, and search results cost 0.7.