Flexible input handling
Resolve the same track from a Spotify share URL, a canonical track ID, or a plain text query.
Overview
Spotify resolution tool, canvas inspection, and operational reference.
Resolve Spotify URLs
Search by track query
Inspect canvas availability
Return structured JSON
Follow with /api/canvas
Check runtime health
Resolve Spotify URLs
Search by track query
Inspect canvas availability
Return structured JSON
The compact workspace for Spotify canvas and track resolution.
Spotycovs is a technical tool designed to resolve Spotify URLs, IDs, and queries into structured metadata and canvas-ready assets.
Canvas-aware output
Track metadata and canvas media are separated clearly so no-canvas responses remain useful instead of looking broken.
Inspection-ready interface
Open the returned Spotify track, inspect raw JSON, copy track IDs, and follow the generated API URLs from the same result surface.
Search-first fallback
When a clean track URL is not available, the interface still documents how query search behaves and how best-match selection is surfaced.
Operational visibility
Health checks, rate-limit state, and missing dependency signals are separated from product copy so trust comes from runtime behavior.
Contract-first docs
Routes, parameters, response fields, and practical failure modes are grouped into a readable developer surface instead of scattered notes.
Next step
Ready to resolve?
Start by resolving a track on the live surface, or jump straight into the technical documentation.
A compact team layer behind the interface.
The people here shape how the tool looks, feels, and works so the workspace stays clear, fast, and trustworthy.
Team
Contributors
lastanswtcf
Core contributor focused on backend API architecture and full-stack website development, ensuring system reliability and high-performance execution.
ilovebee
Key creative force driving the interface concept and website vision, shaping the aesthetic and functional direction of the workspace.
noy
Specialized backend contributor assisting with server-side logic, API optimization, and core infrastructure maintenance.
Contact
Reach the team
Important
Legal & Tool Information
Technical disclaimer regarding the scope and behavior of the Spotycovs utility.
Operational Architecture
Spotycovs functions as a technical bridge for Spotify media inspection.
The tool utilizes an internal, server-side authentication layer (pre-configured service sessions) to resolve track metadata and retrieve canvas media assets.
This architecture ensures that the utility is entirely decoupled from the end-user: it does not request, process, or store any personal credentials, passwords, or login sessions from visitors.
All resolution requests are handled as read-only operations through the service's own secure operational configuration.
Data
Scope of processing
The tool only processes Spotify track identifiers (IDs/URLs) to fetch publicly available metadata and canvas links.
Purpose
Technical utility
The interface is optimized for rapid inspection, ensuring that media asset availability is transparent and deterministic.
Release History
Workspace Updates
Latest changes, version deployments, and system optimizations.
RELEASE LOG
Update V 1.2
Tap to reveal changes
V 1.2
Technical Reconstruction
A complete overhaul of the interface architecture and backend API logic.
- API Optimization: Enhanced resolution speed and reliability across all endpoints.
- Interface Redesign: Transitioned to a professional, monochromatic technical workspace.
- Performance: Reduced asset payload sizes and improved runtime stability.
Resolver
Resolve a Spotify track
Resolve Spotify tracks into metadata and canvas assets.
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.
Primary route
GET /api/resolve
Canvas follow-up
GET /api/canvas
Diagnostics
debug=1 on supported routes
API docs
API Overview
Useful routes for track resolve, canvas lookup, search, metadata, and health checks.
Format
JSON responses
All routes return structured JSON.
Methods
GET endpoints
Use query params to control input.
Debug
debug=1
Available on supported routes for extra details.
GET
/api/resolve
Resolve a Spotify track from a URL, ID, or text query and return normalized resolution metadata together with optional track details.
Params
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.Response
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
GET
/api/canvas
Resolve a track and return canvas availability, canvas asset payloads, and metadata when the Spotify response allows it.
Params
idSpotify track ID.urlSpotify track URL or URI.trackTrack search query.results=1Include additional resolution context.debug=1Include trace and auth diagnostics.Response
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
GET
/api/search
Search by track query and return the best Spotify match together with candidate search results.
Params
trackRequired text query.debug=1Include trace and auth state details.Response
trackIdBest match Spotify track ID.matchedTrackResolved track title.matchedArtistResolved artist.resultsCandidate result list.GET /api/search?track=Artist%20-%20Track%20Name
GET
/api/track
Fetch canonical Spotify metadata directly when the track ID is already known.
Params
idRequired Spotify track ID.Response
trackIdThe normalized Spotify track ID.trackTrack metadata object.GET /api/track?id=3zlJIBfHmFMjvT8TtGf1BWStatus
Runtime health
A simple live view of whether the tool can still resolve tracks and check canvas results reliably.
Loading health data
The dashboard will render after the API responds.