List call history | A1ROUTES Developers

Retrieve call detail records for reporting and integration with your business systems.

Account availability: These examples describe the A1PBX version 7 interface. Confirm the endpoint, header authentication, response format, and record permissions for your assigned account before production use.

Request

Retrieve call detail records for reporting and integration with your business systems.

GET/xml_cdrA1PBX API

Parameters

Parameter	Type	Required	Description
`limit`	integer	No	Requested result count; account limits may apply.
`offset`	integer	No	Pagination position; verify the deployed API semantics.
`order_by`	string	No	Sort expression, for example start_epoch desc.
`start_stamp[]`	string	No	Repeat this parameter for the start and end of a date range. Confirm account timezone and boundary behavior.

Examples

Request example

1curl --fail-with-body --get \
2  "https://$A1PBX_ACCOUNT_ID.a1routes.com/app/api/7/xml_cdr" \
3  --header "Authorization: Basic $A1PBX_API_KEY" \
4  --data-urlencode "limit=20" \
5  --data-urlencode "offset=0" \
6  --data-urlencode "order_by=start_epoch desc"

Inspect an authorized response from your account to establish the returned fields, content type, and empty-result behavior. Response schemas are intentionally not asserted until verified for the deployed service.

Integration notes

The source interface supports date ranges using repeated start_stamp[] parameters and sorting such as start_epoch desc. Confirm timezone, range inclusivity, and offset behavior. Retention and maximum result size are account-specific.

See authentication, pagination, and error handling.