Command Palette
Search for a command to run

HTTP API

About the API

Data Format

All API endpoints return data in JSON format.

The entire database is updated weekly from the supported metadata providers listed below.

The refresh frequency for individual series depends on how often it's updated on the underlying sites with a minimum of 1 day and a maximum of 7 days between updates.

Supported Metadata Providers

  • AniList icon AniList
  • Anime-Planet icon Anime-Planet
  • Kitsu icon Kitsu
  • MangaUpdates icon MangaUpdates
  • MyAnimeList icon MyAnimeList
  • Shikimori icon Shikimori
Bugs and Data Issues

Metadata Issues

Missing or incorrect metadata from underlying data providers should be reported and fixed on their respective sites. Once the issue is resolved, we can update our database to reflect the changes.

You can know more on our Discord server (#data).

Duplicate Titles

If you find a duplicate series, please report it on our Discord server (#data).

Missing links to other sites

If you find a series that is missing links to other sites, please report it on our Discord server (#data).

Data Schema and Structure

No version 1.0 stability yet

The schema is subject to change at any time and without notice.

If changes do happen, they are likely to be additive and not breaking.

Metadata Site Response Fields

Fields with the suffix _response are the raw responses from the upstream APIs, and will only change if the upstream API changes.

Rights and Attribution

Acceptable Usage Policy and Terms of Service

Please make sure to follow the metadata providers' Acceptable Usage Policy (AUP) and Terms of Service (TOS) when using the API.

Data Attribution

When using the API, please make sure to attribute both MangaBaka and the underlying data providers.

Attribution could be done in the following ways:

  • A link in the footer of your site or application
  • A link in your project's README file
  • A link in the 'About' page of your site or application
  • A link to a specific series next to your own data for that series
Rate Limits and Caching

Rate Limiting is only applied to uncached requests, so requesting GET /v1/series/1 10 times will only count as 1 request.

This is true for all endpoints, including the search endpoint.

You can search if your request was cached by checking the cf-cache-status: HIT header in the response.

Exceeding the rate limit will result in a 429 Too Many Requests response.

Kind Path Cache Duration Limit Limited by
Search GET /v1/series/search 2 hours 60 requests per minute IP + Leaky Bucket
Lookup GET /* 12 hours 120 requests per minute IP + Leaky Bucket
Lookup GET /v1/news
GET /v1/series/*/news
2 hours 120 requests per minute IP + Leaky Bucket

Note

Rate limits with the same kind are shared across all endpoints with that kind. For example, the lookup kind is shared between the GET /v1/series/1 and GET /v1/series/2 endpoints.

HTTP API Documentation

The API is available at https://api.mangabaka.dev/

Go to the API Explorer UI to explore the MangaBaka API built with OpenAPI 3.1