Import vs upload
Import then upload — that’s the recommended path. Import gets the
metadata in fast so Patchline knows your full catalog exists. Upload
the audio for the tracks you want to act on — that’s what unlocks
the rest of the product.
If you only want intelligence and don’t plan to sell or AI-caption,
import alone is fine.
How to import
Option A — Paste a URL into Aria
Easiest path. Aria’sanalyze_url
tool resolves any supported streaming URL to its canonical identity and
either imports it or asks for confirmation.
Option B — Use the Catalog UI
Sidebar → Catalog → Import button (top right) → paste the URL into the dialog → click Import. The track’s metadata appears in the catalog list within a few seconds. To unlock AI captioning, smart links, and the Music Store for that track, upload the audio next.Option C — MCP tool call (for AI agents)
What gets imported
Import pulls only the metadata the streaming platform makes public:
What import does not give you:
- The audio file
- AI captions
- Music Store listings, smart links, asset shares for the track
Supported URL types
Artist URLs add the artist to your roster and
trigger an artist-intelligence refresh — they don’t import all of the
artist’s catalog automatically.
Deduplication
Patchline deduplicates by ISRC first, then by its internal catalog identity. If you import the same track twice — once via Spotify URL, once via Apple URL — Patchline merges them into a single catalog entry and updates the metadata with whatever was missing. If you’ve already uploaded a track via file and then import the same track via streaming URL, Patchline keeps the master audio (from the upload) and augments it with the streaming-platform identifiers.Examples
Import a single
Import an album
Import all of an artist’s catalog (advanced)
How it works
- Aria’s
analyze_urltool inspects the URL pattern and resolves it against the right platform API (Spotify Web API foropen.spotify.com, Apple Music API formusic.apple.com, etc.). - Track metadata is fetched, normalized to Patchline’s schema, and saved to your workspace catalog.
- Patchline updates the user-scoped search view used by catalog search. Deduplication runs before the track appears in your catalog.
- The track appears in your catalog as a metadata-only row. The AI-readable caption and Music Store listing are not generated on import — they run only when you upload the audio.
Related features
- Upload a track (file) — when you want the master in Patchline
- AI-discoverable tracks — what runs after you upload the audio
- Catalog search — semantic search across imported tracks
- Artist roster — add artists by URL, separate flow
FAQ
Does importing a track actually move my audio?
Does importing a track actually move my audio?
No. Import references the streaming version. Your master stays
wherever you originally distributed it. If you want
Patchline to hold your master, upload it instead.
What if the same track is on Spotify with one ISRC and on Apple with a different one?
What if the same track is on Spotify with one ISRC and on Apple with a different one?
Most labels distribute the same ISRC to both. If they don’t (rare),
Patchline treats them as separate catalog entries until you manually
merge them in the UI.
Can I bulk-import a CSV of URLs?
Can I bulk-import a CSV of URLs?
Not from the dashboard UI today. From Aria: paste a list and ask
“import these all.” For Enterprise customers with thousands of URLs,
the REST API supports batch import — contact support.
What happens if the streaming URL goes 404?
What happens if the streaming URL goes 404?
The catalog entry stays. Patchline marks the source as unavailable
and keeps the metadata already imported.
Can I undo an import?
Can I undo an import?
Yes. Catalog list → track row → ⋯ → Delete. Lifetime import usage
does not reset after deletion.
Does import work for unreleased tracks?
Does import work for unreleased tracks?
Only if the unreleased track has an unlisted streaming URL (very
uncommon). For unreleased work, upload the file
instead — that’s the canonical path.