Get Posts authored by an X user · Twitter / X API
Return a cursor-paginated timeline of Posts authored by an X user, newest first, optionally dropping replies via the `exclude` parameter. Each page carries a cursor for fetching older Posts — useful for profiling an account's content, monitoring an author, or archiving a feed.
Try it without an API key: Twitter profile viewer — view any X profile free, Twitter media viewer — X photos and videos, free.
Using ChatGPT, Claude Code or another client? See the setup steps
curl https://api.unifapi.com/x/users/{id}/tweets \
-H "Authorization: Bearer $UNIFAPI_KEY"Parameters
- idpathrequired
- X resource id.
- expansionsquery
- tweet.fieldsquery
- user.fieldsquery
- media.fieldsquery
- place.fieldsquery
- poll.fieldsquery
- pagination_tokenquery
- next_tokenquery
- max_resultsquery
- Integer from 1 to 100.
- excludequery
- Comma-separated X timeline exclusions, e.g. `replies`.
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 Posts authored by an X user 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 Posts authored by an X user 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
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.
Twitter media viewer — X photos and videos, free
See the photos and videos a public X account has posted, as a grid, without an account.
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.
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.
Translate an X user profile
Return a machine translation of an X user's profile text (such as the bio) into a target language code. Useful for understanding non-native-language profiles when analyzing international accounts.
Get verified followers for an X user
Return the subset of an X user's followers that carry a verified badge, as a cursor-paginated list of full profiles. Useful for gauging an account's reach among notable or paying accounts.
Get Posts liked by an X user
Return the Posts an X user has liked, as a cursor-paginated list. Useful for understanding an account's interests and engagement signals beyond the content it publishes itself.
Get X user by ID
Resolve a single X (Twitter) account by its numeric user ID and return the full public profile — handle, display name, bio, follower and following counts, verification status, and profile media. Useful when you already hold a stable user ID and need the current profile.
Get an X user's followers
Return a cursor-paginated followers list for a given X (Twitter) user — every account that follows them, with a full profile object per follower. Useful for audience analysis and mapping who follows a brand, creator, or competitor.
Get follower IDs for an X user
Return only the numeric user IDs of an X user's followers as a cursor-paginated list — a lighter, faster payload than full follower profiles. Useful for large-scale audience snapshots and set comparisons such as follower overlap between two accounts.