Pagination and rate limits

Filtered port, port log, and payment queries accept page and pageSize in a JSON body. The contract caps pageSize at 100.

{
  "page": 1,
  "pageSize": 100
}

Responses report data, page, pageSize, and total. Continue until the number of collected items reaches total or a page returns no data. Collection contents can change while paging, so avoid assuming a snapshot unless your workflow controls writes.

Request limits

The service defaults are:

Request class	Default limit
GET	60 requests per minute
POST, PUT, PATCH, DELETE	10 requests per minute

Deployments can override these values. Treat 429 as authoritative, add randomized backoff, and cap concurrency. Batch filtering with pageSize: 100 is more efficient than issuing many individual reads.

Backoff

For 429 and transient 5xx responses, use exponential backoff with jitter and a maximum attempt count. Never retry indefinitely.