Last.fm

Other Users

To monitor and re-scrobble activity from your Last.fm/Libre.fm account create a Last.fm (Source)
To accept scrobbles from outside applications as if multi-scrobbler was Last.fm, create a Last.fm (Endpoint)

You will need a Last.fm account to use the Last.fm API.

After creating your account, register for an API account here.

The callback URL in the API account form is not used, but to keep it consistent use the same value you set using the Callback/Redirect URL section.

Take note of your API Key and Secret after account creation.

Callback/Redirect URL

The Redirect (Callback) URL is used to redirect your browser to multi-scrobbler after authentication has completed.

So, the base of the URL you use should be the same as the URL you would use to navigate to the multi-scrobbler dashboard.

Example

If you can visit the multi-scrobbler dashboard by navigating to http://192.168.0.100:9078 in your web browser...

then the ENV LASTFM_REDIRECT_URI, or redirectUri for last.fm/libre.fm json config, should be

http://192.168.0.100:9078/lastfm/callback

The Redirect URL can be explicitly specified in the configuration below, or by using the global Base URL setting.

Configuration

ENV
File
AIO

Configuration Type

This is configuration for the ENV Config Type.

Environmental Variable	Required?	Default	Description
`LASTFM_API_KEY`	Yes		Api Key from your API Account
`LASTFM_SECRET`	Yes		Shared secret from your API Account
`LASTFM_REDIRECT_URI`	No	`http://localhost:9078/lastfm/callback`	Url to use for authentication. Must include `lastfm/callback` somewhere in it
`LASTFM_SESSION`	No		Session id. Will be generated by authentication flow if not provided.

Config Structure

This displays the structure of the File Configuration for a lastfm type Client with all possible properties, their shape, and descriptions/types. Use this to understand how to write a valid config.

Loading ...

Config Example

This displays an example config file of a lastfm Client File Configuration that adheres to the shown Config Structure.

text mode lets you edit the JSON directly.
tree mode gives you a guided point-and-click editing experience that always keeps the JSON syntax valid.

Both modes validate that the configuraion is correct. Any errors show up as squiggly lines.

After you finish editing, switch to text and then copy all text to get a completed config.

Config Example Mobile Experience

This displays an example config file of a lastfm Client File Configuration that adheres to the shown Config Structure.

The example config file editor is meant for a larger screen experience so only the read-only example is shown. Please use this site on a tablet/laptop/desktop to enable file editor features.

CONFIG/lastfm.json
[
  {
    "name": "myLastFmClient",
    "enable": true,
    "configureAs": "client",
    "data": {
      "apiKey": "a89cba1569901a0671d5a9875fed4be1",
      "secret": "ec42e09d5ae0ee0f0816ca151008412a",
      "redirectUri": "http://localhost:9078/lastfm/callback"
    }
  }
]

Config Structure

This displays the structure of the all-in-one (config.json) configuration with all possible properties, their shape, and descriptions/types. Use this to understand how to write a valid config.

Select the lastfm type from the respective clients node below, then expand it.

Loading ...

Config Example

This displays an example config file of a all-in-one (config.json) configuration that includes a lastfm Client that adheres to the shown Config Structure.

text mode lets you edit the JSON directly.
tree mode gives you a guided point-and-click editing experience that always keeps the JSON syntax valid.