canonical: https://jentic.com/apis/threads.net/threads

# Threads API

Meta Threads API for publishing posts, managing replies, and retrieving insights on the Threads social platform. The API exposes 9 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically create a threads media container for text, image, video, or carousel posts, publish a threads media container. Covers 9 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Create a Threads media container for text, image, video, or carousel posts
- Publish a Threads media container
- Retrieve a specific media object
- Get insights metrics for a specific media post
- Hide or unhide a reply

## Use cases

### Analytics Operations

Use the Threads API to perform analytics operations programmatically. The API provides 9 endpoints covering core functionality including create a threads media container for text, image, video, or carousel posts, publish a threads media container, retrieve a specific media object.

Example prompt: Call POST /{threadsUserId}/threads to create a threads media container for text, image, video, or carousel posts

### Automated Posts Management

Automate posts operations by combining multiple Threads API endpoints. Agents can publish a threads media container and then retrieve a specific media object in a single workflow.

Example prompt: Call POST /{threadsUserId}/threads_publish to publish a threads media container, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Threads API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'create a threads media container for text, image, video, or carousel posts', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/{threadsUserId}/threads` | Create a Threads media container for text, image, video, or carousel posts |
| POST | `/{threadsUserId}/threads_publish` | Publish a Threads media container |
| GET | `/{threadsMediaId}` | Retrieve a specific media object |
| GET | `/{threadsMediaId}/insights` | Get insights metrics for a specific media post |
| GET | `/{threadsUserId}/threads_insights` | Get aggregated insights for a user's Threads profile |
| POST | `/{threadsReplyId}/manage_reply` | Hide or unhide a reply |
| GET | `/{mediaId}/pending_replies` | Get paginated pending replies awaiting approval |
| POST | `/{threadsReplyId}/manage_pending_reply` | Approve or ignore a pending reply |

## Key resources

- **Posts** — Create and manage Threads posts
- **Media** — Retrieve media objects
- **Insights** — Post and user insights/analytics
- **Replies** — Reply management and moderation
- **Profiles** — User profile information

## Why Jentic

- **Setup:** Wiring the Threads API by hand means completing its OAuth 2.0 authorization-code flow, tracking scopes like threads_content_publish and threads_manage_insights, refreshing the access token, and handling your own retries. Through Jentic you install once, import the Threads API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Threads API puts the user id in the URL path (/{threadsUserId}/threads), so a rule can pin your agent to one Threads user: it acts only for that user. You choose the operations it may call, so publishing actions like threads_publish are not included unless you add them.
- **Credential handling:** Your Threads token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a Threads post' or 'get post insights', and Jentic returns the matching Threads operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Threads API use?

The Threads API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a threads media container for text, image, video, or carousel posts with the Threads API?

Yes. Use the POST /{threadsUserId}/threads endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Threads API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a threads media container for text, image, video, or carousel posts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a threads media container for text, image, video, or carousel posts'. Jentic returns the matching Threads API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Threads API have?

The Threads API exposes 9 endpoints covering posts, media, insights operations.

### Can I limit what my agent is allowed to do with the Threads API?

Yes. Because you run Jentic One yourself, your own rules decide which Threads API operations and credentials the agent may use. Since the Threads user id sits in the URL path, such as /{threadsUserId}/threads, you can pin the agent to a single Threads user so it acts only for that account. You also choose the exact operations it may call, so publishing actions like POST /{threadsUserId}/threads_publish or reply moderation stay off unless you add them, letting you allow read-only insights calls on their own.