MusixMatch changed their signature generation

[Lioncat6]

Not sure how yet, but the current method is broken.

[Strvm]

I think they've put their platform behind an auth login now

It asks me to log in when I try to search now on: https://www.musixmatch.com/search

[Lioncat6]

This can easily be circumvented using a session cookie with the requests... they last about a couple weeks from my experience.

[Lioncat6]

But they did change their signature generation logic as both your implementation and mine in js now returns the invalid signature error

[Strvm]

With this auth barrier you no longer require a signature, since the user token is the signature now.

Was able to get it working with something like this (redacted my auth token)

import requests

url = "https://apic-appmobile.musixmatch.com/ws/1.1/community/opensearch/tracks?app_id=mac-ios-v2.0&usertoken=REDACTED&query=Daft"

payload = {}
headers = {
  'Host': 'apic-appmobile.musixmatch.com',
  'Accept': 'application/json',
  'x-mxm-app-version': '1.37.2',
  'User-Agent': 'Musixmatch/2025120901 CFNetwork/3860.300.31 Darwin/25.2.0',
  'Accept-Language': 'en-US,en;q=0.9',
  'Connection': 'keep-alive',
}

response = requests.request("GET", url, headers=headers, data=payload)

print(response.text)

[romankouz]

Hi yall!

Love the project! It's been super neat to use for my multi-modal music critic prediction project!

I have been trying to populate a database with lyrics from a bunch of album reviews and after about 20 successful processes or so, I keep receiving a 401 Error Code.

I'm relatively new here so I was curious if that behavior is in line with the issue raised. If not, I'll do some more investigation on my own, thanks!

[Lioncat6]

Mxm has recently stepped up their api endpoint protection, so you're a lot more likely to hit a captcha or a 401.

Side note: this issue no longer applies since it was a temporary change that has been reverted.

[romankouz]

Understood, thank you so much!