---
title: "Pagination and limits"
description: "Read datasets carefully across different API deployments."
---

## A1PBX result windows

The documented call-history and recording-list interfaces expose `limit` and `offset`. Confirm the maximum limit and whether offset represents a row position or page position on your deployment. Examples use an initial offset of zero; do not infer how the next request should advance.

## Consistent ordering

For call history, the reference supports `order_by=start_epoch desc`. Confirm tie behavior and use a stable record identifier for deduplication. New calls can shift results during pagination.

## Time ranges

Call history supports repeated `start_stamp[]` values for a range. Confirm timezone, inclusive/exclusive boundaries, and precision before scheduling an import.

## Account-specific limits

Request rate limits, retention, audio download limits, and number-lookup charges are not specified here. Obtain the applicable values from A1ROUTES for your account. Do not assume a fixed retry interval or unlimited access.