Skip to main content
All list endpoints use cursor-based pagination. This is more reliable than offset pagination for real-time data.

​
How it works

  1. Make your first request with a limit:
curl -H "Authorization: Bearer oxi_sk_test_..." \
  "https://api.0xinsider.com/api/v1/leaderboard?limit=20"
  1. Check has_more and next_cursor in the response:
{
  "object": "list",
  "data": [...],
  "has_more": true,
  "next_cursor": "95.85_0x885783760858e1bd5dd09a3c3f916cfa251ac270"
}
  1. Pass next_cursor as the cursor param for the next page:
curl -H "Authorization: Bearer oxi_sk_test_..." \
  "https://api.0xinsider.com/api/v1/leaderboard?limit=20&cursor=95.85_0x885..."
  1. Repeat until has_more is false.

​
Parameters

ParameterTypeDefaultMax
limitinteger20100
cursorstring——

​
Cursor format

Cursors are opaque strings — don’t parse or construct them. Always use the next_cursor value from the previous response. Different endpoints use different cursor formats internally:
  • Leaderboard: {score}_{address}
  • Whale trades: {timestamp}_{id} (ISO 8601)
  • Insider radar: {score}_{id}

​
Tips

  • Cursors are stable for the current sort order. Don’t mix cursors between different filter combinations.
  • If you get a 400 with "Invalid cursor format", you’re using a cursor from a different endpoint or an expired cursor.