Pagination

Paginating list responses from ChargeIndia Hub.

List endpoints for locations, tariffs, sessions, and CDRs support offset-based pagination with OCPI Link headers.

Query parameters

ParameterTypeDescription
offsetintegerNumber of records to skip (default: 0)
limitintegerMaximum records per page
date_fromISO 8601Return only records updated after this timestamp

Example request

GET /ocpi/2.2.1/locations?offset=0&limit=50&date_from=2025-06-01T00:00:00Z
Authorization: Token {your-token}

When more results exist, the Hub includes an OCPI Link header:

Link: <https://hub.chargeindia.com/ocpi/2.2.1/locations?offset=50&limit=50>; rel="next"

Follow rel="next" links until no further page is returned.

Response envelope

{
  "status_code": 1000,
  "timestamp": "2025-06-23T10:00:00.000Z",
  "data": [ ... ]
}

Routing filter

Locations and tariffs are filtered by routing rules. Sessions and CDRs are filtered by cdr_token ownership (only records for your eMSP party).

Rate limits

List requests for locations, sessions, and CDRs are limited to 200 requests/minute per party. See Rate Limits & Errors.

Sync strategy

Recommended approach for eMSPs:

  1. Initial full sync with offset/limit pagination
  2. Periodic incremental sync using date_from set to last successful sync timestamp
  3. Handle empty pages gracefully (routing changes may reduce visible catalog rows)