Free for non-commercial use.
Using the AniList API as a backup or data storage service is strictly prohibited.
‘Hoarding’ or mass collection of data from the AniList API is strictly prohibited.
Applications or services must comply with our naming guidelines.
Prohibited from use within competing noncomplementary services of the same nature, including but not limited to Anime/Manga list/tracker services. Competing services may be authorized on request if they provide significant and sustained integration/syncing with the AniList API and AniList user accounts.
Applications or services that utilize the AniList API must adhere to our naming guidelines:
If “AniList” or “AniChart” are used in the title/name of the application you must clearly state your app is an unofficial app by appending either “UNOFFICIAL” or “for AniList”/”for AniChart” to the title/name of the application.
Just the titles/names “AniList” or “AniChart” are strictly prohibited.
Adult content and application stores
Many app stores such as the Apple app store prohibit 18+ content. If you’re planning on providing your client via a third-party service you should check their official stance on the matter.
Where we can, we provide an
isAdult boolean in the media API data, however, we cannot 100% ensure that this will always be accurate or that our definition of ‘adult’ content meets the same standards of other services. Specifically ‘Ecchi’ shows are not included in the ‘adult’ boolean, which is known to have caused issues with Google Adsense and the Apple app store in the past.
We also cannot ensure the data provided by our users will always be non-adult (primarily activity and forum data).
We recommend you do additional checks and limit the data shown on your client to comply with the standards of any services you may be using.
Request API use for commercial clients
If you would like to use the AniList API in a commercial client (this includes ads or in-app purchases), just drop me an email joshstar [a-t] mail [do-t] com or send me a tweet @J0shStar if you would like a quicker reply. With the current usage of the API, it is rather unlikely that any kind of profit cut etc. will be necessary.