Look Up a Threads Post by URL or Shortcode
View all Threads Public Data API endpoints →Retrieve one public Threads post by code or url. Supply at least one selector: code is the post shortcode, not its numeric ID; url must be an HTTPS Threads post URL on threads.com or threads.net. If both are supplied, url takes precedence. URL-encode a full URL when passing it as a query value. The response includes status, request_id and data.post with string id, code, username, text, taken_at as Unix seconds, url, like_count, reply_count, repost_count, quote_count and view_count. The observed shortcode lookup preserved the author, text and timestamp of the same post returned by the account-post collection. view_count was explicitly null: unavailable views must remain unknown, not be converted to zero. Engagement values are observations, not private analytics. Reply and quote counts do not include reply or quote records. Only public, available posts are in scope; invalid or unavailable inputs can fail.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/threads-scraper/get-post-details API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/threads-scraper/get-post-details?key=<API_KEY>&code=DeZtp-TkQHh'
Query Result
Use Cases
- Submitted-link source card: resolve a public post URL into its returned author, text, posting time and canonical link for an editorial review tool.
- Campaign interaction observations: store periodic likes, replies, reposts and quotes for selected posts and calculate changes between your own snapshots.
- Research citation verification: look up a discovered shortcode to cross-check post text and attribution before referencing it in a report.
- Metric-quality reporting: distinguish unavailable views from known interaction counts in a post-level dataset instead of filling missing values with zero.
Frequently asked questions
Do I need a post URL, a shortcode or a numeric post ID?
Provide either url or code. code accepts the shortcode from a public post URL, such as DeZtp-TkQHh, not the numeric-looking post ID. A shortcode can also come from code in account-post or keyword-search results.
What happens if I provide both url and code?
url takes precedence. Use one selector when possible to avoid looking up an unintended post. Accepted URLs are HTTPS public post URLs on threads.com or threads.net; URL-encode the full value in a query string.
Does a null view_count mean the post has no views?
No. It means a view count was not available. The observed successful lookup returned view_count:null alongside numeric interaction counts. Preserve that distinction rather than reporting zero views or calculating a view-based engagement rate.
Can I retrieve the actual replies or private post analytics here?
No. This operation returns the selected public post and available counters. reply_count is a count, not a list of replies, and the response does not provide private reach, audience demographics or account insights.