Skip to main content
GET
cURL
Retrieve call records for dashboards, support tools, exports, and reconciliation. This is the polling counterpart to webhooks.

When to use

  • Show recent calls in your product.
  • Reconcile webhook events with stored call records.
  • Filter campaign results by bulk_list_id.
  • Debug a recipient’s latest call status.

Query guidance

Use date ranges and pagination for production dashboards. Add filters such as agent_id, status, call_type, or bulk_list_id to keep responses focused.

Production note

Prefer webhooks for real-time workflows. Use call history for dashboards, backfills, and periodic consistency checks.

Headers

X-API-KEY
string
required

(Required) Your Ringg AI API key.

Example:

"7251cb4b-3373-43a4-844c-b27a1d45e0c9"

Query Parameters

start_date
string<date-time>
default:2025-09-25T00:00:00+05:30

Filter calls starting from this date (ISO 8601 format with timezone).

Example:

"2025-09-25T00:00:00+05:30"

end_date
string<date-time>
default:2025-09-25T23:59:59+05:30

Filter calls up to this date (ISO 8601 format with timezone).

Example:

"2025-09-25T23:59:59+05:30"

limit
integer
default:10

Maximum number of calls to return (default: 10).

Example:

50

offset
integer
default:0

Number of calls to skip (default: 0).

Example:

20

agent_id
string

Filter calls by assistant ID.

Example:

"830f767a-397e-4b39-82ff-235cd344e2f9"

status
enum<string>

Filter calls by status.

Available options:
registered,
ongoing,
retry,
error,
completed,
failed,
cancelled,
forwarded
Example:

"completed"

bulk_list_id
string

Filter calls by bulk list ID.

Example:

"123e4567-e89b-12d3-a456-426614174000"

Response

Successful Response: Call history. Response format depends on download_format parameter.

calls
object[]
limit
integer
offset
integer
count
integer
total
integer