Odysee Posts by user API

POST

API health

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

Browse a channel's uploads on Odysee by name, @name or channel link, sorted by newest or by support-backed popularity, with views, likes, duration and tags. Anything after a colon (the claim ID) is dropped, so check the channel when names overlap.

Odysee Posts by user lists the uploads of one channel, named by username, with each item's title, description, link, thumbnail, length, views, likes, publish time, media type, languages and tags, plus the channel's name, ID and link. Use it to follow a creator who publishes on Odysee, archive or audit a channel's output, or compare what a channel posts there with its output elsewhere.

username takes the channel name with or without the @, or a channel link that contains @name. Set sort to newest for publish order or popular for a ranking tied to the support amounts behind each item. duration_seconds is null for items that are not video or audio, and a null view_count or like_count is an undisclosed figure, to be kept apart from a real zero.

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

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Odysee Posts by user endpoint (odysee/user_posts).

Endpoint contract:
- 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 user_posts, and put the parameters inside params.
- Required parameters:
  - username: Specifies the channel identifier for the user_posts action. Accepts a channel name, @name, or a full Odysee channel URL. Anything after a colon (the claim ID) is dropped, so check the result when channel names overlap.
- Optional parameters:
  - sort: Sorts content for the user_posts and tag actions. Allowed values are newest (sorts by publish date) and popular (sorts by support amount metrics). Note that popular does not measure total view count or like count. (allowed: newest / popular)
  - limit: The most rows to return in this call, an integer from 1 to 200. 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": "user_posts",
  "params": {
    "username": "@lbry"
  }
}
- 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

NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYesodyseePlatform identifier, fixed value.
actionbodystringYesuser_postsCapability identifier, fixed value.
usernamebody.paramsNot declaredYes-Specifies the channel identifier for the user_posts action. Accepts a channel name, @name, or a full Odysee channel URL. Anything after a colon (the claim ID) is dropped, so check the result when channel names overlap.
sortbody.paramsenumNo-Sorts content for the user_posts and tag actions. Allowed values are newest (sorts by publish date) and popular (sorts by support amount metrics). Note that popular does not measure total view count or like count.Allowed valuesnewestpopular
limitbody.paramsinteger (1–200)No20The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

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": "odysee",
  "action": "user_posts",
  "params": {
    "username": "@lbry"
  }
}'

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

Response example

Real response

Captured September 26, 2026 at 08:56 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.

json
{
  "id": "req_…",
  "platform": "odysee",
  "action": "user_posts",
  "results": [
    {
      "id": "7aa2220e2d1d5942b90240dec25e925b11a8ea04",
      "title": "Odysee LBRY Usage Agreement",
      "channel_name": "@lbry",
      "channel_url": "https://odysee.com/@(已隐去)",
      "url": "https://odysee.com/@lbry/odyseelbryagreement",
      "thumbnail_url": "https://thumbs.odycdn.com/b18ae7090861d94d6c7081969e970348.webp",
      "published_at": "2023-10-19T20:01:10+00:00",
      "media_type": "application/pdf",
      "languages": [
        "en"
      ],
      "platform": "odysee"
    },
    {
      "id": "d434ed74a2a4874358eca22702dd25289d8fc1cd",
      "title": "The End of LBRY Inc.",
      "channel_name": "@lbry",
      "channel_url": "https://odysee.com/@(已隐去)",
      "url": "https://odysee.com/@lbry/theendoflbryinc",
      "thumbnail_url": "https://thumbs.odycdn.com/e9740b8e51f33735964d1cccbc53b70d.webp",
      "published_at": "2023-10-19T16:44:47+00:00",
      "media_type": "text/markdown",
      "languages": [
        "en"
      ],
      "tags": [
        "lbry"
      ],
      "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.

FieldMeaning
idThe record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
titleTitle. null when the platform has no titles (for example text-only posts).
descriptionSummary or description, usually shorter than text.
channel_nameKeeps the platform's own meaning
channel_idKeeps the platform's own meaning
channel_urlKeeps the platform's own meaning
urlLink to the record on the platform.
thumbnail_urlThumbnail link, lower resolution than image_url.
duration_secondsDuration in seconds. null for content that is not video or audio.
duration_secKeeps the platform's own meaning
view_countViews or plays. null means not disclosed, not 0.
like_countLikes. null means the platform or this capability does not disclose it; it is not 0.
published_atKeeps the platform's own meaning
media_typeKeeps the platform's own meaning
languagesKeeps the platform's own meaning
tagsArray of tags. An empty array, not null, when there are none.
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

What can I pass as username?

The channel name in any of three forms: name, @name, or an Odysee channel link that contains @name. For example, lbry and @lbry read the same channel. Pass one channel per call and keep channel_id from the results as the key for what you store.

Does popular mean most viewed?

No. popular ranks items by a measure tied to the support amounts they received on Odysee, not by views or likes. To rank by audience, fetch with newest and order the rows by view_count or like_count yourself.

How do I keep only items in one language?

Filter on languages, which lists each item's content languages, and on media_type to keep videos apart from other formats. tags is an empty array rather than null when an item has none, so it is safe to filter on as well.

Errors and billing

401
Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422
Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402
Insufficient balance. Top up first.
429
The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503
Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty
The request completed without data and is not charged (billing.reason = empty_result_refunded).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

  • Odysee: Distinction Between Channel Names and Claim Identifiers ↗

    Odysee's naming documentation notes that the portion of a URL following a colon relates to the Claim of a specific channel or content item, requiring full identifiers to distinguish same-name addresses. When extracting channel names, this interface removes that portion; citing this documentation does not imply support for precise Claim queries.

    Checked 2026-09-04