Aniyori for developers

Episode releases and anime premieres

GET /v1/episodes/releases returns source-confirmed releases, newest first. GET /v1/schedules returns scheduled/delayed episodes with known scheduledAt, earliest first. A planned time never confirms release automatically. Both accept from/to ISO 8601 timestamps with explicit offsets, exclusive to, at most 31 days, animeId, format, limit and after. Schedules also accept status=scheduled or delayed.

GET /v1/anime/premieres uses known startDate, newest date first. from/to are yyyy-MM-dd, to exclusive, at most 31 days. Use status=airing for recently premiering anime marked airing, or a future window for announced premieres. A catalog premiere date does not confirm broadcast or regional streaming availability.

Releases/premieres default to the last seven UTC dates plus today; schedules to the next seven days. Responses contain items, page.nextCursor and window. Cursors retain the initial default window and release as-of time; keep filters unchanged. limit is 1–100, default 25. Edits can move entries: deduplicate by canonical ID.

GET /v1/anime/{id}/episodes lists imported episodes by number; GET /v1/episodes/{id} reads a stable canonical episode. Unknown titles/times are null. No placeholders are inferred from anime.episodes. Supplied credentials require anime.read; anonymous reads have a lower quota.

episode.released announces the first imported confirmation; episode.updated covers schedules, delays, cancellations and corrections. Event data is an EpisodeResource with data.anime.id and data.id; compare revisions per episode ID. Historical episodes first imported can emit releases: filter data.releasedAt before notifications. Verify signatures and deduplicate event IDs. Existing anime events are unchanged.

curl "https://api.aniyori.cz/v1/episodes/releases?limit=25" -H "Authorization: Bearer $ANIYORI_API_KEY"

curl "https://api.aniyori.cz/v1/anime/premieres?status=airing" -H "Authorization: Bearer $ANIYORI_API_KEY"
Get started with the API →