Vitor P. Miguel
12/03/2025, 9:34 AMkapa.ai
12/03/2025, 9:35 AMpage=1 - Next pages are page=2, page=3, … - Stop when a page returns fewer than 25 (or no) records Configure the stream’s Pagination section like this: 1. Mode: Page Increment [[Page increment](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#page-increment)] 2. Page size: 25 (or omit if the API does not accept a page size parameter) [[Page increment](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#page-increment)] 3. Start from page: 1 (because your API is one-based) [[Advanced page options](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#advanced-page-increment-options)] 4. Inject page number into outgoing HTTP request: - Inject into: request_parameter - Field name: whatever your API uses (e.g. page) 5. (Optional) Inject page size into outgoing HTTP request if your API supports it: - Inject into: request_parameter - Field name: e.g. page_size or per_page With that, Airbyte will call: - ...?page=1 → records - ...?page=2 → records - ...?page=3 → … - …until a page returns fewer records than the page size or empty, then it stops. [[Page increment](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#page-increment)]Vitor P. Miguel
12/03/2025, 10:32 AMkapa.ai
12/03/2025, 10:32 AMkapa.ai
12/03/2025, 10:32 AM$.links.next is in the body). - Property path: links, next (Connector Builder expects a comma‑separated path for nested fields, like the Twitter meta, next_token example). [[Cursor pagination](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#cursor-pagination)] 3. Inject cursor into request: - Inject into: path - This makes Airbyte replace the entire request URL with the value from links.next on subsequent calls, which is exactly the pattern used for APIs that return a full “next page” URL (same as the GitHub example). [[Cursor pagination](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#cursor-pagination)] Airbyte will then: - Call your initial URL (without cursor) - Read response.links.next - Call that URL as the next request - Continue until links.next is missing/empty, at which point it stops. [[Cursor pagination](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/pagination#cursor-pagination)]Vitor P. Miguel
12/03/2025, 11:18 AMkapa.ai
12/03/2025, 11:18 AMkapa.ai
12/03/2025, 11:19 AM120 - `interval`: PT1M (ISO-8601 for “1 minute”) [[Rate limiting](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/rate-limit-api-budget); [Rate object](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/reference#/definitions/Rate)] In YAML (for reference, same concept behind the UI): yaml api_budget: type: "HTTPAPIBudget" policies: - type: "MovingWindowCallRatePolicy" rates: - limit: 120 interval: "PT1M" matchers: - method: "GET" url_base: "<https://api.example.com>" This tells Airbyte to allow at most 120 calls in any 1‑minute window and automatically throttle requests to stay within that budget. [[Rate limiting](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/rate-limit-api-budget); [HTTP API Budget UI](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/global-configuration#http-api-budget)]