BTN API
A single JSON-RPC endpoint over the tracker: torrents, series, forums, your inbox and your stats. 24 methods, fully documented from the server's own schema.
Start here
Every call is a POST to https://api.broadcasthe.net/ with the method name in the body. The one method that needs no credentials is getChangelog, so it is the quickest way to confirm you can reach the endpoint at all:
curl -sS -X POST https://api.broadcasthe.net/ \
-H 'Content-Type: application/json' \
-d '{"id":1,"method":"getChangelog","params":{}}'Everything else takes an API key, issued from your profile on the site, as the key parameter.
Browse by group
The v1 reference is one page per method, grouped by what they operate on.
Before your first authenticated call
Two things surprise almost everyone, and both are worth knowing before you write any code against this API.
Your key is bound to your IP. A call from an address the tracker has not seen before fails with -32004, and the address is filed for approval rather than accepted. Approve it from your notices on the site, then retry. This is the most common first-run failure by a wide margin — a correct key from a new host still fails.
Numbers arrive as strings. Scalars are stringified on the way out of the database, so "12345" rather than 12345, throughout. The reference marks these as string (numeric). Parse, don't assume.
How this documentation is built
The shapes on these pages are not written by hand. Each API version generates a JSON Schema from its own source and publishes it; this site builds from that artifact. The same schema is checked against live production traffic, so a response that stopped matching its documentation is a reported defect rather than something a reader discovers.
The migration guide covers what changes between majors, and what to do about it.