You may use the Threads API to enable people to create and publish content on a person’s behalf on Threads, and to display those posts within your app solely to the person who created it.
The Threads API can be accessed by either graph.threads.com or graph.threads.net.
Calls within 24 hours = 4800 * Number of Impressions720000 * number_of_impressions for total_cputime
2880000 * Number of Impressions for total_timeThreads profiles are limited to 250 API-published posts within a 24-hour moving period. Carousels count as a single post. This limit is enforced on the POST /{threads-user-id}/threads_publish endpoint when attempting to publish a media container. We recommend that your app also enforces the publishing rate limit, especially if your app allows app users to schedule posts to be published in the future.
To check a profile's current Threads API rate limit usage, query the GET /{threads-user-id}/threads_publishing_limit endpoint.
Note: This endpoint requires the threads_basic and threads_content_publish permissions.
| Name | Description |
|---|---|
| Threads publishing count over the last 24 hours. |
| Threads publishing rate limit config object, which contains the |
curl -s -X GET \ "https:graph.threads.net/v1.0/<THREADS_USER_ID>/threads_publishing_limit?fields=quota_usage,config&access_token=<ACCESS_TOKEN>"
{
"data": [
{
"quota_usage": 4,
"config": {
"quota_total": 250,
"quota_duration": 86400
}
}
]
}
Threads profiles are limited to 1,000 replies within a 24-hour moving period.
To check a profile's current Threads replies rate limit usage, query the GET /{threads-user-id}/threads_publishing_limit endpoint. See the Reply Management documentation for more information.
Note: This endpoint requires the threads_basic, threads_content_publish, and threads_manage_replies permissions.
| Name | Description |
|---|---|
| Threads reply publishing count over the last 24 hours. |
| Threads reply publishing rate limit config object, which contains the |
curl -s -X GET \ "https://graph.threads.net/v1.0/<THREADS_USER_ID>/threads_publishing_limit?fields=reply_quota_usage,reply_config&access_token=<ACCESS_TOKEN>"
{
"data": [
{
"reply_quota_usage": 1,
"reply_config": {
"quota_total": 1000,
"quota_duration": 86400
}
}
]
}
Threads profiles are limited to 100 deletions within a 24-hour moving period.
To check a profile's current Threads deletion rate limit usage, query the GET /{threads-user-id}/threads_publishing_limit endpoint. See the Delete Posts documentation for more information.
Note: This endpoint requires the threads_basic and threads_delete permissions.
| Name | Description |
|---|---|
| Threads deletion count over the last 24 hours. |
| Threads deletion rate limit config object, which contains the |
curl -s -X GET \ "https://graph.threads.net/v1.0/<THREADS_USER_ID>/threads_publishing_limit?fields=delete_quota_usage,delete_config&access_token=<ACCESS_TOKEN>"
{
"data": [
{
"delete_quota_usage": 1,
"delete_config": {
"quota_total": 100,
"quota_duration": 86400
}
}
]
}
Threads profiles are limited to 500 location searches within a 24-hour moving period.
To check a profile's current Threads location search rate limit usage, query the GET /{threads-user-id}/threads_publishing_limit endpoint. See the Location Search documentation for more information.
Note: This endpoint requires the threads_basic and threads_location_tagging permissions.
| Name | Description |
|---|---|
| Threads location search count over the last 24 hours. |
| Threads location search rate limit config object, which contains the |
curl -s -X GET \ "https://graph.threads.net/v1.0/<THREADS_USER_ID>/threads_publishing_limit?fields=location_search_quota_usage,location_search_config&access_token=<ACCESS_TOKEN>"
{
"data": [
{
"location_search_quota_usage": 1,
"location_search_config": {
"quota_total": 500,
"quota_duration": 86400
}
}
]
}