Lidarr

Aurral requires Lidarr. Aurral adds artists and albums, reads library state, and shows queue and history status through Lidarr.

The Lidarr integration has two parts:

1. Aurral connects to the Lidarr API.
2. Aurral reads the library files at the paths that Lidarr reports.

The API connection can pass while the file connection fails. Mount the same media root in Aurral and Lidarr at the same container path. See Filesystem and mounts.

Connection

Enter these values in first-run setup or in Settings > Lidarr:

• The URL Aurral can reach (often http://lidarr:8686 in Docker). When an API key is configured, use HTTPS. For a trusted local HTTP connection, set LIDARR_ALLOW_HTTP=true in the Aurral environment.
• Your Lidarr API key
• Default quality profile, metadata profile, tag, monitoring option, and search-on-add behavior
• Optional Davo’s Community Lidarr Guide for quality profiles and file names

Metadata providers

Aurral keeps the MusicBrainz UUID for artist routes and stores Lidarr’s provider ID separately. If Lidarr uses a provider such as Tubifarry Deezer or Discogs, Aurral verifies the submitted MusicBrainz artist, uses Lidarr’s lookup to identify the active provider, and retries a provider-ID format error with the canonical provider ID. Existing provider-ID artists are verified and backfilled when Aurral reads the library. If the identities do not match, search for the artist in Lidarr first or use MusicBrainz metadata.

Library access check

Aurral tests file access at paths that Lidarr reports. If the test fails, mount the Lidarr media root in Aurral. The recommended layout uses /data in both containers, with a Lidarr root folder such as /data/music.

The check samples a track from an artist inside a root folder. It falls back to an artist outside them and then reports that the artist was left behind by a root folder change.

See Library access fails on a folder that is not your root folder.

In mixed Windows and Docker setups, Test library access shows the exact path that Lidarr reports. If that path differs from the path inside Aurral, add a mapping under Settings > Download Clients > Remote Path Mappings with Source set to Lidarr.

This mapping only helps Aurral read Lidarr files. It does not change paths in Navidrome .m3u files. Configure Navidrome paths under Settings > Playback > Navidrome. See Path mismatches.

Safety

Artist and album changes go through Lidarr. Aurral does not write directly into your root music library.

Import list feeds

Each flow can provide a Lidarr Custom List URL.

1. Open the flow menu on Playlists.
2. Select Lidarr import URL.
3. In Lidarr, open Settings > Import Lists > Custom List.
4. Add the URL.

The copied URL uses the Aurral host in your browser. For example, the URL can start with https://aurral.example.com/api/feeds/.

Lidarr must be able to reach that host.

The URL includes a per-flow token. Treat it like a secret. Anyone with the URL can read that flow’s artist list.

The feed always reflects the flow’s current tracklist.

Aurral does not include tracks without a MusicBrainz artist ID in the feed. Aurral includes available album IDs.

Lidarr uses the IDs for Specific Album monitoring on versions that support album-level custom lists.