@Nicholas_Turbanov did you ever figure this out? We are just starting to use Airtable and the API and have been running into this error. It is indeed frustrating and there is not much documentation on how to handle it.
Yes and no.
The value of “offset” consists of two different concatenated values
foobar/recdxxxyyyzzz
The limiter is the slash. The second value, _ recdxxxyyyzzz_, is the last record returned in the response.
But the first value, _ foobar_, is apparently some token that changes over time. So you can make the same paginated calls for some x amount of time until that value changes.
I did not figure out how often the token changes. Basically you always have to query the first page initially and then the subsequent pages. You can’t really make a query for the nth page directly.
Kinda of a weird choice by Airtable if you ask me.
Thank you for the response! That sounds a bit strange re: the token change, but definitely good to know. It sounds like if our iterative API calls to pull a full list of records are too slow or take longer than the token change, we’d have to start the iteration over and try again.
Hi, I have tutorial on how to do pagination with the api. Check out it and let me know if it helped.
Airtable’s API is great and so is their documentation. However, I came across a small stumbling block while using it to build a simple project. The problem, Airtable returns a maximum of 100 records…
