anidb.net APIanidb.net ↗
Access AniDB anime metadata, episode details, character data, and seasonal charts via 7 REST endpoints. Search titles, filter by season, type, and year.
curl -X GET 'https://api.parse.bot/scraper/85433efe-2087-4e5a-bff1-1c78cbd5820a/search_anime?query=One+Piece' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for anime by title or keyword. Returns up to 30 results ranked by relevance score. If the query matches a single anime exactly, the site may redirect and return a single-item result.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword or anime title (e.g. 'Naruto', 'Dragon Ball'). |
{
"type": "object",
"fields": {
"items": "array of anime search results, each with id, title, and score",
"total": "integer count of items returned"
},
"sample": {
"data": {
"items": [
{
"id": "239",
"score": "7.668",
"title": "Naruto"
},
{
"id": "4880",
"score": "6.858",
"title": "Naruto Shippuuden"
}
],
"total": 2
},
"status": "success"
}
}About the anidb.net API
The AniDB API exposes 7 endpoints covering anime search, full series metadata, character lookups, episode details, and seasonal charts drawn from AniDB's community-maintained database. The get_anime_details endpoint alone returns episode lists with air dates and durations, tags, descriptions, and ratings for any series by numeric ID. Whether you need to search by keyword or filter by year, season, and airing status, the API gives structured JSON back for every request.
Anime Search and Metadata
The search_anime endpoint accepts a query string and returns up to 30 results, each with an id, title, and relevance score. When the query matches a single title exactly, the result may be a single-item array. To fetch full metadata, pass that id to get_anime_details, which returns the title, description, a tags array, and a complete episodes array — each episode object includes id, number, title, duration, and airdate. For multi-filter queries, advanced_search_anime accepts a query alongside year, season, types (comma-separated type names like tvseries), and an airing_status integer, returning up to 25 ranked results.
Characters and Episodes
search_character accepts a query and returns up to 30 matching characters with id, name, and gender. Passing a character id to get_character_details retrieves name, description, and a related_anime array where each entry includes the anime's id, title, and the character's role in that series. Individual episodes can be fetched directly with get_episode_details using a numeric episode id, returning title, description, air_date, and play_length fields without needing to go through the parent anime.
Seasonal Charts
The get_season_chart endpoint accepts an optional year integer and a season string (winter, spring, summer, or autumn). The response is an items array where each entry includes id, title, date, type_info, rating, and average. This makes it straightforward to build season-browsing features or compare ratings across a single cour. If neither parameter is provided, the endpoint returns data for the current or most recently populated season.
- Build an anime recommendation engine using tags and ratings from
get_anime_details. - Populate a seasonal airing calendar using
get_season_chartwith year and season filters. - Generate character profile pages using
name,description, andrelated_animefromget_character_details. - Track episode air dates and durations for a watchlist app using the
episodesarray inget_anime_details. - Filter anime by type and airing status for a discovery tool using
advanced_search_anime. - Cross-reference a character's appearances across multiple series using the
related_animefield. - Fetch standalone episode synopses for a trivia or quiz application via
get_episode_details.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does AniDB have an official developer API?+
What does `get_anime_details` return, and how does the episode data look?+
id, title, description, tags (an array of tag name strings), and episodes. Each object in the episodes array includes id, number, title, duration, and airdate. Tags may be an empty array if the anime has none recorded on AniDB.Does `search_anime` support pagination or return more than 30 results?+
search_anime returns up to 30 results per call and does not expose a pagination parameter. The total field reflects the count of items actually returned in that response, not the full database count. You can fork the API on Parse and revise it to add offset or page-based pagination if your use case requires deeper result sets.Is staff, voice actor, or studio data available through this API?+
How does the `airing_status` filter in `advanced_search_anime` work?+
airing_status parameter accepts a numeric code; for example, 2 corresponds to finished airing. The accepted integer values map to AniDB's internal status taxonomy, so you should test values against known series to confirm which codes are active. The endpoint returns up to 25 results regardless of how many filters are applied.