Platforms / Social media
Threads data, through one API.
Explore 6 documented endpoints for Threads. Choose an operation, inspect its inputs, and test the response before adding it to your application.
Threads API
Public-data endpoint catalog
- Documented endpoints
- 6
- Credits per success
- From 1
STARTING ENDPOINT
GET /v1/threads/profile
One API key. Shared response metadata. Availability varies by operation during preview.
API catalog
Choose the data you need.
Open an endpoint for its request parameters, examples, and credit cost. Each operation has its own data contract.
Coverage is rolling out during preview. Test the endpoint you need before integrating. Unavailable operations return an explicit error and use no credits.
Threads Profile API
Retrieve the public profile details available for a Threads account.
Threads User Posts API
List the public posts returned for a Threads account.
Threads Post API
Retrieve a public Threads post and its available content and metadata.
Threads Search API
Search Threads using the documented query and filters, and return structured results.
Threads Post Comments API
Retrieve available comments for the specified Threads content.
Threads Search Users API
Find matching Threads results using this operation’s documented search parameters.
API playground
Inspect a response before you integrate.
Select an operation and enter its required parameters. Browser tests are protected by Turnstile; an unavailable source returns an error instead of sample data.
curl -X GET 'https://socialquery.dev/v1/threads/profile?handle=zuck' \
-H "x-api-key: $SOCIALQUERY_API_KEY"// Edit the params above and hit "Try it" to run a live request against the APIFrom browser to code
Use the same request in your application.
- 01 Create a SocialQuery API key and store it on your server.
- 02 Send the documented inputs with your x-api-key header.
- 03 Check the response status, data, credits, and request ID.
Example request
curl -X GET 'https://socialquery.dev/v1/threads/profile?handle=zuck' \
-H "x-api-key: $SOCIALQUERY_API_KEY"FAQ
Questions teams ask
Are all Threads endpoints available?
+
This is the documented catalog. Live coverage is rolling out during preview and depends on the operation. Test the specific request you need before using it in production.
How are requests charged?
+
The endpoint lists its credit cost before you call it. The response includes credits used and your remaining balance. Unavailable operations use no credits.
Do I need a separate key for each platform?
+
No. Use your SocialQuery key for available endpoints across the catalog. Keep it server-side and pass it in the x-api-key header.
Explore related platforms
Next step
Build with Threads data.
Start with a documented endpoint and 100 free signup credits.