🐦

X (Twitter) Public Data API

Read public X profiles, recent account posts, keyword matches and audience pages as JSON. Resolve a handle first, keep IDs as strings and use returned cursors to build coverage-labeled research datasets.

Open the standalone X data demo

Your first public profile lookup

Replace <API_KEY> with your authorized platform API key from the dashboard. The query URL contains your key; keep it out of shared links, screenshots and logs.

The example calls user-info with screenname=NASA, a public handle without the @ prefix. Inspect status and rest_id before requesting account content. Results can change: an active profile and a notfound lookup are different outcomes, and neither live data nor populated optional fields are guaranteed.

Base URL https://api.opendata-api.com

curl -X GET 'https://api.opendata-api.com/api/project/twitter/user-info?key=<API_KEY>&screenname=NASA'
Public X data request basics
  • This independent, read-only product is for available public X data, not official X account access. It does not publish posts, change follows or retrieve private messages. Use public data only for authorized, lawful purposes, respect privacy and retention requirements, and label exported datasets with collection time and coverage.
  • user-info demonstrated status=active for a resolved profile and status=notfound with null identity and counters for a nonexistent handle. Preserve null fields instead of converting them to zero. Verification labels are account metadata, not proof of a person's identity or account ownership.
  • Use screenname without @ where a handle is required. In user-info and user-timeline, optional rest_id takes precedence but screenname remains schema-required. Media and following ID selection need independent checks. Keep account, tweet, List and Community IDs as strings; a Space ID may be alphanumeric. Verify author.rest_id before assigning timeline posts to an account.
  • Omit cursor on the first request. For demonstrated paginated collections, pass next_cursor unchanged and keep account or search selection fixed. Stop on missing, empty or repeated cursors, deduplicate tweet_id for posts or user_id for follower/following records, and impose your own request budget. Page sizes and available history vary; no complete archive, full roster or streaming coverage is promised.
  • A keyword or hashtag search is not a single-account timeline. The demonstrated NASA query also matched unrelated authors using lowercase nasa in other languages. Review text and user_info.rest_id before classifying a mention or attributing it to the named account; keep the search query and capture time with the dataset.
  • Latest was demonstrated for search_type; do not assume other modes behave identically. community-posts documents separate Top and Latest ranking choices, while inspiration-posts documents its own country, period and type options. Send one option per selector, not a comma-separated choice list. Validate trends country values and all unverified selector behavior independently.
  • check-follow is best-effort for recent relationships and has limitations for large accounts or older follows. check-retweet may miss older reposts. Validate result schemas before use: negative checks are inconclusive, and absent records in collected follower or following pages do not establish a confirmed unfollow.
  • Observed photo references appear in media.photo as media_url_https and id; retain the source post and assess reuse rights separately. Media links do not grant access to private content or a complete media library. spaces-info describes basic metadata only, without a promise of audio streams, recordings, transcripts or listener identities; user-live is a status read, not video delivery.
  • Demonstrated reads cover user-info, user-timeline, search, tweet-info, followers, users-media and following. Other catalog operations need response validation before field-level parsers or examples are published. Timeline likes use favorites, while tweet-info uses likes; views may be a numeric string and author details can be null. Public counters are changing snapshots, not private impressions or built-in sentiment analysis.

Check request and account status separately

Check HTTP status separately from the gateway's code/message/data business status: code 200 indicates gateway business success, but HTTP 200 alone does not. Then inspect the endpoint payload inside data. The demonstrated profile uses status=active or status=notfound; timeline, search, media, follower and following reads use status=ok. A notfound profile has null identity and count fields, not a valid account with zero activity. Validate each endpoint's result shape before parsing it.

Choose an X data workflow
Resolve handles and enrich account records

user-info requires screenname and demonstrates active/notfound handling; optional rest_id overrides selection without removing the required handle. Batch profiles require comma-separated rest_ids, and account context requires screenname. Validate batch coverage and context fields separately before enrichment.

Collect account posts, media and authored replies

Timeline, media and account-reply reads require screenname. Start without cursor, then continue the same account using its validated response cursor. Timeline rest_id overrides the handle; media ID selection needs independent validation. Check author IDs, preserve repost context and do not confuse an account's authored replies with replies to one post.

Find brand mentions and hashtag discussions

search requires query; search_type=Latest was demonstrated. Continue with next_cursor while keeping query and mode unchanged. Matching words can come from unrelated authors or languages: check text and user_info.rest_id, and use user-timeline rather than keyword search for one account's activity.

Inspect a post and its available discussion

Use a public post's string id for tweet-info, latest-replies or tweet-thread. Post details demonstrate text, author, media references and public counters; reply and conversation response schemas still need validation. Discussion reads accept cursor, but available replies do not establish a complete conversation or an author's entire multi-post thread.

Explore public account connections and amplifiers

Followers, following and affiliates require screenname; reposters require post id. check-follow requires source user and target follows, while check-retweet requires tweet_id and screenname. Validate identifier formats and unverified result schemas; recent relationship checks have coverage limits, and missing rows or negative checks do not prove an unfollow or no historical repost.

Read curated List feeds and account rosters

Obtain a known public list_id for List posts, members or subscribers. Members are curated accounts; followers are subscribers to the List. All three accept optional cursor, but their response pagination and fields need validation before collection. A List feed is not a personalized home timeline.

Discover Communities and sample public discussions

Community discovery and latest/top post searches require query. Information, posts and members require a known community_id; validate IDs returned by discovery before reusing them. Community posts offer one ranking value, Top or Latest. Exact response fields and continuation behavior remain unverified, and collected discussions or members are not a complete archive or census.

Research observed topics and creative references

trends requires an endpoint-supported country value whose format needs validation. inspiration-posts requires country, period and type: select one documented country option, Daily/Weekly/Monthly and Likes/Replies. Do not transfer country formats between endpoints or assume verified ranking formulas, topic volumes or asset reuse rights.

Look up broadcast status and Spaces context

Resolve an account with user-info before passing its string rest_id to user-live. spaces-info requires the alphanumeric id from a known public Space link, not a tweet ID. Validate status and metadata fields before rendering; these reads do not promise video, audio, recordings, transcripts or push updates.

Discover public job listings by keyword

jobs-search requires query, with developer as the documented example. No location, salary, date or pagination inputs are declared. Validate listing fields and any returned stable IDs or source URLs before building a deduplicated digest; the read does not submit applications or cover every vacancy.

Profiles

GET /api/project/twitter/user-info

Get Public Profile by Username

Full docs β†’
Details

Resolve a public X (Twitter) handle with required screenname, without the @ prefix. Optional rest_id is the numeric account ID and takes precedence over screenname; screenname remains required by the request schema. An observed successful response has status=active, profile, rest_id, id, name, desc, website, avatar, header_image, location, created_at, protected, blue_verified and verification_type. Account counters include sub_count (followers), friends (following), statuses_count and media_count; affiliates and business_account may also be present. A nonexistent handle returned status=notfound with null identity and count fields, rather than a profile or numeric zero. Preserve IDs as strings, allow nullable fields and store the collection time with changing public counters. Verification labels are platform metadata, not proof of identity or ownership.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/user-info?key=<API_KEY>&screenname=NASA'
GET /api/project/twitter/profiles-by-rest-ids

Look Up Multiple Profiles by Account IDs

Full docs β†’
Details

Submit required rest_ids as a comma-separated string of numeric X account IDs. This read is described as returning an array of user profiles for the supplied IDs. Preserve each ID as a string and join records by returned identifiers rather than assuming response order, one result per input or a fixed batch limit. This endpoint has not been live-verified: exact profile fields, accepted batch sizes and unavailable-account behavior require validation before production parsing. Use user-info when a single handle lookup and its observed active/notfound contract are sufficient.

Test this X data endpoint 1 required Β· 0 optional
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/profiles-by-rest-ids?key=<API_KEY>&rest_ids=44196397%2C34743251'
GET /api/project/twitter/about-profile

Get Account Registration and Usage Context

Full docs β†’
Details

Pass required screenname to retrieve the available registration and usage information associated with a public X profile. This contextual read complements the ordinary user-info profile lookup; it must not be used as proof of a person's location, identity or account ownership. No response sample has been live-verified for this endpoint, so exact metadata keys, historical depth and missing-account behavior are not established. Preserve absent information instead of inventing account-history details.

Test this X data endpoint 1 required Β· 0 optional
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/about-profile?key=<API_KEY>&screenname=elonmusk'

Account Content

GET /api/project/twitter/user-timeline

Get Recent Posts from a Public Account

Full docs β†’
Details

Pass required screenname to read an account's recent timeline. Optional rest_id overrides the handle selection but does not remove the schema requirement for screenname. Leave cursor empty on the first request, then use the returned next_cursor unchanged for later pages. The observed response has status=ok, timeline, user, next_cursor and prev_cursor. Timeline entries include tweet_id, text, created_at, favorites, retweets, replies, quotes, bookmarks, views, entities, author and media. Reposts can include retweeted and retweeted_tweet; author fields can be null, and views may be a numeric string. Verify author.rest_id against the target, preserve IDs as strings and deduplicate tweet_id across pages. Stop on a missing, empty or repeated next_cursor. Returned page sizes and available history vary; this is not a complete historical archive or a streaming feed.

Test this X data endpoint 1 required Β· 2 optional
ParameterInValue
query
Optional selectors and cursor inputs (2)
ParameterInValue
query
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/user-timeline?key=<API_KEY>&screenname=NASA'
GET /api/project/twitter/users-media

Get Public Account Media Posts

Full docs β†’
Details

Supply required screenname for an account's media posts. Optional rest_id and cursor are available; the rest_id selection behavior has not been independently verified, so keep required screenname and validate any ID-based use. The observed response has status=ok, timeline, user and next_cursor. Entries include tweet_id, text, created_at, favorites, retweets, replies, quotes, bookmarks, views, author and nonempty media; observed photos expose media.photo items with media_url_https and id. Media and author details may vary by post. Follow returned cursors only for the same account, retain source post IDs and treat media links as available references rather than permission to republish. This is neither private-media access nor a guaranteed complete media library.

Test this X data endpoint 1 required Β· 2 optional
ParameterInValue
query
Optional selectors and cursor inputs (2)
ParameterInValue
query
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/users-media?key=<API_KEY>&screenname=NASA'
GET /api/project/twitter/user-replies

Get Replies Posted by an Account

Full docs β†’
Details

Pass required screenname to request the public replies authored by that account. Optional cursor continues the available account-reply collection; keep the handle unchanged between pages. This is different from latest-replies, which targets replies to one supplied post. Exact reply fields, continuation response keys and empty or unavailable-account shapes have not been live-verified. Treat returned replies as observed conversational activity, not a complete interaction history or private messages.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/user-replies?key=<API_KEY>&screenname=<screenname>'

Post Search

Post Details & Discussion

GET /api/project/twitter/tweet-info

Get a Post by Tweet ID

Full docs β†’
Details

Send required id as the string tweet ID from a public post or a previous collection result. The verified response has status=active, id, conversation_id, text, display_text, created_at, likes, retweets, replies, quotes, bookmarks, views, lang, sensitive, author, entities and media. Observed author fields include rest_id, screen_name, name, image, blue_verified, verification and sub_count; a photo post exposes media.photo items with media_url_https and id. Reply-context fields and conversation_control.policy may be null. Preserve large IDs as strings and handle views as a possible numeric string. Public counters can change between calls and are not private impressions or campaign analytics; unavailable-post behavior has not been verified.

Test this X data endpoint 1 required Β· 0 optional
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/tweet-info?key=<API_KEY>&id=<id>'
GET /api/project/twitter/latest-replies

Get Recent Replies to a Post

Full docs β†’
Details

Provide required id for the public post whose latest replies you want to inspect. Optional cursor requests another available reply page for that same post. This endpoint targets incoming replies to a particular post, not the replies authored by a selected username. No live sample established exact reply fields, response cursor keys, chronological ordering guarantees or unavailable-post behavior. Validate those shapes before strict parsing, and treat returned discussion as a bounded sample rather than every reply or a push stream.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/latest-replies?key=<API_KEY>&id=<id>'
GET /api/project/twitter/tweet-thread

Get Post Context and Available Replies

Full docs β†’
Details

Pass required id for a public tweet to request basic post information together with available replies. Optional cursor continues the returned discussion where supported. Keep the selected post's context separate from reply entries; this endpoint is not documented as an exhaustive author-written multi-post thread. Field names, pagination output and missing-post behavior have not been live-verified, so validate a successful sample before enforcing a conversation schema. Retain collection limits and omissions in any exported discussion.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/tweet-thread?key=<API_KEY>&id=<id>'

Audience & Relationships

GET /api/project/twitter/followers

Get Available Follower Profiles

Full docs β†’
Details

Supply required screenname for the account whose follower pages you want. Optional cursor continues the same account's collection; optional blue_verified has documented selector values 0 and 1, but its filtering behavior was not verified. The observed response has status=ok, followers_count, followers, next_cursor and more_users. Follower records include user_id, screen_name, name, profile_image, created_at, followers_count and verification fields. Optional description, website, statuses_count, friends_count, media_count, can_dm or business_account details can be null. The account's total followers_count is not the returned page length. Preserve IDs as strings, deduplicate user_id across available pages and keep collection timestamps. Latest-follower ordering and complete roster coverage were not independently established.

Test this X data endpoint 1 required Β· 2 optional
ParameterInValue
query
Optional selectors and cursor inputs (2)
ParameterInValue
query
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/followers?key=<API_KEY>&screenname=NASA'
GET /api/project/twitter/following

Get Accounts a Public User Follows

Full docs β†’
Details

Pass required screenname for the account whose following list you need. Optional rest_id and cursor are available; the rest_id precedence behavior was not independently tested, so retain required screenname and validate any ID-based selection. The observed response has status=ok, following, next_cursor and more_users. Returned profiles include user_id, screen_name, name, description, profile_image, website, created_at, statuses_count, followers_count, friends_count and media_count. Field availability can vary, and these counters describe each returned account, not the selected account's full relationship history. Deduplicate user_id across cursor pages, retain collection time and do not equate missing rows with confirmed unfollows.

Test this X data endpoint 1 required Β· 2 optional
ParameterInValue
query
Optional selectors and cursor inputs (2)
ParameterInValue
query
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/following?key=<API_KEY>&screenname=NASA'
GET /api/project/twitter/retweets

Get Accounts That Reposted a Tweet

Full docs β†’
Details

Provide required id as the public tweet ID to request available accounts that reposted it. Optional cursor takes the next_cursor value returned by a previous page for the same tweet; this continuation field is documented, but this endpoint's full response shape has not been live-verified. Validate account fields and unavailable-post behavior before joining to profile data. Returned reposters are a collected sample, not a guaranteed complete amplification graph or evidence about quote posts and likes.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/retweets?key=<API_KEY>&id=<id>'
GET /api/project/twitter/check-follow

Check a Recent Follow Relationship

Full docs β†’
Details

Supply required user for the source account and follows for the target account. The read offers a best-effort follow-relationship check and is explicitly limited for large accounts or older relationships. Accepted identifier formatting and exact result fields have not been live-verified; validate a public account pair before building a parser. Use a positive match as supporting evidence, but treat a negative result as inconclusive rather than definitive proof that the source does not follow the target. This endpoint checks a relationship and does not create or remove a follow.

Test this X data endpoint 2 required Β· 0 optional
ParameterInValue
query
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/check-follow?key=<API_KEY>&user=<user>&follows=<follows>'
GET /api/project/twitter/check-retweet

Check Whether an Account Recently Reposted a Tweet

Full docs β†’
Details

Send required tweet_id for the public post and screenname for the account to check. The described result concerns recent repost activity and may not cover older reposts. Exact status or boolean field names and missing-account or missing-post behavior have not been live-verified. Validate a known public case before depending on the result; a negative check cannot rule out an older repost or prove nonparticipation. This read does not publish a repost, modify the account or measure every form of engagement.

Test this X data endpoint 2 required Β· 0 optional
ParameterInValue
query
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/check-retweet?key=<API_KEY>&tweet_id=<tweet_id>&screenname=<screenname>'
GET /api/project/twitter/affiliates

Get Corporate Account Affiliates

Full docs β†’
Details

Pass required screenname for a corporate X account to request its available affiliated accounts. Optional cursor continues that account's affiliate collection. Affiliation represents a displayed platform association, not legal ownership, employment or a complete corporate structure. No live response sample established affiliate profile keys, continuation fields or empty-account behavior. Validate returned identifiers and coverage before enriching affiliates through profile or timeline lookups.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/affiliates?key=<API_KEY>&screenname=x'

Lists

GET /api/project/twitter/list-timeline

Get Posts from a Public List

Full docs β†’
Details

Supply required list_id as the string ID of a known public X List. Optional cursor continues available posts from that same List. A List timeline is a collection associated with curated member accounts, not a personalized home feed. Exact post fields, response pagination keys and private or unavailable-List behavior have not been live-verified. Retain the List ID and collection time, validate returned tweet identifiers before deduplication and do not assume complete membership activity or full historical coverage.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/list-timeline?key=<API_KEY>&list_id=<list_id>'
GET /api/project/twitter/list-members

Get Accounts Included in a List

Full docs β†’
Details

Pass required list_id for a known public X List to retrieve its available member accounts. Members are the accounts curated into the List, not the people who subscribe to it; use list-followers for subscribers. Optional cursor continues the member collection. Member profile fields, pagination output and unavailable-List behavior have not been live-verified, so validate returned identifiers before directory enrichment. Snapshot dates and collected coverage must accompany any membership-change claims.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/list-members?key=<API_KEY>&list_id=1177128103228989440'
GET /api/project/twitter/list-followers

Get Subscribers to a Public List

Full docs β†’
Details

Provide required list_id to request the available accounts that follow a public X List. These are List subscribers, not the curated member accounts returned by list-members. Optional cursor requests another subscriber page for the same List. Subscriber fields, continuation response keys and missing or private-List behavior have not been live-verified. Treat exported records as dated observed coverage rather than a complete subscriber census or proof of audience interests.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/list-followers?key=<API_KEY>&list_id=1177128103228989440'

Communities

GET /api/project/twitter/community-info

Get Community Information by ID

Full docs β†’
Details

Supply required community_id as the string identifier of a known public X Community. This read requests available descriptive information about that group; it does not return a guaranteed member census or every post. No live sample established exact metadata keys, field completeness or unavailable-Community status. Validate a returned record before building field-level examples, and separate unavailable groups from existing groups with missing descriptive attributes.

Test this X data endpoint 1 required Β· 0 optional
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/community-info?key=<API_KEY>&community_id=1493290339532222469'
GET /api/project/twitter/community-posts

Get Posts from a Known Community

Full docs β†’
Details

Provide required community_id for a public X Community. Optional ranking has documented values Top and Latest; choose one value rather than a comma-separated list. Optional cursor continues the same Community and ranking. This endpoint has not been live-verified, so exact post fields, ranking behavior, continuation keys and unavailable-group results must be validated. Treat collected posts as observed group discussion, not a complete Community archive or built-in topic analysis.

Test this X data endpoint 1 required Β· 2 optional
ParameterInValue
query
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/community-posts?key=<API_KEY>&community_id=1783990533192651232&ranking=Latest'
GET /api/project/twitter/community-members

Get Available Community Members

Full docs β†’
Details

Pass required community_id to request a public X Community's available member accounts. Optional cursor continues the member collection for that same group. Member identifiers, profile attributes, pagination fields and unavailable-group behavior have not been live-verified; validate returned records before profile enrichment or deduplication. Collected membership represents observed coverage, not a complete participant census, private-interest inference or demographic data.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/community-members?key=<API_KEY>&community_id=1506779564160258059'
GET /api/project/twitter/communities-posts-search-latest

Search Latest Community Posts

Full docs β†’
Details

Send required query for a keyword search of latest-ranked posts in X Communities. Optional cursor continues the same query through available results. This endpoint selects a latest-oriented search rather than returning all posts from one community_id. No live sample established exact post or Community-context fields, cursor output, no-match behavior or strict chronological coverage. Validate returned IDs and timestamps before deduplication or change tracking; scheduled polling is not streaming or exhaustive Community monitoring.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/communities-posts-search-latest?key=<API_KEY>&query=superman'
GET /api/project/twitter/communities-posts-search-top

Search Top-Ranked Community Posts

Full docs β†’
Details

Provide required query to request top-ranked matching posts in X Communities. Optional cursor continues available results for the same keyword. Top ranking is endpoint-specific and must not be interpreted as a platform-wide popularity measure or a known engagement formula. Exact post fields, Community context, continuation keys and no-match behavior have not been live-verified. Retain the query and capture time when comparing returned ranked samples.

Test this X data endpoint 1 required Β· 1 optional
ParameterInValue
query
Optional selectors and cursor inputs (1)
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/communities-posts-search-top?key=<API_KEY>&query=superman'
GET /api/project/twitter/inspiration-posts

Get Country and Period Inspiration Posts

Full docs β†’
Details

Choose required country, period and type to request a creator-inspiration post selection. Documented country options include ALL and listed three-letter codes; periods are Daily, Weekly and Monthly, and type values are Likes or Replies. Send one value per selector, never the catalog's comma-separated choice list. This endpoint has not been live-verified: accepted-selector behavior, returned post keys and ranking semantics require validation. Use results as source-linked creative research, not universal content-performance benchmarks or permission to reuse assets.

Test this X data endpoint 3 required Β· 0 optional
ParameterInValue
query
query
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/inspiration-posts?key=<API_KEY>&country=ALL&period=Daily&type=Likes'

Live & Spaces

GET /api/project/twitter/user-live

Check an Account's Broadcast Status

Full docs β†’
Details

Send required rest_id as the string numeric X account ID to check available current broadcast status. Resolve a handle to its account ID with user-info if needed; this endpoint does not accept screenname. No live sample established status keys, broadcast identifiers, no-broadcast behavior or update latency. Validate the result before displaying an indicator, debounce scheduled checks and treat observed status changes as polling evidence rather than push delivery. This read does not provide a video stream or start a broadcast.

Test this X data endpoint 1 required Β· 0 optional
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/user-live?key=<API_KEY>&rest_id=11348282'
GET /api/project/twitter/spaces-info

Get Available Spaces Information

Full docs β†’
Details

Pass required id as the X Space identifier from a known public Spaces link. Space IDs can be alphanumeric and are not numeric tweet or user IDs. This read is described as returning basic Spaces information; exact metadata fields, lifecycle states and unavailable-Space behavior have not been live-verified. Validate a sample before rendering session details. Do not promise audio streams, recordings, transcripts, listener identities or a complete attendance history.

Test this X data endpoint 1 required Β· 0 optional
ParameterInValue
query
curl -X GET 'https://api.opendata-api.com/api/project/twitter/spaces-info?key=<API_KEY>&id=1yoJMwpbmaXKQ'

Jobs

Public data capabilities and coverage

Read public X (Twitter) data as JSON for account research, social listening and repeatable collection pipelines. Start with a public handle, keyword or post ID and preserve the source identifiers and collection time.

  • Profiles: resolve usernames to account IDs, biographies, images, verification labels and public activity counts
  • Account content: retrieve recent timelines, public media posts and authored replies
  • Post search and details: collect keyword matches, post text, authors, timestamps, media references and public engagement counters
  • Audience data: explore available follower, following, reposter and affiliated-account records
  • Topic discovery: work with Lists, Communities, country trends and creator-inspiration selections
  • Event and job context: request broadcast status, basic Spaces information and keyword-based job listings
  • Pagination: continue supported collections with returned cursors, deduplicate string IDs and keep coverage notes

An independent, read-only data product, not an official X service. Profile, timeline, search, post-detail, follower, following and media reads have verified examples; other catalog capabilities require response validation before strict parsing. Available results are snapshots or samples, not guaranteed complete historical archives, private messages, publishing actions or audio downloads.

Guides