Flexible input handling
Resolve the same track from a Spotify share URL, a canonical track ID, or a plain text query.
Spotify resolution tool, canvas inspection, and operational reference.
Spotycovs is a technical tool designed to resolve Spotify URLs, IDs, and queries into structured metadata and canvas-ready assets.
Resolve the same track from a Spotify share URL, a canonical track ID, or a plain text query.
Track metadata and canvas media are separated clearly so no-canvas responses remain useful instead of looking broken.
Open the returned Spotify track, inspect raw JSON, copy track IDs, and follow the generated API URLs from the same result surface.
Search matching is score-filtered to avoid weak or stale-like results and returns only confident candidates for the current query.
Health checks, rate-limit state, and missing dependency signals are separated from product copy so trust comes from runtime behavior.
Routes, parameters, response fields, and practical failure modes are grouped into a readable developer surface instead of scattered notes.
Next step
Start by resolving a track on the live surface, or jump straight into the technical documentation.
The people here shape how the tool looks, feels, and works so the workspace stays clear, fast, and trustworthy.
History
Spotycovs started as a small tool created out of boredom, used initially only on our own websites. Over time, we kept improving the resolver flow, response quality, and overall interface.
After it became stable and genuinely useful in day-to-day usage, we decided to make it public and shape it into the form you see now.
Team
Core contributor focused on backend API architecture and full-stack website development, ensuring system reliability and high-performance execution.
Key creative force driving the interface concept and website vision, shaping the aesthetic and functional direction of the workspace.
Specialized backend contributor assisting with server-side logic, API optimization, and core infrastructure maintenance.
Support
Support our work if you find Spotycovs useful. Every contribution helps us keep improving the tool.
LYr5ypcGNUfXYF5As7JapdciKNxEHm4r1t
Spotycovs functions as a technical bridge for Spotify media inspection. The platform is designed for read-only resolution workflows and metadata analysis, with a strict boundary between runtime infrastructure and user credentials.
The utility uses an internal server-side authentication layer (pre-configured service sessions) to resolve track metadata and retrieve canvas media assets. All requests are processed as technical lookup operations.
Spotycovs does not request, store, or process personal Spotify passwords, login tokens, or account credentials from visitors. Runtime operations remain isolated in backend service context.
The tool processes Spotify identifiers such as track URLs, IDs, and textual queries to produce structured API output for inspection, debugging, and metadata/canvas verification.
No passwords and no personal login sessions from visitors.
Resolution and media checks run in backend service context.
Built for deterministic inspection and verification workflows.
Only track URLs, IDs, and text queries are processed for output.
Latest platform changes, release notes, and backend behavior upgrades for resolver quality and API consistency.
RELEASE LOG
Tap to reveal changes
Accuracy upgrades for resolver output plus major API surface expansion for lyrics and artist flows.
/api/lyrics and /api/artist with detailed payloads.Resolve Spotify inputs into deterministic metadata, canvas payloads, and follow-up API routes for inspection workflows.
Use a public Spotify track URL when you already have the shared link.
Useful when testing the search resolver or when only the song title is known.
Best option for deterministic lookups when the canonical Spotify ID is available.
Provide at least one of track query, track ID, or track URL to fetch lyrics.
Use query, ID, or URL. Limit controls related payload size.
Contract-first reference for Spotycovs routes: request parameters, response fields, and practical runtime behavior.
API docs
Use this as a contract-first reference for request parameters, response fields, and production-safe usage patterns.
All routes return structured JSON.
All resolver routes use query parameters and return JSON.
debug=1
Available on supported routes for extra details.
error + code
Failures return explicit error messages and stable machine-friendly codes.
Getting Started
Fastest way to integrate: call one route, inspect request.apiUrl, then chain into adjacent routes.
Base URL/api/* on the same domain as your deployment.Typical chain/api/resolve → /api/canvas for deterministic media checks.Debug modeAdd debug=1 where supported for additional trace context.GET /api/resolve?url=https://open.spotify.com/track/...Resolve URL into canonical track identity.GET /api/canvas?id=3zlJIBfHmFMjvT8TtGf1BWRequest canvas/media payload for a known ID.GET /api/lyrics?track=Summertime%20Sadness&artist=Lana%20Del%20ReyFetch lyrics using text-first resolution.Reference
Shared response and error rules that apply across endpoints.
successBoolean success signal for machine checks.sourceUpstream resolver/source used for this payload.request.apiUrlCanonical route form you can reuse directly.success: falseReturned on all handled endpoint failures.errorHuman-readable explanation for UI rendering.codeStable machine-friendly token (e.g. spotify_rate_limited)./api/resolve
Resolve URL/ID/query inputs into a stable track identity before calling metadata-heavy routes.
idSpotify track ID.urlSpotify track URL or URI.trackText query used for search resolution.results=1Include candidate matches when search is involved.debug=1Include auth and resolver debug information.trackIdThe resolved Spotify track ID.trackTrack metadata object when available.resolutionResolver details such as source and strategy.requestPrebuilt follow-up API URLs.GET /api/resolve?url=https://open.spotify.com/track/3zlJIBfHmFMjvT8TtGf1BW
/api/canvas
Fetch canvas availability and media payloads for a resolved track identity.
idSpotify track ID.urlSpotify track URL or URI.trackTrack search query.results=1Include additional resolution context.debug=1Include trace and auth diagnostics.hasCanvasWhether Spotify returned canvas media.canvasesCanvas payload list.trackResolved track metadata when available.request.apiUrlCanonical API URL for the request.GET /api/canvas?id=3zlJIBfHmFMjvT8TtGf1BW
/api/search
Run search-first matching and return confident candidates plus the best track match.
trackRequired text query.debug=1Include trace and auth state details.trackIdBest match Spotify track ID.matchedTrackResolved track title.matchedArtistResolved artist.resultsCandidate result list.GET /api/search?track=Artist%20-%20Track%20Name
/api/track
Fetch canonical track metadata directly when you already know the Spotify track ID.
idRequired Spotify track ID.trackIdThe normalized Spotify track ID.trackTrack metadata object.GET /api/track?id=3zlJIBfHmFMjvT8TtGf1BW
/api/lyrics
Return lyrics lines and optional Spotify color-lyrics payload when auth context allows it.
idSpotify track ID.urlSpotify track URL or URI.trackTrack name query.artistOptional artist name for better resolution.trackIdResolved Spotify track ID.lyrics.linesLyrics lines array.colorLyricsSpotify color lyrics payload when available.resolutionTrack resolution details.GET /api/lyrics?track=Summertime%20Sadness&artist=Lana%20Del%20Rey
/api/artist
Return normalized artist profile + related top tracks, albums, and artists.
idSpotify artist ID.urlSpotify artist URL or URI.queryArtist text query.limitRelated surface size (max 25).raw=1Include raw upstream artist payload for deep debugging.artistIdResolved artist ID.summaryNormalized profile, stats, genres, and curated lists.related.topTracksTop tracks normalized for UI/API consumers.related.albumsPopular releases/albums normalized for display.related.artistsRelated artists list with normalized identity fields.GET /api/artist?query=The%20Weeknd
Live operational status for Spotify connectivity, canvas auth checks, and recent API request activity.
The dashboard will render after the API responds.