API · /odysee-api

Odysee API

healthy 3,910 Subscribers

Live data for Odysee, the decentralised video platform built on the LBRY blockchain — a censorship-resistant YouTube alternative — served straight from the public Odysee/LBRY backend with no key and nothing cached. The channel endpoint resolves a @channel handle to its title, description, avatar and cover art, the number of videos it has published, the LBC staked on it and its tags and languages: @Odysee resolves to the official channel with 134 published claims. The videos endpoint lists a channel's most recent uploads with the title, description, duration, thumbnail, release date and a ready-to-open watch URL. The search endpoint searches the whole platform for videos by keyword, returned in trending order with their channel, title and link. This is the channel-and-video discovery layer for any app building on decentralised, creator-owned video — read live on-chain from the LBRY network, nothing stored. Distinct from centralised-platform and other video APIs — this is the on-chain Odysee/LBRY catalogue. 4 endpoints.

#odysee #lbry #video #decentralized #social #creator #web3

api.oanor.com/odysee-api

Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/odysee-api/openapi.json

/api/odysee-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy

Uptime: 100.00%; Server probes · 24h
Avg latency: 651 ms; Server probes · 24h
Subscribers: 3,910; active
Total calls: 16; last 7 days

Full status page → · 8 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

12,500 calls / month
3 requests / second
Hard cap (429 above quota, no overage)
12,500 calls/month
3 req/sec
Channels, videos & search
No credit card

Starter

€6.00 /month

155,000 calls / month
8 requests / second
Hard cap (429 above quota, no overage)
155,000 calls/month
8 req/sec
Video lists, durations & watch URLs
Email support

Pro

€15.00 /month

690,000 calls / month
15 requests / second
Hard cap (429 above quota, no overage)
690,000 calls/month
15 req/sec
Creator & discovery pipelines
Priority support

Scale

€37.00 /month

3,450,000 calls / month
30 requests / second
Hard cap (429 above quota, no overage)
3,450,000 calls/month
30 req/sec
Decentralised-video scale
Dedicated SLA

Built by

PremiumApi

Related APIs

Other APIs with overlapping tags.

RUTUBE API

Live data from RUTUBE, the largest Russian video platform with tens of millions of users — served straight from its public web API, no key, nothing cached. Search videos by query and get their view counts, duration and channel; pull one video's full stats (views, duration, publish date, category and author); and list a channel's recent uploads by its person id. A distinct video-platform feed, separate from YouTube, Vimeo, Bilibili, Dailymotion, PeerTube and other video APIs.

api.oanor.com/rutube-api

Coub API

Live looping-video data from Coub, the social platform built around short, seamlessly looping video clips, served straight from Coub's public API — no key, nothing cached. The explore endpoint returns the trending feed (rising, hot or random coubs across the whole site), each with its title, view, like and recoub counts, duration, channel and tags, plus ready-to-use loop-preview image URLs at several sizes. The tag endpoint returns the newest coubs for a tag — cats, gaming, music — the hashtag feed of Coub. The channel endpoint returns a creator's profile (title, follower and recoub counts) together with their most recent coubs. Every clip comes back cleaned up: the watch URL, the channel handle, the human tags and several preview-image sizes. Everything is live from Coub, nothing stored. This is the looping-video discovery layer for any feed, meme, moodboard, embed or social app. Distinct from YouTube, Vimeo, Dailymotion and other video APIs — this is Coub's looping clips by trend, tag and channel. 3 endpoints, no key on our side.

api.oanor.com/coub-api

Time-lapse API

Time-lapse photography maths as an API, computed locally and deterministically — the clip-length, interval and storage numbers a photographer, filmmaker or camera app plans a sequence with. The clip-length endpoint trades a long shoot for a short clip: the frames captured = the shoot duration ÷ the interval, and the clip length = those frames ÷ the playback frame rate — shooting for 60 minutes at one frame every 5 seconds gives 720 frames, and at 24 fps that plays back in 30 seconds, a 120× speed-up. Longer intervals compress time harder but can stutter on fast motion. The interval endpoint works backwards from a target clip: the frames needed = the target clip length × the frame rate, and the interval = the shoot duration ÷ those frames, so a 60-minute shoot for a 20-second clip at 24 fps needs 480 frames, one every 7.5 seconds. The storage endpoint sizes the card and disk: total storage = the frame count × the size of one frame, and because time-lapse shoots full-resolution stills (RAW ~20–30 MB each), 720 RAW frames at 25 MB is about 18 GB for a single 30-second clip — which is why a long lapse eats cards fast. Everything is computed locally and deterministically, so it is instant and private. Ideal for time-lapse and intervalometer apps, photography-planning tools, and production calculators. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For video bitrate and file size use a bitrate API.

api.oanor.com/timelapse-api

Bitrate & Transfer API

Media, file-size and data-transfer maths as an API. The file-size endpoint relates bitrate, duration and file size: give any two and it computes the third — so you can find the size of a video at a given bitrate and length, the bitrate of a file of known size and length, or how long a file will play. The transfer-time endpoint computes how long a file takes to download or upload over a given bandwidth (with optional protocol overhead), or the bandwidth needed to move it within a target time. The storage endpoint works out how many hours of media at a bitrate, or how many items of a given size, fit in a storage capacity. Bitrates use decimal units (kbps, Mbps, Gbps) and sizes are reported in both decimal (KB/MB/GB/TB) and binary (KiB/MiB/GiB/TiB). Everything is computed locally and deterministically, so it is instant and private. Ideal for video and audio encoding, streaming and CDN planning, storage and backup sizing, and download-time estimates. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is bitrate and transfer maths; for plain byte-unit conversion use a bytes API.

api.oanor.com/bitrate-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Odysee API?

Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Odysee API with the x-oanor-key header. No credit card needed for the free tier.

What's the rate limit for Odysee API?

Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.

How much does Odysee API cost?

Odysee API has a free tier with 100 calls / month. Paid plans start at €6.00 / month with higher quotas and faster rate limits.

Can I cancel my subscription anytime?

Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.

Is Odysee API GDPR-compliant?

All requests to Odysee API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Odysee 3

Meta 1

Pick an endpoint from the list on the left to see its details and try it.

GET /v1/channel

Resolve a channel

Playground

Parameters

Custom headers

Language: Client:

GET /v1/search

Search the platform for videos

Playground

Parameters

Custom headers

Language: Client:

GET /v1/videos

A channel's recent uploads

Playground

Parameters

Custom headers

Language: Client:

GET /v1/meta

Spec

Playground

Custom headers

Language: Client:

Code snippets

curl https://api.oanor.com/odysee-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."

const res = await fetch("https://api.oanor.com/odysee-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();

$ch = curl_init("https://api.oanor.com/odysee-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);

import requests
r = requests.get(
    "https://api.oanor.com/odysee-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

New thread

📌 Pinned 🔒 Locked

· ·

🔒 This thread is locked — no new replies.

No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.

Pick a key

Plaintext is shown once at creation — use the prefix as a reminder.

Odysee API

API health

Pricing

Built by

Related APIs

RUTUBE API

Coub API

Time-lapse API

Bitrate & Transfer API

Frequently asked questions

Parameters

Parameters

Parameters

Code snippets

Ratings

Discussion

New thread

📌 🔒

Support

Open new ticket

Your cookie choices