Threads

API data_source: threads_auto

Configuring a Job

The query type decides how a Threads Job searches: across the whole platform, by hashtag, or from one account. Each Job uses one query type, set in query.query_type (the Query Type field on the Portal's New Job form), with query.platform set to threads. To cover more than one, create a Job for each.

• Search by topic. keyword finds posts that mention your terms anywhere on Threads.
• Search by hashtag. hashtag finds posts tagged with one hashtag.
• Follow an account. user collects posts from one account.
• Full control. advanced takes a Lucene query, so you can combine terms and search specific fields. See Advanced Search Query.

Query types

The query object for each type:

{"platform": "threads", "query_type": "keyword", "query": "electric vehicles"}
{"platform": "threads", "query_type": "hashtag", "query": "technology"}
{"platform": "threads", "query_type": "user", "query": "starbucks"}
{"platform": "threads", "query_type": "advanced", "query": "(electric OR hybrid) AND vehicle"}

Job options

Advanced Search Query

The advanced query type takes a Lucene query in query.query. You can search any field in the Datastreamer unified schema; a term without a field searches content.body.

{ "platform": "threads", "query_type": "advanced", "query": "(\"electric vehicle\" OR ev) AND content.hashtags:charging" }

Do not put dates in the query. Set the date range with query_from and query_to on the Job instead.

See the Schema Reference for field names.

Example Job request

curl --request POST \
  --url 'https://api.platform.datastreamer.io/api/pipelines/{PIPELINE_ID}/components/{COMPONENT_ID}/jobs?ready=true' \
  --header 'apikey: <your-api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "job_name": "threads-example",
  "component_name": "threads-auto",
  "query": {
    "platform": "threads",
    "query_type": "keyword",
    "query": "electric vehicles",
    "prioritization": "coverage"
  },
  "data_source": "threads_auto",
  "job_type": "onetime",
  "query_from": "2026-10-01T00:00:00Z",
  "query_to": "2026-10-02T00:00:00Z",
  "max_documents": 1000
}'

Refer to the Job creation documentation for full configuration details: Creating Jobs

API Reference: Create a Job

What is Collected

Each document returned from the Threads source represents a post or reply. Fields are mapped to the Datastreamer unified schema and include content text, author metadata, engagement metrics (likes, replies, reposts), and post date.

Platform-specific fields are available under the threads schema namespace. See the Schema Reference for field details.

Troubleshooting

Job fails or returns no data

• Check that the query or account target is valid and publicly accessible
• Verify the date range contains data
• Review Job logs for specific errors

Unexpectedly high document counts

• Add more specific filters to narrow the query
• Set a document limit on the Job
• Review the DVU pricing page

Provider switch noted in Job logs

• This is expected behavior. If a provider is unavailable, the Job is routed to an alternative automatically. No action is required.

Related

• Sources Overview
• Creating Jobs
• Data Volume Units
• Direct Integrations: use if you need a specific provider directly