Paginating API Results

Paginating API Results

List endpoints return data in pages so responses stay fast.

Cursor-Based Pagination

Kinexa uses cursors rather than page numbers, which is reliable even when data changes between requests.

curl "https://api.kinexa.id/v1/contacts?limit=50" \
  -H "Authorization: Bearer kx_live_xxxxx"

Response Shape

{
  "data": [ /* up to 50 items */ ],
  "has_more": true,
  "next_cursor": "c_aGVsbG8"
}

Fetching the Next Page

Pass next_cursor as the cursor parameter:

curl "https://api.kinexa.id/v1/contacts?limit=50&cursor=c_aGVsbG8"

Keep looping while has_more is true.

Limits

• Default limit: 20
• Maximum limit: 100

Tips

• Don't store cursors long-term — they're meant for sequential traversal
• For full exports, prefer the dedicated export endpoint over manual pagination
• Sort with sort=created_at&order=desc to process newest records first