starred/SpotAPI
1
0
Fork 0
mirror of https://github.com/Aran404/SpotAPI.git synced 2026-04-25 16:55:50 +03:00
Code Issues 3 Projects Releases Packages Wiki Activity

[GH-ISSUE #60] Issue with User.get_plan_info: 404 /ca-en/api/zine/v2/plan/ not Found #36

New issue
Open
opened 2026-02-27 19:06:33 +03:00 by kerem · 1 comment
kerem commented 2026-02-27 19:06:33 +03:00
Owner
Copy link

Originally created by @simonebartolibp on GitHub (Feb 11, 2026).
Original GitHub issue: https://github.com/Aran404/SpotAPI/issues/60

Hey!

Since yesterday (10 Feb 2026), fetching the user plan info has been consistently failing with a 404.

The hardcoded endpoint
https://www.spotify.com/ca-en/api/account/v2/plan/
still exists and requires auth, but now always responds with:

{
  "timestamp": "<current_timestamp>",
  "status": 404,
  "error": "Not Found",
  "path": "/ca-en/api/zine/v2/plan/"
}

So it looks like the backend route may have changed or been removed.

I’m not sure if there’s another simple REST endpoint for this, but if not, it might be worth switching to the same GraphQL call the web player uses. For reference, this is the curl request:

curl 'https://api-partner.spotify.com/pathfinder/v2/query' \
  -H 'accept: application/json' \
  -H 'app-platform: WebPlayer' \
  -H 'authorization: Bearer <BaseClient.access_token>' \
  -H 'client-token: <BaseClient.client_token>' \
  -H 'content-type: application/json;charset=UTF-8' \
  -H 'spotify-app-version: 1.2.84.154.g23b98c02' \
  -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36' \
  --data-raw '{"variables":{},"operationName":"accountAttributes","extensions":{"persistedQuery":{"version":1,"sha256Hash":"<BaseClient..part_hash(\"accountAttributes\")>"}}}'

And the response includes the plan details inside account attributes, for example:

{
  "data": {
    "me": {
      "account": {
        "attributes": {
          "catalogue": "premium",
          "onDemand": true,
          "ads": false
        },
        "country": "GB",
        "product": "PREMIUM"
      }
    }
  }
}

Happy to open a PR to switch over to this approach if that sounds good.

Originally created by @simonebartolibp on GitHub (Feb 11, 2026). Original GitHub issue: https://github.com/Aran404/SpotAPI/issues/60 Hey! Since yesterday (10 Feb 2026), fetching the user plan info has been consistently failing with a **404**. The hardcoded endpoint `https://www.spotify.com/ca-en/api/account/v2/plan/` still exists and requires auth, but now always responds with: ```json { "timestamp": "<current_timestamp>", "status": 404, "error": "Not Found", "path": "/ca-en/api/zine/v2/plan/" } ``` So it looks like the backend route may have changed or been removed. I’m not sure if there’s another simple REST endpoint for this, but if not, it might be worth switching to the same GraphQL call the web player uses. For reference, this is the curl request: ```bash curl 'https://api-partner.spotify.com/pathfinder/v2/query' \ -H 'accept: application/json' \ -H 'app-platform: WebPlayer' \ -H 'authorization: Bearer <BaseClient.access_token>' \ -H 'client-token: <BaseClient.client_token>' \ -H 'content-type: application/json;charset=UTF-8' \ -H 'spotify-app-version: 1.2.84.154.g23b98c02' \ -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36' \ --data-raw '{"variables":{},"operationName":"accountAttributes","extensions":{"persistedQuery":{"version":1,"sha256Hash":"<BaseClient..part_hash(\"accountAttributes\")>"}}}' ``` And the response includes the plan details inside account attributes, for example: ```json { "data": { "me": { "account": { "attributes": { "catalogue": "premium", "onDemand": true, "ads": false }, "country": "GB", "product": "PREMIUM" } } } } ``` Happy to open a PR to switch over to this approach if that sounds good.
kerem commented 2026-02-27 19:06:34 +03:00
Author
Owner
Copy link

@Aran404 commented on GitHub (Feb 14, 2026):

I'm going to recode spotapi soon, it's almost completely outdated

<!-- gh-comment-id:3900428562 --> @Aran404 commented on GitHub (Feb 14, 2026): I'm going to recode spotapi soon, it's almost completely outdated
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/SpotAPI#36
No description provided.