Skip to content
Thirdlane

Reporting

Reporting endpoints are historical and read-only. They let you pull call detail records, message detail records, and recorded calls into dashboards, data warehouses, and analytics tools.

All examples use https://your-server.thirdlane.com and tenant acme; authenticate with an X-API-Key header. All list endpoints support limit/offset pagination and a from/to time range (epoch seconds or ISO-8601).

Call detail records (CDR)

Terminal window
curl -H "X-API-Key: YOUR_KEY" \
  "https://your-server.thirdlane.com/api/reports/cdr/acme?from=2026-01-01T00:00:00Z&limit=100"

Common filters: src, dst, disposition (ANSWERED, NO ANSWER, BUSY, FAILED), did, trunk, accountcode, uniqueid, and search (substring match on caller ID). Each record includes a has_recording flag.

Message detail records (MDR)

Terminal window
curl -H "X-API-Key: YOUR_KEY" \
  "https://your-server.thirdlane.com/api/reports/mdr/acme?direction=outbound&limit=100"

Common filters: direction, status, number, did, and gateway_name.

Recorded calls

List recordings, each with an absolute download_url you can fetch directly (with the same authentication).

Terminal window
curl -H "X-API-Key: YOUR_KEY" \
  "https://your-server.thirdlane.com/api/reports/recorded-calls/acme?from=2026-01-01T00:00:00Z"

Fetch a single recording’s metadata by call unique id:

Terminal window
curl -H "X-API-Key: YOUR_KEY" \
  "https://your-server.thirdlane.com/api/reports/recorded-calls/acme/1737830000.42"

Common filters: src, dst, agent, did, type, uniqueid, and search.

Call history

For per-user Thirdlane Connect call history, see the Call History API in the OpenAPI REST reference.