Pagination

The Tolinku API uses limit-based pagination on endpoints that return collections.

How it works

List endpoints accept a limit query parameter to control the number of results returned:

GET /v1/api/analytics/events?limit=50
GET /v1/api/referral/leaderboard?limit=25
GET /v1/api/audiences/:id/users?limit=100

Endpoint limits

Endpoint	Default	Maximum
GET /v1/api/analytics/events	50	200
GET /v1/api/referral/leaderboard	25	100
GET /v1/api/audiences/:id/users	100	1,000

Response format

List responses include the collection and a count:

{
  "events": [ ... ],
}

{
  "users": ["user_123", "user_456"],
  "count": 2
}

{
  "leaderboard": [
    { "referrer_id": "user_123", "completed_count": 15, "rank": 1 }
  ]
}

Notes

• Most analytics endpoints return aggregate data (not paginated lists). The overview, funnel, timeseries, campaigns, and geo endpoints return complete result sets for the requested date range.
• The export endpoint returns all events as a CSV file download, not a paginated JSON response.
• Banner and message list endpoints return all active items (typically a small number) without pagination.