limit, then following the page URLs returned by the API.
Charge paginates top-level list endpoints with opaque page URLs. You make the first request with any supported filters and an optional limit, then continue the sequence by requesting the next_page_url or previous_page_url exactly as returned.
This matters because the page token is opaque. Do not construct or mutate page tokens manually. Once a pagination sequence starts, keep following the returned URLs until you reach the end of the result set.
Do not change filters after the first request in a pagination sequence.
Follow returned page URLs
When the response includesnext_page_url, request that URL exactly as returned.
cURL
previous_page_url, use it the same way. In both directions, the safest client behavior is to treat the returned URL as the complete instruction for the next request.
Parameters
integer
Maximum number of objects to return (default 10).Allowed range:
1 to 100.string
Page token from a previous list response. Use it only by following
next_page_url or previous_page_url.Attributes
array
required
List of objects returned for the current page.
string | null
required
URL for the next page of results, or
null when there is no next page.string | null
required
URL for the previous page of results, or
null when there is no previous page.
