Skip to main content

​
Overview

The Rntor API uses cursor-based pagination for endpoints that return lists of resources. This approach provides consistent results even when data is being modified.

​
Pagination Parameters

ParameterTypeDefaultDescription
limitinteger20Number of items per page (max: 100)
cursorstring-Cursor for the next page of results

​
Response Format

Paginated responses include a pagination object: 
{
  "data": [...],
  "pagination": {
    "has_more": true,
    "next_cursor": "eyJpZCI6IjEyMzQ1In0=",
    "total_count": 150
  }
}

​
Example

​
First Request

curl -X GET "https://api.rntor.com/v1/bookings?limit=20" \
  -H "Authorization: Bearer YOUR_CLIENT_SECRET" \
  -H "X-Client-ID: YOUR_CLIENT_ID"

​
Subsequent Requests

Use the next_cursor from the previous response: 
curl -X GET "https://api.rntor.com/v1/bookings?limit=20&cursor=eyJpZCI6IjEyMzQ1In0=" \
  -H "Authorization: Bearer YOUR_CLIENT_SECRET" \
  -H "X-Client-ID: YOUR_CLIENT_ID"

​
Best Practices

Use Reasonable Limits

Request only what you need. Smaller page sizes mean faster responses.

Handle Empty Pages

Always check has_more before requesting the next page.

Store Cursors Carefully

Cursors are opaque strings. Don’t modify or parse them.

Avoid Offset Pagination

Cursor-based pagination is more reliable for large datasets.