#
Static Data
#
Language Codes & Localization
To denote Chapter Translation language, translated fields such as Titles and Descriptions, the API expects a 2-letter
language code in accordance with the ISO 639-1 standard.
Additionally, some cases require the 5-letter extension if the
alpha-2 code is not sufficient to determine the correct sub-type of a language, in the style of $language-$region,
e.g. zh-hk
or pt-br
.
Because there is no standardized method of denoting romanized translations, we chose to append the -ro
suffix. For
example the romanized version of 五等分の花嫁
is 5Toubun no Hanayome
or Gotoubun no Hanayome
. Both would have
the ja-ro
language code, alternative versions are inserted as alternative titles. This is a clear distinction from the
localized en
translation The Quintessential Quintuplets
Notable exceptions are in the table below, otherwise ask a staff member if unsure.
#
Manga publication demographic
#
Manga status
#
Manga reading status
#
Manga content rating
#
Manga order options
#
Chapter order options
#
CustomList visibility
#
Relationship types
*
Note, that on manga resources you get only one cover_art resource relation marking the primary cover if there are
more than one.
By default this will be the latest volume's cover art. If you like to see all the covers for a given manga, use the
cover search endpoint for your mangaId and select the one you wish to display.
#
Manga links data
In Manga attributes you have the links
field that is a JSON object with some strange keys, here is how to decode this
object:
#
Manga related enum
This data is used in the "related" field of a Manga relationships