API record limits

When you list records with Airtable's API, you won't necessarily get all of them at once. Instead, you will receive them in pages of up to 100 records at a time. As soon as a table has more than 100 records, you will need to make multiple requests, one per page.

For example, if your table has 501 records, the results will be spread across 6 pages, and therefore 6 HTTP requests are needed to fully capture all of that table's records. Your first request might look something like this with your base's app id appxxx and the table name:

https://api.airtable.com/v0/appxxx/TableName

You will get the first page of records (under the "records" key), but if there is another page, you'll also get an "offset" that would look something like this: 

"offset": "itrSJ1l4jlPyxEG6c/recxxx"

To fetch the next page (in other words, the next 100 records), you'll include that offset as a query parameter. For example: 

https://api.airtable.com/v0/appxxx/TableName?offset=itrSJ1l4jlPyxEG6c%2Frecxxx

This will give you the records from the next page. If there's another page, you'll repeat the process—grab the offset and put it in the offset query parameter. When the response doesn't include an offset anymore, you know you've reached the last page and can stop.