When you load your Facebook news feed, you only see the first 10 results. When you scroll down, Facebook loads more posts to the feed and you see the next 10 results.

It would take ages to load if Facebook would try to load the whole news feed in one go. If you have to wait 1 second for 10 posts to load, you'd be waiting a whole minute for all 600 posts to load.

In a similar way to Facebook's news feed, APIs often split their datasets into smaller packages. So when you request let's say a dataset that contains 10 years of Bitcoin candles (OHLCs), you might need to paginate through the results to get the whole dataset (i.e. request #1 would include data for the first 5 years and request #2 would include data for the next 5 years).

In addition to splitting datasets into pages, data APIs also charge on a per-request basis so rather than paying $1 for the full 1000 rows of data, you'd pay $0.1 for every 100 rows.

How pagination works on

Since our site is made to load datasets, we've eliminated the pagination component - all you need to select is the number of rows you'd like to retrieve. When pagination is present in an API, you will see a slider at the bottom of the query tab:

When you move the slider, pricing will adjust based on the per-request price of the API.

If we end up retrieving fewer rows (either because the API has run out of results or because a request failed), we will not charge you for the requests that did not execute.

For example, let's say an API charges 1 credit per 100 rows of data and you entered that you want to pull 1000 rows. If we end up retrieving 500 rows, you will only be charged 0.5 credits.

Last updated