Threads Scraper - Posts, Likes & Replies by Profile
Pricing
from $1.20 / 1,000 post scrapes
Scrape posts from any public Threads profile with exact like, reply, repost and quote counts, full text, media URLs and true UTC timestamps. Pages back through years of history. No login, no API key. Tells you which profiles Threads will not serve.
You can access the Threads Scraper - Posts, Likes & Replies by Profile programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in API & Integrations in Apify Console.
{ "openapi": "3.0.1", "info": { "version": "0.0", "x-build-id": "d9w7AlxD2fPAbrfkN" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/eiv~threads-profile-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-eiv-threads-profile-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/eiv~threads-profile-scraper/runs": { "post": { "operationId": "runs-sync-eiv-threads-profile-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/eiv~threads-profile-scraper/run-sync": { "post": { "operationId": "run-sync-eiv-threads-profile-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "profiles": { "title": "Threads profiles", "type": "array", "description": "Profiles to scrape, one per line. Accepts a handle (@zuck or just zuck) or a profile URL (https://www.threads.com/@zuck). A link to a single post is rejected rather than quietly turned into a whole-profile scrape. Leave empty to run a small demo on @zuck.", "items": { "type": "string" } }, "maxPostsPerProfile": { "title": "Max posts per profile", "minimum": 1, "maximum": 10000, "type": "integer", "description": "Stop after this many posts from each profile. The first page arrives with the profile itself; after that Threads returns about 10 posts per request, so 100 posts is roughly seven requests.", "default": 100 }, "maxTotalPosts": { "title": "Max posts in total", "minimum": 1, "maximum": 200000, "type": "integer", "description": "A ceiling across every profile in the run, so one prolific account cannot spend the whole budget. Counted on rows actually written, and a post that appears under two of your inputs is only counted, written and charged once.", "default": 1000 }, "maxPagesPerProfile": { "title": "Max pages per profile", "minimum": 1, "maximum": 200, "type": "integer", "description": "A work limit rather than an output limit: pages READ, not rows kept. It matters when a strict filter drops nearly everything, where without it a run could walk a whole profile to find ten rows. At about 10 posts a page the default reaches roughly 1,000 posts. If a profile stops on this limit the summary row says so, so it is never mistaken for the profile running out of posts.", "default": 100 }, "includeReplies": { "title": "Include replies", "type": "boolean", "description": "Off by default. A Threads profile feed mixes original posts with the author's replies to other people. Leaving this off keeps only original posts, which is what most analyses want; turning it on adds the replies, each marked isReply with the username it replied to. Filtered posts are never written and never charged.", "default": false }, "minLikes": { "title": "Minimum likes", "minimum": 0, "maximum": 100000000, "type": "integer", "description": "Skip posts below this like count. Compared against the exact number from the payload, not a rounded display figure.", "default": 0 }, "postedAfter": { "title": "Only posts after this date", "type": "string", "description": "Keep only posts published on or after this date. Posts are returned newest first, so this also gives the run a natural stopping point. Left empty, the run goes as deep as your other limits allow." }, "maxConcurrency": { "title": "Parallel workers", "minimum": 1, "maximum": 10, "type": "integer", "description": "How many profiles may be in flight at once. Raising this does not speed up a run on its own, because the delay below paces requests globally rather than per worker.", "default": 3 }, "requestDelayMs": { "title": "Delay between requests", "minimum": 0, "maximum": 60000, "type": "integer", "description": "Milliseconds between the START of one request and the next, counted across the whole run rather than per worker. Lowering it risks blocks that cost retries and return less data, not more.", "default": 1000 }, "proxyConfig": { "title": "Proxy", "type": "object", "description": "Leave this alone unless you have a reason not to. Threads serves a profile page to anyone, but it only serves the requests that page PAST the first few posts to European addresses - measured across seven locations, where US and Middle East egress returned the profile and then refused every continuation, and EU egress returned full history. So this Actor pins the proxy country to Germany by default. Changing it to a non-EU country will usually get you the first few posts of each profile and nothing more, and the run will say so.", "default": { "useApifyProxy": true } } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } }}OpenAPI is a standard for designing and describing RESTful APIs, allowing developers to define API structure, endpoints, and data formats in a machine-readable way. It simplifies API development, integration, and documentation.
OpenAPI is effective when used with AI agents and GPTs by standardizing how these systems interact with various APIs, for reliable integrations and efficient communication.
By defining machine-readable API specifications, OpenAPI allows AI models like GPTs to understand and use varied data sources, improving accuracy. This accelerates development, reduces errors, and provides context-aware responses, making OpenAPI a core component for AI applications.
You can download the OpenAPI definitions for Threads Scraper - Posts, Likes & Replies by Profile from the options below:
If you’d like to learn more about how OpenAPI powers GPTs, read our blog post.
You can also check out our other API clients: