Use HTTPS and HTTP Basic authentication with approved API credentials. Keep credentials on your application server. These Hosted PBX endpoints use /hpbx/ on api.multitel.net; do not insert /v3. Check both the HTTP result and the application status in the JSON response.
Request a bounded date range
curl --request POST --user "USERNAME:PASSWORD" \
--data-urlencode "date_from=2026-10-01" \
--data-urlencode "date_to=2026-10-02" \
--data-urlencode "disposition=ANSWERED" \
"https://api.multitel.net/hpbx/cdrs/YOUR_BILLING_CODE?start=0&length=50"Replace the billing code and dates. Date filters include the stated days. For this endpoint, body filters are form-encoded and paging is in the query string.
Filters and response
| Parameter | Meaning |
|---|---|
| date_from / date_to | Start/end dates in YYYY-MM-DD format. |
| wherelanded | Destination filter when needed. |
| disposition | Call outcome filter, for example ANSWERED. |
| callerid | Calling-number filter. |
| timezone | The supported timezone identifier, when used; do not assume it accepts an IANA name. |
| start / length | Query parameters controlling the returned page. |
Call records contain start time, caller identity, source, first destination, billable seconds, disposition and call identifiers. Use the returned result structure for this endpoint; it can differ from portal API pagination. A successful HTTP request is not proof that the result contains matching calls.
Use the current call-history reference for portal REST integrations, including its response schema and account permissions.