Help Wizard
Step 1
Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Just quickly...
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Help categories
Account & Payment
Using Spotify
Listen Everywhere
I’m facing an issue with pagination in the Spotify Search Web API where the total value changes unexpectedly when updating the offset.
Steps to reproduce:
Perform a search request (e.g., /v1/search) with:
limit = 10
offset = 0
The response returns a total value = N
Change the offset to offset = N - 10
The response now returns a different total value = M (where M ≠ N)
Expected behavior:
The total count should remain consistent for the same query, regardless of offset changes, as it represents the total number of matching results.
Actual behavior:
The total value changes when the offset is updated, which breaks pagination logic and makes it unreliable to calculate the last page or total pages.
Impact:
This makes cursor/offset-based pagination unpredictable
UI pagination (page numbers, last page detection) becomes incorrect
Difficult to determine when all results have been fetched
Has anyone else encountered this issue, or is this expected behavior due to backend ranking/index updates?
Suggested posts
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…
