# Threads API

Extract public Threads profiles, search results, timelines, posts, and replies.

- Platform ID: `threads`
- Capabilities: 8
- Execute endpoint: `POST https://data.upscrape.com/execute`
- OpenAPI: https://upscrape.com/scrapers/threads/openapi.json

## Capabilities

| Endpoint | Capability ID | Cost | Description |
| --- | --- | --- | --- |
| [Home feed](https://docs.upscrape.com/docs/platforms/threads/threads.home.feed) | `threads.home.feed` | 1 credit per request | Extract publicly visible home-feed post links with opaque pagination metadata. |
| [Post lookup](https://docs.upscrape.com/docs/platforms/threads/threads.post) | `threads.post` | 1 credit per request | Fetch public metadata and candidate links for a Threads post. |
| [Post replies](https://docs.upscrape.com/docs/platforms/threads/threads.post.replies) | `threads.post.replies` | 1 credit per request | Fetch public metadata and candidate reply links for a Threads post. |
| [Profile lookup](https://docs.upscrape.com/docs/platforms/threads/threads.profile) | `threads.profile` | 1 credit per request | Fetch public profile summary fields from a Threads handle page. |
| [Profile feed](https://docs.upscrape.com/docs/platforms/threads/threads.profile.feed) | `threads.profile.feed` | 1 credit per request | Extract publicly visible Threads, replies, media, or repost links for a profile. |
| [Search](https://docs.upscrape.com/docs/platforms/threads/threads.search) | `threads.search` | 1 credit per request | Fetch a public Threads search page and extract lightweight result metadata. |
| [User search](https://docs.upscrape.com/docs/platforms/threads/threads.search.users) | `threads.search.users` | 1 credit per request | Discover public Threads profile links from a search page. |
| [Profile posts](https://docs.upscrape.com/docs/platforms/threads/threads.user.threads) | `threads.user.threads` | 1 credit per request | Extract public post links from a Threads profile media page. |

## Common uses

- Profile enrichment and creator discovery
- Search, timeline, and post monitoring
- Reply-link collection for conversation analysis

## Integration contract

All capabilities use the shared `POST /execute` envelope. A `200` response completed inline; a `202` response must be polled through `GET /jobs/{id}`.

See [authentication](https://docs.upscrape.com/docs/api/authentication), [jobs and results](https://docs.upscrape.com/docs/api/jobs), and [errors and retries](https://docs.upscrape.com/docs/api/errors).