Get Retry History

View every retry attempt for a call placed under a campaign with auto-retry enabled, including outcome per attempt.

GET /call-logs/{id}/retries

Get retry history for a call

cURL

curl --request GET \
  --url https://api.dialnexa.com/v1/call-logs/{id}/retries \
  --header 'Authorization: Bearer <token>'

200

{
  "call_id": "call_abc123",
  "data": [
    {
      "attempt": 1,
      "status": "no_answer",
      "timestamp": "2024-03-01T10:00:00.000Z"
    },
    {
      "attempt": 2,
      "status": "completed",
      "timestamp": "2024-03-01T12:00:00.000Z"
    }
  ]
}

Returns the complete retry history for a single call. When a campaign is configured with retry logic, calls that fail or are not answered are automatically redialled after a configured interval. This endpoint returns every dial attempt linked to the parent call, the attempt number, the outcome (completed, no-answer, busy, failed), the duration, and the timestamp of each attempt, so you can reconstruct exactly what happened before the lead was reached (or finally written off).

When to use this

• Why didn’t we reach this lead?: inspect the retry history to see whether the lead was repeatedly busy, never answered, or only failed on the first attempt.
• Tuning retry policy: if many leads reach the maximum retry count without ever being answered, consider extending the interval or shifting it to a different time of day. See Auto-retry.
• Compliance review: produce a per-call dial log to demonstrate the number of contact attempts made.
• Cost attribution: confirm how many billable minutes a difficult-to-reach lead consumed across attempts.

Path parameters

Parameter	Description
id	The parent call ID, for example call_x9y3zp4mq7r1.

Response fields

Field	Description
attempt	1-based attempt number.
status	Outcome of that attempt.
duration_sec	Connected duration of that attempt. 0 for no-answer or busy outcomes.
called_at	Timestamp when the attempt was placed.

Errors

• 404 Not Found is returned when the call does not exist.
• 403 Forbidden is returned when the API key cannot read call data on this workspace.

Request

curl "https://api.dialnexa.com/v1/call-logs/call_x9y3zp4mq7r1/retries" \
  -H "Authorization: Bearer YOUR_API_KEY"

Response

{
  "data": [
    { "attempt": 1, "status": "no-answer", "duration_sec": 0,  "called_at": "2024-05-01T10:00:00.000Z" },
    { "attempt": 2, "status": "no-answer", "duration_sec": 0,  "called_at": "2024-05-01T12:00:00.000Z" },
    { "attempt": 3, "status": "completed", "duration_sec": 98, "called_at": "2024-05-01T14:00:00.000Z" }
  ]
}

Related endpoints

• Get Call Log: final outcome of the parent call.
• Get Call Details: full transcript of the connected attempt.
• Auto-retry: how retry intervals and max attempts are configured.
• Concurrency and limits: how retries interact with concurrency caps.

Authorizations

Authorization · string · header · required

Pass your API key as a Bearer token in the Authorization header.

Path Parameters

id · string · required

Response

200 - application/json

Success.

call_id · string

Example:

"call_abc123"

data · object[]

Show child attributes

Example:

[
  {
    "attempt": 1,
    "status": "no_answer",
    "timestamp": "2024-03-01T10:00:00.000Z"
  },
  {
    "attempt": 2,
    "status": "completed",
    "timestamp": "2024-03-01T12:00:00.000Z"
  }
]