Search by Tracks
POST/library-tracks/similarity-search
Get a list of Tracks from your Library that are most similar to the set of reference Tracks specified in the request body.
The endpoint calculates an equal mix of all your input songs, and finds tracks in your catalog similar to that equal mix.
Up to 10 reference tracks may be supplied. When a single reference track is supplied the behaviour is equivalent to the single-track similarity endpoint.
A reference may also be an external source, given as a Spotify track URL or
a YouTube video URL. A request may reference either exactly one external
source or one or more Library Tracks, but not both. Searching by an
external source must be enabled for your account; otherwise the request
is rejected with a 401. See the
Search by External Tracks section of the search guide
for a walkthrough.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
A list of Library Tracks similar to the reference tracks
The request was not successful because it lacks valid authentication credentials for the requested resource. This error indicates that the client has not provided valid authentication details or the provided credentials are invalid.
This object implements RFC 9457 Problem Details for HTTP APIs.
The request associated with this error is refused because the client does not have the necessary permissions to access the requested resource. This could be due to exceeding a quota limit or other authorization issues.
This object implements RFC 9457 Problem Details for HTTP APIs
Response Headers
The maximum quota allowed for the current quota period, indicating the upper limit of resource usage.
The amount of quota still available for use in the current quota period.
The UTC epoch time (in seconds) when the current quota limit resets. If the quota does not reset, this value will be undefined.
One or more reference tracks were not found, or an external source could not be resolved.
The request associated with this error is refused because of an unprocessable request The server understands the content type of the request entity, but was unable to process the contained instructions.
The request associated with this error has exceeded the allowed rate limit for accessing the API. This error indicates that the client has sent too many requests in a given amount of time.
This object implements RFC 9457 Problem Details for HTTP APIs
Response Headers
The maximum number of requests allowed in the current rate limit window.
The number of requests remaining in the current rate limit window.
The UTC epoch time (in seconds) when the current rate limit window
resets. Not present on every 429 response; retry-after always is.
The delay in seconds to wait before retrying the request.