Lastfm (Endpoint)
This Source enables multi-scrobbler to accept scrobbles from outside applications as if it was a Last.fm server.
- To scrobble to Last.fm, create a Last.fm (Client)
- To monitor and re-scrobble activity from your Last.fm account, create a Last.fm (Source)
URL
If a slug is not provided in configuration then multi-scrobbler will accept Last.fm scrobbles at
http://localhost:9078/2.0/
which is the "standard" Last.fm server path for scrobbling
Use a slug only if you need to setup multiple Last.fm Endpoint sources and cannot use different tokens.
If a slug is used then the URL will be:
http://localhost:9078/api/lastfm/mySlug
Configuration
- ENV
- File
- AIO
This is configuration for the ENV Config Type.
| Environmental Variable | Required? | Default | Description |
|---|---|---|---|
LFMENDPOINT_ENABLE | No | Use LFM Endpoint as a Source without any other configuration. Only required if slug/token are not provided as ENVs | |
LFM_SLUG | No | (Optional) The URL suffix to use for accepting LFM scrobbles |
Config Structure
This displays the structure of the File Configuration for a endpointlfm type Source with all possible properties, their shape, and descriptions/types. Use this to understand how to write a valid config.
Config Example
This displays an example config file of a endpointlfm Source 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 endpointlfm Source 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.
[
{
"name": "myLfm",
"enable": true,
"data": {
"slug": "mySlug"
}
}
]
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 endpointlfm type from the respective sources node below, then expand it.
Config Example
This displays an example config file of a all-in-one (config.json) configuration that includes a endpointlfm Source 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 all-in-one (config.json) configuration that includes a endpointlfm Source 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.
{
"sources": [
{
"name": "myLfm",
"enable": true,
"data": {
"slug": "mySlug"
},
"type": "endpointlfm"
}
]
}