Odysee Trending API
API health
- 24h health
- Normal
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
See what is trending on Odysee, with no input. Each item has title, channel, duration, views, likes and publish time. Order is the only position signal. The trending algorithm is not explained, and no history is kept between calls.
Send POST https://api.everyinfra.com/api/v1/social with platform set to odysee and action set to trending. Price $1.39 per 1,000 requests ($0.001389 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 Odysee Trending endpoint (odysee/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 odysee and action to trending, and put the parameters inside params.
- No required parameters.
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, title, description, channel_name, channel_id, channel_url, url, thumbnail_url, duration_seconds, duration_sec, view_count, like_count; 16 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=odysee.
- Example request body:
{
"platform": "odysee",
"action": "trending",
"params": {}
}
- Price: $1.39 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
#| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | odysee | Platform identifier, fixed value. |
action | body | string | Yes | trending | Capability identifier, fixed value. |
limit | body.params | integer (1–50) | No | 20 | The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
Code samples
#curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "odysee",
"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
#{ "id": "req_…", "platform": "odysee", "action": "trending", "results": [ { "id": "02ac1ee63979e9c7a06e3c370ffede4403fb8015", "title": "BLEACH. Capítol 79. La decisió, de morir de la Yoshino.", "description": "En Renji i l'Ichigo passaran tota la nit barallant-se mentre la Yoshino s'escapa tramant alguna cosa... Però no comptarà amb la presència d'en Kariya. A més, coneixerem un nou tipus d'insecte, els bitto.", "channel_name": "@•••", "channel_id": "1d95839d87a85ceb284c14b60c83cffa5b37dd3a", "url": "https://odysee.com/@•••/BLEACH.-Capítol-79.-La-decisió-de-morir-de-la-Yoshino:02ac1ee639", "thumbnail_url": "https://thumbs.odycdn.com/7c824de50ec1938563f7e95adb515f1c.webp", "duration_seconds": 1475, "view_count": 0, "published_at": "2026-10-01T19:02:00+00:00", "platform": "odysee" }, { "id": "354beeec5da2088090d294affaaf04b459bebc5a", "title": "GT PSP- Specialtatin' My Weirdest Race Yet", "description": "short but sheet", "channel_name": "@•••", "channel_id": "968abcaf8050ed54e1e81d056b579040858dd19e", "url": "https://odysee.com/@•••/gt-psp-specialtatin-my-weirdest-race-yet:3", "thumbnail_url": "https://thumbs.odycdn.com/b95b9d21204fae1ab74154796e5e9b17.webp", "duration_seconds": 217, "view_count": 18540, "published_at": "2026-09-26T06:24:18+00:00", "tags": [ "gaming", "weird", "nissan" ], "platform": "odysee" } ], "count": 20, "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.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
title | Title. null when the platform has no titles (for example text-only posts). |
description | Summary or description, usually shorter than text. |
channel_name | Keeps the platform's own meaning |
channel_id | Keeps the platform's own meaning |
channel_url | Keeps the platform's own meaning |
url | Link to the record on the platform. |
thumbnail_url | Thumbnail link, lower resolution than image_url. |
duration_seconds | Duration in seconds. null for content that is not video or audio. |
duration_sec | Keeps the platform's own meaning |
view_count | Views or plays. null means not disclosed, not 0. |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
published_at | Keeps the platform's own meaning |
media_type | Keeps the platform's own meaning |
languages | Keeps the platform's own meaning |
tags | Array of tags. An empty array, not null, when there are none. |
platform | Source 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.