Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Platform Pagination" |
| 4 | description: "Public guidance for endpoint-specific list limits and cursor pagination." |
| 5 | category: "auth-config" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-07-16T00:00:00Z" |
| 8 | tags: |
| 9 | - "api" |
| 10 | - "pagination" |
| 11 | - "cursors" |
| 12 | --- |
| 13 | # Platform Pagination |
| 14 | |
| 15 | ## Pagination limits are endpoint-specific |
| 16 | |
| 17 | Composio does not have one global page-size limit. Resource lists, catalogs, Tool Router, logs, and billing endpoints can define different limits, while toolkit actions also inherit provider-specific rules. Check the exact endpoint schema and live behavior before quoting a maximum. |
| 18 | |
| 19 | ## Auth-config list pages return at most 50 items |
| 20 | |
| 21 | `GET /api/v3/auth_configs` and `GET /api/v3.1/auth_configs` currently return at most 50 auth configs per page. Read `next_cursor` from each response and pass it as `cursor` until it is empty. |
| 22 | |
| 23 | Some generated descriptions may advertise a larger limit; the deployed endpoint still clamps the page to 50. Treat that documentation/runtime mismatch as a product issue, not as a reason to skip cursor pagination. |