Rocksky implements the Last.fm Audioscrobbler API (both the modern 2.0 protocol and the legacy submission protocol). Migrating an existing client usually means changing one URL and swapping credentials.Documentation Index
Fetch the complete documentation index at: https://docs.rocksky.app/llms.txt
Use this file to discover all available pages before exploring further.
Get your credentials
- Sign in to rocksky.app.
- Go to your API Applications.
- Create an application to get an API key and shared secret.
- Generate a session key with
rocksky login.
Modern Last.fm clients (API 2.0)
Replace the base URL:| Last.fm | Rocksky |
|---|---|
https://ws.audioscrobbler.com/2.0 | https://audioscrobbler.rocksky.app/2.0 |
api_key and sk (session key) parameters with
MD5-signed requests:
- Sort all request parameters by key alphabetically.
- Concatenate
key + valuepairs into one string. - Append your shared secret.
- MD5-hash the result; send it as
api_sig.
Legacy submission protocol
For older clients (e.g. Deadbeef), use the legacy endpoint:- Username: your API key
- Password: your shared secret
Metadata normalization
Rocksky normalizes incoming track metadata before storing it. If the track can’t be matched against a known song, the scrobble is skipped rather than stored as an orphan record.Why migrate?
- Your scrobbles live on infrastructure you can self-host
- Real-time Stories feed for what your network is playing
- AT Protocol identity — portable, exportable, no lock-in
- Compatible with existing tools you already trust