xREL.v3
xrel.to · Debrid · 1 record · JSON
xREL.v3 Debrid
caveatanonymousno cardD
| Free tier | The release lists are readable without an account; the JSON API at api.xrel.to answered our reader with HTTP 403 and a 5-word bot challenge instead of content. unit unlimited; metered on none |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable: release metadata, not an object |
| Retention | records persist; the release lists carry dated entries per category (console, TV, movies), newest first |
| Egress | no byte allowance: the site serves NFO text, screenshots and metadata, not files free_allowance: none |
| Identity | anonymous The HTML lists were readable without an account. The API's authentication requirement was not established beyond the 403 challenge. |
| Limits |
The challenge is the first obstacle, not a quota: the reader saw 'bot challenge' with a 5-word body at HTTP 403. |
| Binding | none An API challenge is not one of the seven constraints and no byte quota exists; the client meets the challenge first and would then meet an unpublished rate. |
| Interface | rest A documented JSON API under api.xrel.to/v2/ (the v2 index path returned 404 from nginx, and /v2/ returned a 403 challenge), plus HTML release lists per category. endpoint: https://api.xrel.to/v2/ |
| Tooling | HTTP client for the API when the challenge permits; otherwise HTML scraping of the release lists. Nothing to download, so no rclone or debrid tool applies. |
| Composes with | Use it as the metadata layer: given a release name from a DDL index, xREL gives the group, the date, the NFO and the IMDb/TVDB id, which is what makes a release name resolvable to a title. |
| Reliability | Cloudflare-style bot screening sits in front of the API, so a client that works today can be challenged tomorrow; the HTML surface answered normally. |
| Notes | Included because it is the metadata layer a DDL pipeline needs to turn 'Some.Release.2026.1080p-GRP' into a title, and because it is the clean example's challenge rule: HTML readable, API challenged, recorded as unverified rather than rejected. |
| Evidence rung | documented The home page was read on 2026-10-23 and the API challenge was captured. Getting one API response through a permitted client would settle the real endpoint shape and any rate limit. |
| Checked | 2026-10-24 (live); stale on 2026-11-23 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | www.xrel.to/ | live German scene release database, title 'xREL.v3 - Release & NFO Source #1', release lists with NFO links and sizes |
| 2026-10-23 | api.xrel.to/v2/ | HTTP 403 with a 5-word body: the reader classified it as a bot challenge, so no API content was read |
| 2026-10-23 | api.xrel.to/v2/index.html | HTTP 404 from nginx, so that documentation path does not exist |
More fields (3)
{
"api_status_observed": 403,
"challenge": true,
"has_download_links": false
}