Threads API opens to all developers
What changed
The Threads API documentation became public on April 8, 2024 and the API opened to all developers on June 18, 2024. A graph.threads.net domain with v1.0 and Threads access tokens was introduced on June 7, 2024. Meta's sample app on GitHub moved its API calls to graph.threads.com and its authorization URL to www.threads.com in commit 583bfaa on March 23, 2026, while Meta's Postman collection in the same repository still uses graph.threads.net.
What it means
Any developer can now build Threads publishing integrations, so scheduling tools can add Threads support.
Who is affected
Schedulers and anyone wanting to automate Threads posting.
What to do by 18 Jun 2024
Developers: create an app with the Threads use case; Meta's own GitHub uses both graph.threads.net (Postman collection) and graph.threads.com (sample app since March 2026), so test which host your calls use. Users: check whether your scheduler supports Threads.
Primary sources
- Meta for Developers: Threads API changelog
- Meta on GitHub: Threads sample app moves to threads.com (fbsamples/threads_api commit 583bfaa, 23 Mar 2026)
- Meta on GitHub: Threads API Postman collection, api_host still graph.threads.net (line 3640)
Get an email when a new API change is added
Follow new entries with the RSS feed. Each platform also has its own feed, for example X or Meta.