Threads is Meta's text-based social app for sharing posts and joining public conversations. The Threads connector reads the connected account's profile, posts, replies, conversations, mentions, keyword search results, account and post insights, follower counts and demographics, and publishing limits. It can also hide or unhide replies and approve or ignore pending replies.
Power end-to-end data operations for your Threads API with Nexla. Our bi-directional Threads connector is purpose-built for Threads, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Threads or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Threads workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Nexla connects to the Threads API with a long-lived Threads user access token that you create with your own Meta app and paste into the credential. The token belongs to one Threads account, and every template reads or manages that account.
Sign in to Meta for Developers, and create an app with the Access the Threads API use case.
In the use case settings, add the permissions for the templates you plan to use:
Permission
Needed for
threads_basic
Every template, including Get My Profile, List My Threads (Posts), and Get Publishing Limit.
threads_read_replies
List My Replies, List Replies to a Thread, List Thread Conversation, and List Pending Replies.
threads_manage_replies
The Hide or Unhide Reply and Approve or Ignore Pending Reply destinations.
threads_manage_insights
Get Account Insights, Get Followers Count, Get Follower Demographics, and Get Thread (Post) Insights.
threads_manage_mentions
List Mentions.
threads_keyword_search
Search Threads by Keyword.
Under App roles, add the Threads account you want to connect as a Threads Tester, and accept the invitation in the Threads app. Until Meta approves your app in App Review, only accounts with a role on the app can authorize it, keyword search returns only that account's own posts, and mentions return only mentions by other testers.
Get a short-lived access token for the Threads account, either with the Threads authorization window of your app or with the Graph API Explorer. Short-lived tokens are valid for one hour.
Exchange it for a long-lived token, valid for 60 days, with this request, replacing the values in angle brackets:
GET https://graph.threads.net/access_token?grant_type=th_exchange_token&client_secret=<app secret>&access_token=<short-lived token>
Nexla does not refresh the token. A long-lived token expires 60 days after it was issued or last refreshed, and an expired token cannot be refreshed. Before it expires (and at least 24 hours after it was issued), refresh it with GET https://graph.threads.net/refresh_access_token?grant_type=th_refresh_token&access_token=<current token>, and paste the new token into the credential. If the token expires, create a new one as described above.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Paste the long-lived token into the Long-lived Access Token field. Nexla sends it as the access_token query parameter on every request.
The access token is sensitive and should be kept secure. If it is exposed, remove the app's access in Threads (or reset the app secret in your Meta app), create a new token, and update this credential.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Nexla tests the credential by reading the ID and username of the Threads account the token belongs to. To replace an expiring token, edit the credential and paste the refreshed token into Long-lived Access Token.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Threads connector tile, then select the credential that will be used to connect to your Threads account, and click Next; or, create a new Threads credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Threads endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by area.
Templates that say Nexla reads every page follow the after cursor in each response; all other templates make a single request. Date settings accept a date in yyyy-MM-dd format or a Unix timestamp, and default to the last 30 days ({now-30} to {now}). Fields settings list the fields Threads returns; the defaults cover the useful set, and the Threads API reference lists every field. Templates that need a Thread (Media) ID read one post; use List My Threads (Posts) to find the id.
Returns the profile of the connected Threads account: ID, username, name, biography, profile picture URL, and whether the account is verified. Use it to confirm which account the token belongs to.
Calls GET /v1.0/me?fields={Fields}.
Fields (required; default id,username,name,threads_profile_picture_url,threads_biography,is_verified): Comma-separated profile fields to return.
Lists the posts the connected account published in a date range, newest first, with text, media type, permalink, and timestamp. Use it to build a content inventory and to find post IDs.
Calls GET /v1.0/me/threads?fields={Fields}&since={Since}&until={Until}&limit={Page Size}.
Nexla follows the after cursor in each response and reads every page automatically.
Fields (required; default id,media_product_type,media_type,media_url,permalink,owner,username,text,timestamp,shortcode,thumbnail_url,children,is_quote_post,quoted_post,reposted_post,alt_text,link_attachment_url,has_replies,reply_audience,topic_tag): Comma-separated post fields to return. Default is the useful set; see the Threads docs for every field.
Since (required; default {now-30}): Start date (yyyy-MM-dd or Unix time); posts on/after it. Default 30 days ago. Earliest 2023-07-05.
Until (required; default {now}): End date (yyyy-MM-dd or Unix time), not later than now. Default today.
Page Size (required; default 100): The number of records per page, up to 100.
Returns one post or reply by its media ID, with its text, media, permalink, timestamp, reply status, and hide status.
Calls GET /v1.0/{Thread (Media) ID}?fields={Fields}.
Thread (Media) ID (required): The numeric Threads media ID of a post: the id returned by List My Threads (Posts).
Fields (required; default id,media_product_type,media_type,media_url,permalink,owner,username,text,timestamp,shortcode,thumbnail_url,children,is_quote_post,alt_text,link_attachment_url,has_replies,is_reply,root_post,replied_to,hide_status,reply_audience,quoted_post,reposted_post,topic_tag): Comma-separated post fields to return. Default is the useful set; see the Threads docs for every field.
Searches public Threads posts for a keyword or topic tag, and returns the top or most recent matches.
Calls GET /v1.0/keyword_search?q={Keyword}&search_type={Search Type}&search_mode={Search Mode}&since={Since}&until={Until}&limit={Max Results}&fields={Fields}.
Keyword (required): The keyword or keywords to search for, or a topic tag when Search Mode is TAG.
Search Type (required; default TOP): TOP (most popular, default) or RECENT. Options: TOP, RECENT.
Search Mode (required; default KEYWORD): KEYWORD (default) or TAG (topic tag). Options: KEYWORD, TAG.
Since (required; default {now-30}): Start date (yyyy-MM-dd or Unix time); posts on/after it. Default 30 days ago. Earliest 2023-07-05.
Until (required; default {now}): End date (yyyy-MM-dd or Unix time), not later than now. Default today.
Max Results (required; default 100): The maximum number of results, up to 100.
Fields (required; default id,media_product_type,media_type,media_url,permalink,username,text,timestamp,shortcode,has_replies,is_quote_post,is_reply,root_post,replied_to,topic_tag): Comma-separated post fields to return. Default is the useful set; see the Threads docs for every field.
Returns a single page of up to 100 results. Needs the threads_keyword_search permission; until Meta approves the permission in App Review, only the connected account's own posts match. Meta limits keyword searches to 2,200 queries per 24 hours.
Lists public posts by other accounts that mention the connected account in a date range.
Calls GET /v1.0/me/mentions?fields={Fields}&since={Since}&until={Until}&limit={Page Size}.
Nexla follows the after cursor in each response and reads every page automatically.
Fields (required; default id,media_product_type,media_type,media_url,permalink,username,text,timestamp,shortcode,thumbnail_url,children,is_quote_post,quoted_post,reposted_post,alt_text,link_attachment_url,topic_tag): Comma-separated post fields to return. Default is the useful set; see the Threads docs for every field.
Since (required; default {now-30}): Start date (yyyy-MM-dd or Unix time); posts on/after it. Default 30 days ago. Earliest 2023-07-05.
Until (required; default {now}): End date (yyyy-MM-dd or Unix time), not later than now. Default today.
Page Size (required; default 100): The number of records per page, up to 100.
Needs the threads_manage_mentions permission. Until your app passes App Review, only mentions by other testers of the app are returned.
Returns the connected account's usage and limits over a rolling 24 hours for posts (250), replies (1,000), and deletions. Check it before bulk publishing or replying from another tool.
Calls GET /v1.0/me/threads_publishing_limit?fields={Fields}.
Fields (required; default quota_usage,config,reply_quota_usage,reply_config,delete_quota_usage,delete_config): Comma-separated quota fields to return.
Lists the replies the connected account posted in a date range, with the post each one answers (replied_to and root_post).
Calls GET /v1.0/me/replies?fields={Fields}&since={Since}&until={Until}&limit={Page Size}.
Nexla follows the after cursor in each response and reads every page automatically.
Fields (required; default id,media_product_type,media_type,media_url,permalink,username,text,timestamp,shortcode,has_replies,root_post,replied_to,is_reply,is_reply_owned_by_me,reply_audience): Comma-separated reply fields to return. Default is the useful set; see the Threads docs for every field.
Since (required; default {now-30}): Start date (yyyy-MM-dd or Unix time); posts on/after it. Default 30 days ago. Earliest 2023-07-05.
Until (required; default {now}): End date (yyyy-MM-dd or Unix time), not later than now. Default today.
Page Size (required; default 100): The number of records per page, up to 100.
Lists the top-level replies to one post, with author username, text, timestamp, and hide status. Use it for moderation and reply analysis.
Calls GET /v1.0/{Thread (Media) ID}/replies?fields={Fields}&reverse={Newest First}.
Nexla follows the after cursor in each response and reads every page automatically.
Thread (Media) ID (required): The numeric Threads media ID of a post: the id returned by List My Threads (Posts).
Fields (required; default id,media_product_type,media_type,media_url,permalink,username,text,timestamp,shortcode,has_replies,root_post,replied_to,is_reply,is_reply_owned_by_me,hide_status,reply_audience,topic_tag): Comma-separated reply fields to return. Default is the useful set; see the Threads docs for every field.
Newest First (required; default true): true returns the newest replies first; false returns the oldest first. Options: true, false.
Lists every reply under one post, both top-level and nested, as a flat list linked by replied_to and root_post. Use it to read a whole discussion.
Calls GET /v1.0/{Thread (Media) ID}/conversation?fields={Fields}&reverse={Newest First}.
Nexla follows the after cursor in each response and reads every page automatically.
Thread (Media) ID (required): The numeric Threads media ID of a post: the id returned by List My Threads (Posts).
Fields (required; default id,media_product_type,media_type,media_url,permalink,username,text,timestamp,shortcode,has_replies,root_post,replied_to,is_reply,is_reply_owned_by_me,hide_status,reply_audience,topic_tag): Comma-separated reply fields to return. Default is the useful set; see the Threads docs for every field.
Newest First (required; default true): true returns the newest replies first; false returns the oldest first. Options: true, false.
Lists the replies waiting for your approval on a post that has reply approvals turned on. Use it to find the reply IDs for the Approve or Ignore Pending Reply destination.
Calls GET /v1.0/{Thread (Media) ID}/pending_replies?fields={Fields}&reverse={Newest First}&approval_status={Approval Status}.
Nexla follows the after cursor in each response and reads every page automatically.
Thread (Media) ID (required): The numeric Threads media ID of a post: the id returned by List My Threads (Posts).
Fields (required; default id,media_product_type,media_type,media_url,permalink,username,text,timestamp,shortcode,has_replies,root_post,replied_to,is_reply,is_reply_owned_by_me,hide_status,reply_audience,topic_tag,reply_approval_status): Comma-separated reply fields to return. Default is the useful set; see the Threads docs for every field.
Newest First (required; default true): true returns the newest replies first; false returns the oldest first. Options: true, false.
Approval Status (required; default pending): pending returns replies waiting for approval; ignored returns replies you ignored. Options: pending, ignored.
Returns the connected account's totals for a date range, with one record per metric: views (as a daily series), likes, replies, reposts, quotes, and clicks.
Calls GET /v1.0/me/threads_insights?metric={Metrics}&since={Since}&until={Until}.
Metrics (required; default views,likes,replies,reposts,quotes): Comma-separated metrics: any of views, likes, replies, reposts, quotes, and clicks.
Since (required; default {now-30}): The start date. Threads has insights data from April 13, 2024 on.
Until (required; default {now}): End date (yyyy-MM-dd or Unix time), not later than now. Default today.
Returns the connected account's current total follower count as one record (total_value.value). Threads returns the live total, so this template takes no date range.
Calls GET /v1.0/me/threads_insights?metric=followers_count.
Returns the lifetime metrics of one post, with one record per metric: views, likes, replies, reposts, quotes, and shares.
Calls GET /v1.0/{Thread (Media) ID}/insights?metric={Metrics}.
Thread (Media) ID (required): The numeric Threads media ID of a post: the id returned by List My Threads (Posts).
Metrics (required; default views,likes,replies,reposts,quotes,shares): Comma-separated metrics: any of views, likes, replies, reposts, quotes, and shares.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Threads data sources can also be manually configured to ingest data from any valid Threads API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Threads data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Threads destination, and select the Send to Destination option from the menu. Select the Threads connector from the list of available destination connectors, then select the credential that will be used to connect to your Threads account, and click Next; or, create a new Threads credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Threads endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
These templates need the threads_manage_replies permission and change what people see on your posts. Test them with a single record before sending a full Nexset. The connector does not publish or delete posts.
Approve or Ignore Pending Reply
Approves a pending reply, which makes it public, or ignores it.
Sends POST /v1.0/{reply_id}/manage_pending_reply?approve={approve}.
Each record must contain reply_id (the ID of the pending reply) and approve (true to approve, false to ignore). Nexla sends one request per record.
Use List Pending Replies to find pending reply IDs.
Threads destinations can also be manually configured to send data to any valid Threads API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Threads endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Threads endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.