starred/spotify-web-api-php

Fork 0

mirror of https://github.com/jwilsson/spotify-web-api-php.git synced 2026-04-26 23:45:49 +03:00

[GH-ISSUE #286] getMyEpisodes() – offset parameter appears to be ignored (possible upstream Spotify API regression) #211

New issue

Closed

opened 2026-02-27 19:26:37 +03:00 by kerem · 7 comments

kerem commented

2026-02-27 19:26:37 +03:00

Owner

Originally created by @paha77 on GitHub (Feb 15, 2026).
Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/286

Hi,

since a few days ago, the getMyEpisodes() method seems to ignore the offset parameter.

Context

We are paginating through a user’s saved episodes using getMyEpisodes() with explicit limit and offset parameters, e.g.:

$episodes = $api->getMyEpisodes([
    'limit' => 50,
    'offset' => 50,
]);

Previously, this returned the expected “next page” of results. However, as of recently, the response appears to always return the first page, regardless of the offset value provided.

Observed Behavior

offset is set explicitly (e.g. 50, 100, etc.)
Response still contains items starting from index 0
The returned payload structure itself looks valid
No error is thrown
Behavior is reproducible and consistent

Assumptions

From initial inspection, this looks like a potential upstream issue with the Spotify Web API rather than a client-side bug in this library. The request parameters appear to be constructed correctly.

Questions

Has anyone else observed similar behavior with getMyEpisodes() (or other paginated endpoints)?
Is there any known recent change in the Spotify API regarding saved episodes or pagination?
Could this be related to user-specific permissions/scopes (e.g. user-library-read)?
Is there an official Spotify changelog where such changes are documented?

At the moment, it is unclear whether:

this affects all users,
only specific accounts,
or if there has been an undocumented API change.

Any insights would be appreciated. Happy to provide additional debugging details if needed.

Thanks.

Originally created by @paha77 on GitHub (Feb 15, 2026). Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/286 Hi, since a few days ago, the `getMyEpisodes()` method seems to ignore the offset parameter. ### Context We are paginating through a user’s saved episodes using getMyEpisodes() with explicit limit and offset parameters, e.g.: ```php $episodes = $api->getMyEpisodes([ 'limit' => 50, 'offset' => 50, ]); ``` Previously, this returned the expected “next page” of results. However, as of recently, the response appears to always return the first page, regardless of the offset value provided. ### Observed Behavior - offset is set explicitly (e.g. 50, 100, etc.) - Response still contains items starting from index 0 - The returned payload structure itself looks valid - No error is thrown - Behavior is reproducible and consistent ### Assumptions From initial inspection, this looks like a potential upstream issue with the Spotify Web API rather than a client-side bug in this library. The request parameters appear to be constructed correctly. ### Questions 1. Has anyone else observed similar behavior with `getMyEpisodes()` (or other paginated endpoints)? 2. Is there any known recent change in the Spotify API regarding saved episodes or pagination? 3. Could this be related to user-specific permissions/scopes (e.g. user-library-read)? 4. Is there an official Spotify changelog where such changes are documented? At the moment, it is unclear whether: - this affects all users, - only specific accounts, - or if there has been an undocumented API change. Any insights would be appreciated. Happy to provide additional debugging details if needed. Thanks.

kerem

2026-02-27 19:26:37 +03:00

closed this issue
added the
bug

upstream
labels

kerem commented

2026-02-27 19:26:38 +03:00

Author

Owner

@paha77 commented on GitHub (Feb 15, 2026):

This could be related to these changes, although it's not explicitly mentioned here.

@paha77 commented on GitHub (Feb 15, 2026): This could be related to [these changes](https://developer.spotify.com/documentation/web-api/references/changes/february-2026), although it's not explicitly mentioned here.

kerem commented

2026-02-27 19:26:38 +03:00

Author

Owner

@paha77 commented on GitHub (Feb 15, 2026):

GET v1/me/episodes?limit=2 returns

{
  "href": "https://api.spotify.com/v1/me/episodes?offset=0&limit=2&locale=*",
  "limit": 2,
  "next": "https://api.spotify.com/v1/me/episodes?offset=2&limit=2&locale=*",
  "offset": 0,
  "previous": null,
  "total": 953,
  "items": [
    {
      "added_at": "2026-02-14T05:28:45Z",
      ...
      "id": "3GGaRrCVBuCs7hlhivHHOY"
      ...
    },
    {
      "added_at": "2026-02-14T05:28:45Z",
      ...
      "id": "3zVT64LoUbUZ7rfT03InzT"
      ...
    },
  ]
}

But when I call:

GET v1/me/episodes?offset=2&limit=2 returns

{
  "href": "https://api.spotify.com/v1/me/episodes?offset=2&limit=2&locale=*",
  "limit": 2,
  "next": "https://api.spotify.com/v1/me/episodes?offset=4&limit=2&locale=*",
  "offset": 4,
  "previous": "https://api.spotify.com/v1/me/episodes?offset=0&limit=2&locale=*",
  "total": 953,
  "items": [
    {
      "added_at": "2026-02-14T05:28:45Z",
      ...
      "id": "3GGaRrCVBuCs7hlhivHHOY"
      ...
    },
    {
      "added_at": "2026-02-14T05:28:45Z",
      ...
      "id": "3zVT64LoUbUZ7rfT03InzT"
      ...
    },
  ]
}

Listing in items exactly the same episodes.

@paha77 commented on GitHub (Feb 15, 2026): `GET v1/me/episodes?limit=2` returns ```json { "href": "https://api.spotify.com/v1/me/episodes?offset=0&limit=2&locale=*", "limit": 2, "next": "https://api.spotify.com/v1/me/episodes?offset=2&limit=2&locale=*", "offset": 0, "previous": null, "total": 953, "items": [ { "added_at": "2026-02-14T05:28:45Z", ... "id": "3GGaRrCVBuCs7hlhivHHOY" ... }, { "added_at": "2026-02-14T05:28:45Z", ... "id": "3zVT64LoUbUZ7rfT03InzT" ... }, ] } ``` But when I call: `GET v1/me/episodes?offset=2&limit=2` returns ```json { "href": "https://api.spotify.com/v1/me/episodes?offset=2&limit=2&locale=*", "limit": 2, "next": "https://api.spotify.com/v1/me/episodes?offset=4&limit=2&locale=*", "offset": 4, "previous": "https://api.spotify.com/v1/me/episodes?offset=0&limit=2&locale=*", "total": 953, "items": [ { "added_at": "2026-02-14T05:28:45Z", ... "id": "3GGaRrCVBuCs7hlhivHHOY" ... }, { "added_at": "2026-02-14T05:28:45Z", ... "id": "3zVT64LoUbUZ7rfT03InzT" ... }, ] } ``` Listing in `items` exactly the same episodes.

kerem commented

2026-02-27 19:26:38 +03:00

Author

Owner

@paha77 commented on GitHub (Feb 15, 2026):

I've just tried it with another account; the behavior is the same.

@paha77 commented on GitHub (Feb 15, 2026): I've just tried it with another account; the behavior is the same.

kerem commented

2026-02-27 19:26:38 +03:00

Author

Owner

@jwilsson commented on GitHub (Feb 16, 2026):

Hello!
This does indeed look like a change in the API. I'm getting the same results as you do, I've tried with different client IDs (one extended quota mode and one development mode). I think you'll need to post on their forums.

@jwilsson commented on GitHub (Feb 16, 2026): Hello! This does indeed look like a change in the API. I'm getting the same results as you do, I've tried with different client IDs (one extended quota mode and one development mode). I think you'll need to post on [their forums](https://community.spotify.com/t5/Spotify-for-Developers/bd-p/Spotify_Developer).

kerem commented

2026-02-27 19:26:38 +03:00

Author

Owner

@paha77 commented on GitHub (Feb 16, 2026):

I think you'll need to post on their forums.

I've posted it: https://community.spotify.com/t5/Spotify-for-Developers/Offset-parameter-appears-to-be-ignored-v1-me-episodes/td-p/7343213

@paha77 commented on GitHub (Feb 16, 2026): > I think you'll need to post on [their forums](https://community.spotify.com/t5/Spotify-for-Developers/bd-p/Spotify_Developer). I've posted it: https://community.spotify.com/t5/Spotify-for-Developers/Offset-parameter-appears-to-be-ignored-v1-me-episodes/td-p/7343213

kerem commented

2026-02-27 19:26:38 +03:00

Author

Owner

@jwilsson commented on GitHub (Feb 19, 2026):

Looks like this has been resolved upstream, closing this one.

@jwilsson commented on GitHub (Feb 19, 2026): Looks like this has been resolved upstream, closing this one.

kerem commented

2026-02-27 19:26:38 +03:00

Author

Owner

@paha77 commented on GitHub (Feb 19, 2026):

Looks like this has been resolved upstream, closing this one.

https://community.spotify.com/t5/Spotify-for-Developers/Offset-parameter-appears-to-be-ignored-v1-me-episodes/m-p/7344662/highlight/true#M20548

@paha77 commented on GitHub (Feb 19, 2026): > Looks like this has been resolved upstream, closing this one. https://community.spotify.com/t5/Spotify-for-Developers/Offset-parameter-appears-to-be-ignored-v1-me-episodes/m-p/7344662/highlight/true#M20548

kerem referenced this issue

2026-02-27 19:26:54 +03:00

[PR #211] [MERGED] Update Request.php #276