The Seedr API is opening up

The same API that runs our Sonarr, Radarr, Roku, and Kodi integrations is now available on request to any Premium or V2 user. No long form, no case-by-case review queue. Email support, we enable it, you build.

Why we built this

The Seedr API has been quietly powering everything for a while. The *arr stack integrations talk to it. The new Roku and Kodi apps talk to it. A few upcoming integrations we have not announced yet talk to it. It is the same production pipe in every case.

Originally we gated it tightly: tell us what you want to build, and we enabled access by hand. That made sense when the API was young and we needed to know exactly what was hitting which endpoint. It made less sense once it stabilised.

The pain that forced a change:

• Plugin authors wanted to prototype over a weekend, not email and wait.
• Home-lab tinkerers had a dashboard idea at 2am and lost momentum by Monday.
• Integration partners wanted a predictable story they could document.

So we stopped gating by use case and started gating by plan. Simpler for you. Simpler for us.

What changed

Before: Per-project approval. Describe your use case. Wait for a human.

Now:

• Premium or V2? Email support with the subject line "API access." We enable it on your account.
• Same endpoints our plugins use. No sandbox, no separate staging. You are hitting production from the first request.
• Same rate limits and behaviours our own integrations run against. If it works for Sonarr, it will work for your tool.
• Not on Premium but building something real? Email anyway. We do read those and make exceptions for genuine projects.

What the API actually does

Short version: anything the Seedr web UI can do, the API can do. That includes:

• Add download links and URLs to your account.
• List, move, rename, and delete files and folders.
• Fetch direct streaming URLs for playback or casting.
• Read account state (storage used, active transfers, completed history).
• Manage folders as structured objects (not just paths).

It is the same API our Sonarr and Radarr connectors use, so if you have seen those tools work, you have seen what the API can do.

How to use it today

Three steps.

1. Confirm your plan. You need to be on a paid plan (Basic, Pro, Master, or Gold) or in V2 alpha. Free accounts are not eligible by default. Upgrade at /pricing if needed.
2. Email support. From the email on your Seedr account, message _{support@seedr.cc} with the subject line exactly: _{API access}. A short sentence about what you are building helps but is not required for Premium users.
3. We enable it on your account. You will get a confirmation email with a pointer to the docs and your credentials. Turnaround is usually 1 business day.

After that:

• Read the endpoint docs.
• Write your first request against your own account.
• Build.

If you are prototyping a public plugin or a shared integration, tell us in the email. We will keep an eye out for edge cases on your account and loop you in if anything in the API changes in a breaking way.

Roadmap

What is coming next:

• Self-serve keys in the account UI so you do not need to email us at all.
• Per-key scopes so you can issue a read-only key to one tool and a full-access key to another.
• Webhook support for events like "save complete" or "storage 90% full."
• Public OpenAPI spec for autogenerated client libraries.

Honest limit: the API is production-only. There is no public sandbox yet. If you need to test without touching your real account, use a free account for development and your main account for production.

Build the thing

We like seeing what people do with this. If you build something worth sharing, let us know and we will help you reach our community.