⛩️
shinkro
GithubDiscord
  • shinkro Documentation
  • Installation
    • Docker
    • Linux
    • Windows
  • Configuration
    • shinkro config.toml
    • shinkro MAL authentication
    • Reverse Proxy
  • Setup Plex or Tautulli
    • shinkro URL
    • Plex Webhook
    • Tautulli
  • Usage
    • General Usage FAQ
    • Correct Anime Matching
Powered by GitBook
On this page
  • Create a client for accessing the MAL API
  • Authenticate shinkro to update your MAL
  • Security Consideration
  1. Configuration

shinkro MAL authentication

Give your shinkro instance permissions to update your myanimelist

Previousshinkro config.tomlNextReverse Proxy

Last updated 1 year ago

Create a client for accessing the MAL API

Go to to create an ID.

Click on Create ID.

App Information can be entered as follows:

App Name:

<Any that you wish>

App Type:

web

App Description:

Sync watch status between Plex and MAL using the former's webhook and the latter's API. The goal is to not have to manually update how many episodes have been watched etc.

App Redirect URL:

Your publicly accessible with /malauth/callback endpoint instead of /api/plex

https://shinkro.domain.com/malauth/callback

Homepage URL:

https://github.com/varoOP/shinkro

App Logo URL:

https://raw.githubusercontent.com/varoOP/shinkro/main/.github/images/logo.png

Commercial / Non-Commercial:

non-commercial

Name/ Company Name:

<Any that you wish>

Purpose of Use:

hobbyist

Agree to the API License and Developer agreement, if you wish to.

Then, click on Submit.

Return to the list of your API clients, and click on Edit for the one that you just created to get the Client ID and Client Secret.

Authenticate shinkro to update your MAL

Open your shinkro instance in your browser:

https://shinkro.domain.com

Enter the Client ID and Client secret you just created:

Click on Start OAuth, and then Allow your shinkro instance to access your MAL account.

You will be redirected to your shinkro instance if you set the App Redirect URL correctly when creating your MAL API client, and authenticate successfully.

Security Consideration

The client ID, client secret, and access token will be saved in shinkro.db which is located in shinkro's config directory. The default is $HOME/.config/shinkro, or the one you give it when running shinkro with the --config flag.

Since the above sensitive information is saved in shinkro.db, make sure that the shinkro.db file is only accessible to you on your server/device.

MAL API
shinkro URL