POST

API health

24h health
Normal
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Normal

Last 24 hours

Last 30 days

Read the topics trending on Threads now. Each row has rank, id, title, a one-line summary, the search keyword, post_count and post_count_label, image_url, url and trend_type. Pass a row's keyword, and its id as trend_id, to trend_posts to read its posts. One call returns the list of up to 15 trends, with no paging, and limit has no effect.

Send POST https://api.everyinfra.com/api/v1/social with platform set to threads and action set to trending. Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

#
Please help me write a data collection script with the EveryInfra Threads Trending endpoint (threads/trending).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to threads and action to trending, and put the parameters inside params.
- No required parameters.
- Returns a list of records. Main fields of each record: rank (Position in this result, starting from…), id, title (trending: the trend's title), summary (trending: a one-line summary of the tre…), keyword (trending: the trend's search term), post_count, post_count_label (trending: the post count text as the pa…), image_url (trending: image for the trend), url, trend_type (trending: the trend type as the platfor…).
- Example request body:
{
  "platform": "threads",
  "action": "trending",
  "params": {}
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

#
NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYesthreadsPlatform identifier, fixed value.
actionbodystringYestrendingCapability identifier, fixed value.

Code samples

#
bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "threads",
  "action": "trending",
  "params": {}
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

#
No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.
json
{  "id": "req_…",  "platform": "threads",  "action": "trending",  "results": [    {      "rank": …,      "id": …,      "title": …,      "summary": …,      "keyword": …,      "post_count": …,      "post_count_label": …,      "image_url": …,      "url": …,      "trend_type": …,      "platform": …    }  ],  "count": …,  "billing": {    "charged": …,    "charged_usd": …,    "balance_after_usd": …,    …  },  "quota": { … }}

Response fields

#

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

FieldMeaning
rankPosition in this result, starting from 1.
idThe record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
titletrending: the trend's title.
summarytrending: a one-line summary of the trend written by the platform.
keywordtrending: the trend's search term; pass it with id to trend_posts to read the posts under the trend. search_suggest: the text you typed, as sent.
post_countTotal posts. null means not disclosed, not 0.
post_count_labeltrending: the post count text as the page shows it, e.g. 11K posts.
image_urltrending: image for the trend; signed link that expires.
urlLink to the record on the platform.
trend_typetrending: the trend type as the platform gives it, e.g. decoupled.
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

Errors and billing

#
401
Missing or invalid key.
402
Insufficient balance. Top up first.
422
Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429
Per-minute request limit reached. Wait for Retry-After, then try again.
503
Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty
No data. No charge.

Errors

Google Analytics needs consent. Privacy