For 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.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Threads API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Threads API API.
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
GET STARTED
Use for: I need to a threads media container for text, image, video, or carousel posts, I want to publish a threads media container, Search for a specific media object, Find all insights metrics for a specific media post
Not supported: Does not handle payments, communications, or crm — use for analytics only.
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.
Hide or unhide a reply
Patterns agents use Threads API API for, with concrete tasks.
★ 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.
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.
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.
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
9 endpoints — meta threads api for publishing posts, managing replies, and retrieving insights on the threads social platform.
METHOD
PATH
DESCRIPTION
/{threadsUserId}/threads
Create a Threads media container for text, image, video, or carousel posts
/{threadsUserId}/threads_publish
Publish a Threads media container
/{threadsMediaId}
Retrieve a specific media object
/{threadsMediaId}/insights
Get insights metrics for a specific media post
/{threadsUserId}/threads_insights
Get aggregated insights for a user's Threads profile
/{threadsReplyId}/manage_reply
Hide or unhide a reply
/{mediaId}/pending_replies
Get paginated pending replies awaiting approval
/{threadsReplyId}/manage_pending_reply
Approve or ignore a pending reply
/{threadsUserId}/threads
Create a Threads media container for text, image, video, or carousel posts
/{threadsUserId}/threads_publish
Publish a Threads media container
/{threadsMediaId}
Retrieve a specific media object
/{threadsMediaId}/insights
Get insights metrics for a specific media post
/{threadsUserId}/threads_insights
Get aggregated insights for a user's Threads profile
Three things that make agents converge on Jentic-routed access.
Credential isolation
Threads API oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create a threads media container for text, image, video, or carousel posts') and Jentic returns the matching Threads API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Threads API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Mixpanel
Alternative analytics API
Choose Mixpanel when you need a different approach to analytics operations
Amplitude
Alternative analytics API
Choose Amplitude when you need a different approach to analytics operations
Segment
Complementary analytics API
Choose Segment when you need a complementary approach to analytics operations
Pendo
Complementary analytics API
Choose Pendo when you need a complementary approach to analytics operations
Specific to using Threads API API through Jentic.
What authentication does the Threads API use?
The Threads API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
/{threadsReplyId}/manage_reply
Hide or unhide a reply
/{mediaId}/pending_replies
Get paginated pending replies awaiting approval
/{threadsReplyId}/manage_pending_reply
Approve or ignore a pending reply