Get X Posts by IDs · Twitter / X API
Batch-fetch up to 100 Posts in one call from a comma-separated list of numeric Post IDs, returning the same full object as the single-Post lookup. Useful for hydrating a set of Posts without one request each.
Using ChatGPT, Claude Code or another client? See the setup steps
curl https://api.unifapi.com/x/tweets?ids= \ -H "Authorization: Bearer $UNIFAPI_KEY"
Parameters
- expansionsquery
- tweet.fieldsquery
- user.fieldsquery
- media.fieldsquery
- place.fieldsquery
- poll.fieldsquery
- idsqueryrequired
- Comma-separated resource ids.
This operation is part of the Twitter / X API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs Twitter / X public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.
Common agent workflows
- Fetch canonical public Twitter / X content for summarization, ranking, monitoring, or enrichment.
- Attach engagement, author, media, and source metadata to an agent workflow.
- Give an AI agent a stable Twitter / X data source without building a per-platform integration.
- Normalize Twitter / X responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
- The `billing.records_charged` field reports the charged billable-record quantity for the successful response.
- A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.
Response status codes
Billing
This operation charges 1 credit per billable record, with a 1 credit ($0.001) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.
Errors and retries
Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
Fields on each record in data
A successful Get X Posts by IDs call returns data as an array; each record carries these fields.
- idstring
- textstring
- author_idstring
- created_atstring
- conversation_idstring
- langstring
- possibly_sensitiveboolean
- public_metricsobject
- attachmentsobject
- edit_history_tweet_idsstring[]
- authorobject
- mediaobject[]
Agents & Skills built on Twitter / X
You rarely call Get X Posts by IDs by hand. These prebuilt agents and skills already read Twitter / X data inside Claude or Codex — start from one of them, or call this endpoint yourself.
Try it free in the browser
Social media handle availability checker
Check a username across every social platform in one shot.
Twitter viewer — see any X profile, post or trend
Free X viewer: paste a handle, post link, hashtag or search. No account, no login to X.
Twitter profile viewer — view any X profile free
See any public X account without logging in: followers, bio, recent posts with views, and engagement rate.
Tweet viewer — view any Twitter / X post free
Paste a Twitter/X post link to read the tweet with its media, quoted post and engagement, no login.
Agents
More Twitter / X operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
Get X trends by WOEID
Return the current trending topics for a location identified by its WOEID (Yahoo "Where On Earth" ID), each with its name and, when available, associated Post volume. Useful for region-specific trend tracking and timing content to live conversations.
Get X Post by ID
Fetch a single X (Twitter) Post by its numeric ID — the classic get-tweet-by-ID lookup — returning text, author, timestamp, language, and public metrics (likes, reposts, replies, quotes, and views). Useful for hydrating a known Post or checking its current engagement.
Get the article-style payload for an X Post
Return the long-form X Article payload attached to a Post, including its full text body and authoring metadata. Useful for extracting complete article content from Posts that carry it, rather than only the short Post text.
Get users who liked an X Post
Return the accounts that liked a given X Post, as a cursor-paginated list of full profiles. Useful for analyzing who engaged with a Post and surfacing an interested audience.
Get quote Posts for an X Post
Return the quote Posts that reference a given X Post, as a cursor-paginated list with author and metrics for each quote. Useful for measuring how a Post is being amplified and what commentary it is attracting.
Get users who reposted an X Post
Return the accounts that reposted (retweeted) a given X Post, as a cursor-paginated list of full profiles. Useful for identifying who amplified a Post and mapping the audience that spread it.