> ## Documentation Index
> Fetch the complete documentation index at: https://docs.capitalcheckin.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Pagination

> Learn how to handle pagination in the Capital Check In API

# Pagination

The Capital Check In API uses cursor-based pagination for endpoints that return lists of resources.

## Pagination Parameters

When making requests to endpoints that support pagination, you can use the following query parameters:

| Parameter | Type    | Description                                           |
| --------- | ------- | ----------------------------------------------------- |
| `limit`   | integer | Number of items to return (default: 20, max: 100)     |
| `cursor`  | string  | Cursor for pagination (returned in previous response) |

## Example Request

```bash theme={null}
GET /collaborators?limit=10&cursor=eyJpZCI6MTIzfQ==
```

## Response Format

Paginated responses include pagination metadata:

```json theme={null}
{
  "data": [
    // Array of resources
  ],
  "pagination": {
    "hasMore": true,
    "nextCursor": "eyJpZCI6MjM0fQ==",
    "total": 150
  }
}
```

## Pagination Metadata

| Field        | Type    | Description                                      |
| ------------ | ------- | ------------------------------------------------ |
| `hasMore`    | boolean | Whether there are more items available           |
| `nextCursor` | string  | Cursor for the next page (null if no more pages) |
| `total`      | integer | Total number of items (if available)             |

## Best Practices

* Use appropriate `limit` values based on your needs
* Always check `hasMore` before making additional requests
* Store the `nextCursor` for subsequent requests
* Handle cases where `nextCursor` is null (end of results)