Playlist editor API

The playlist editor's own API, called with an editor API token: for scripts that only need your edited playlists.

The playlist editor has its own small API under /editor/api/v1/. It reaches only the playlists you allow, and it uses editor API tokens, not the API keys of the rest of the API.

Editor API token API key
Reaches The playlists you choose, their content, customers, updaters and backups Everything the account can do
Made in Playlist editor → API tokens API keys
Starts with mnm_ —
Paths /editor/api/v1/… only Every path in the API reference

Use an editor token for a script that only syncs or tidies your edited playlists. Use an API key for anything else.

Make a token

In the dashboard, open Playlist editor → API tokens and choose New token:

  • Name: what it is for.
  • Playlists: All playlists (including ones made later), or Only some.
  • Expires after: 30, 90, 180 or 365 days.
  • Only from these addresses (optional): the addresses or networks it may be used from, up to 50.
  • Token password (optional): a second secret the token must be sent with.

Confirm with your account password. The token is shown once; the page also shows the API address to call. An account can hold 10 tokens.

Use it

curl 'https://panel.example.com/editor/api/v1/playlists/' \
  -H "Authorization: Bearer $EDITOR_TOKEN"
  • X-API-Key: mnm_… works too, instead of Authorization.
  • A token with a password also needs X-Token-Password: <password>.

Limits

  • 120 requests a minute per token. Past that: 429 with Retry-After.
  • 10 wrong tokens from one address within 5 minutes: that address is refused for 5 minutes.
  • Lists of channels, films and shows come up to 500 at a time: send after with the last id you received to get the next ones.

Calls

Every call is in the API reference under Playlist editor API.