/musicbrainz/recordings/search

POST /api/musicbrainz/recordings/search

Price: 1 credit

Search MusicBrainz recordings (tracks)

How to use it

Search MusicBrainz for recordings (individual tracks). Provide a free-text 'query' and/or named filters (recording title, artist, artist MBID, ISRC, release title, duration in ms, video flag, first release date, tag, disambiguation comment). Returns scored matches with title, length, video flag, first release date, ISRCs, artist credits and the releases they appear on.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Free-text Lucene query (examples: "smells like teen spirit")
• recording string nullable — Filter by recording title
• artist string nullable — Filter by artist name (examples: "Nirvana")
• arid string nullable — Filter by artist MBID
• isrc string nullable — Filter by ISRC code
• release string nullable — Filter by the title of a release it appears on
• dur string nullable — Filter by recording length in milliseconds
• video boolean nullable — Filter by whether the recording is a video
• first_release_date string nullable — Filter by first release date (YYYY or YYYY-MM-DD)
• tag string nullable — Filter by folksonomy tag
• comment string nullable — Filter by disambiguation comment
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "MusicBrainzRecordingSearchResult")
• id string required
• url string required
• score integer nullable
• disambiguation string nullable
• length integer nullable
• video boolean (default: false)
• first_release_date string nullable
• isrcs array (default: [])
• artist_credit array (default: [])
  • @type string (default: "MusicBrainzArtistCredit")
  • name string nullable
  • join_phrase string nullable
  • artist object nullable
    • @type string (default: "MusicBrainzArtistRef")
    • id string nullable
    • name string nullable
    • sort_name string nullable
    • disambiguation string nullable
    • type string nullable
• releases array (default: [])
  • @type string (default: "MusicBrainzReleaseStub")
  • id string required
  • url string required
  • status string nullable
  • quality string nullable
  • packaging string nullable
  • date string nullable
  • country string nullable
  • barcode string nullable
  • disambiguation string nullable
  • artist_credit array (default: [])
    • @type string (default: "MusicBrainzArtistCredit")
    • name string nullable
    • join_phrase string nullable
    • artist object nullable (see schema MusicBrainzArtistRef)
  • release_events array (default: [])
    • @type string (default: "MusicBrainzReleaseEvent")
    • date string nullable
    • area object nullable (see schema MusicBrainzAreaRef)
  • label_info array (default: [])
    • @type string (default: "MusicBrainzLabelInfo")
    • catalog_number string nullable
    • label object nullable (see schema MusicBrainzLabelRef)
  • text_representation object nullable
    • @type string (default: "MusicBrainzTextRepresentation")
    • language string nullable
    • script string nullable
  • track_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.