Anume Player reseller portal, branding and API

Request an account; the administrator approves it

Complete the reseller form with a username, contact email, password and brand name. Submitting does not activate access automatically. The administrator reviews and approves the account before the portal or API can be used.

The account is separate from the public form for a personal playlist. Use reseller access to manage customers, assign playlists correctly and view your account activity.

In-app branding, not a new APK

After approval, set the brand name, logo and accent colour. The app receives the identity for the playlist assigned to your account when it syncs. Your logo can also be used where the source supplies no icon.

The launcher app name and icon remain Anume Player. This customises the same app; it does not publish a separate store application. Playlists must be assigned correctly to the reseller to receive the right branding.

Generate and control your API key

Generate a key from your approved account. The key is shown once and must be stored privately on your server. Rotate or revoke it in the portal. Do not place it in public JavaScript, a public QR code or a URL.

Requests use HTTPS and Bearer authentication. Use the portal documentation for exact routes, fields and responses. Populate examples with test data, not customer URLs or passwords.

MAC playlists and account activity in one place

View your account playlists and events, and add, select or delete your own playlists by MAC. The device receives configuration when it syncs. The API is not a video traffic proxy and does not provide content.

The administrator handles assigning a customer to another reseller. Do not create duplicate playlists as a transfer method. Check operation results in the activity log and test on a dedicated device before bulk changes.

Frequently asked questions