Concepts
How the data and the API work, and why.
Where series data comes from, how often it refreshes, and what to do when it is wrong.
The API sits behind a CDN cache, and rate limits are only applied to requests that miss it, so a cached response is free.
A scope is one permission your app asks for and the user approves on the consent screen.
Every error comes back as JSON with the HTTP status repeated in the body. Branch on the status and, where present, the code field. The message is for humans and its wording can change.
The version in the path groups endpoints, but each endpoint declares its own stability. Check the stability of the endpoints you call, not the version number.
Tags form a tree. Filter by a tag id and you get every series tagged with that tag or anything below it. Each tag on a series also has a weight that says how central it is to the story.
Every series has a content rating that measures sexual explicitness and nothing else. The API applies no rating filter unless you ask for one.
The headers the API sets on its responses, what they mean, and which ones are worth reading in a client.
What the MangaBaka OAuth provider supports, how long its tokens live, and the behaviour most likely to trip up a client.
What you may do with MangaBaka data, from the API or the dumps, and how to credit it.