Search API ignoring market parameter

Anemo — Mon, 15 Sep 2025 17:53:00 GMT

Hello,

I recently noticed that the search API endpoint is not taking the passed market parameter into account when making a query.

For example, I have the following ISRC "JPF702500331" which has two different links, one for Japan, and one for the rest of the world:

- Japan link: https://open.spotify.com/track/3C0YQ1zvSJ2dN3OlhDH7zF

- Rest of the world link: https://open.spotify.com/track/4CQavbYj3kUJBJaWKDGKgK

However, when using the search endpoint with query "isrc:JPF702500331" and market "JP", it's always the second link that is returned.

On the web API page, it is specified the following for the market param.

If a valid user access token is specified in the request header, the country associated with the user account will take priority over this parameter. Note: If neither market or user country are provided, the content is considered unavailable for the client.

While I understand this behaviour for the authorization flow where we explicitly provide an access token, I don't think it should also apply to the client credentials flow. Else what would be the point of having a "market" parameter if it's always taking the one from the base account?

Re: Search API ignoring market parameter

ATLAST — Fri, 19 Sep 2025 13:27:32 GMT

I can second this. When using the client_credentials flow (no user logged in specifically), it will not honour the market parameter. This has been the case for about 2 weeks now.

For example when looking at availability for songs in certain markets, it won't use the market parameter at all in my testing. I see this across the board. Anywhere where the market parameter is an option to use.

topic Search API ignoring market parameter in Spotify for Developers

Search API ignoring market parameter

Re: Search API ignoring market parameter