# Replace example resource IDs and ownerId with values from your workspace.
: "${POWERDIALER_API_KEY:?Set POWERDIALER_API_KEY to your scoped API key}"
# Set this once per operation; reuse it with the same request after a timeout.
: "${POWERDIALER_REQUEST_ID:?Set POWERDIALER_REQUEST_ID to a new UUID for this operation}"
curl --request PATCH \
--url 'https://api.migration.powerdialer.ai/api/public/v2/scheduled-calls/123' \
--header "Authorization: Bearer $POWERDIALER_API_KEY" \
--header "Idempotency-Key: $POWERDIALER_REQUEST_ID" \
--header 'Content-Type: application/json' \
--data '{
"notes": "Updated callback notes"
}'{
"id": 123,
"ownerId": "user_example",
"contactId": 123,
"phoneNumber": "+12125550100",
"scheduledAt": "2026-10-15T18:00:00.000Z",
"status": "Pending",
"notes": "Call back",
"callHistoryId": null,
"createdAt": "2026-10-12T12:00:00.000Z",
"updatedAt": "2026-10-12T12:00:00.000Z",
"timeZone": "America/New_York",
"timeZoneSource": "provided"
}{
"error": {
"code": "invalid_api_key",
"message": "API key is invalid, expired or revoked",
"requestId": "00000000-0000-4000-8000-000000000004"
}
}Update scheduled call
Requires a contact attributed to the credential workspace: ScheduledCall has no workspace column, so unlinked or unattributed legacy records are excluded. Owner restrictions apply. The API does not dial callbacks or alter in-app scheduling. scheduledAt is a UTC instant; contact timezone and source accompany it. Update scheduledAt, status or notes; omissions remain unchanged. Requires an Idempotency-Key. callHistoryId remains managed by the existing app.
# Replace example resource IDs and ownerId with values from your workspace.
: "${POWERDIALER_API_KEY:?Set POWERDIALER_API_KEY to your scoped API key}"
# Set this once per operation; reuse it with the same request after a timeout.
: "${POWERDIALER_REQUEST_ID:?Set POWERDIALER_REQUEST_ID to a new UUID for this operation}"
curl --request PATCH \
--url 'https://api.migration.powerdialer.ai/api/public/v2/scheduled-calls/123' \
--header "Authorization: Bearer $POWERDIALER_API_KEY" \
--header "Idempotency-Key: $POWERDIALER_REQUEST_ID" \
--header 'Content-Type: application/json' \
--data '{
"notes": "Updated callback notes"
}'{
"id": 123,
"ownerId": "user_example",
"contactId": 123,
"phoneNumber": "+12125550100",
"scheduledAt": "2026-10-15T18:00:00.000Z",
"status": "Pending",
"notes": "Call back",
"callHistoryId": null,
"createdAt": "2026-10-12T12:00:00.000Z",
"updatedAt": "2026-10-12T12:00:00.000Z",
"timeZone": "America/New_York",
"timeZoneSource": "provided"
}{
"error": {
"code": "invalid_api_key",
"message": "API key is invalid, expired or revoked",
"requestId": "00000000-0000-4000-8000-000000000004"
}
}Authorizations
Issued in Developers. Workspace/owner/scopes come from credential, never acting-user headers. API keys cannot manage API credentials.
Headers
Required. Omitting this header returns 400 idempotency_key_required and changes nothing; a value outside the pattern returns 400 idempotency_key_invalid. Persist one key for this logical operation before sending it. Reuse the same value only with the same method, path and body after a timeout. A changed request returns 409 idempotency_conflict; a matching retry returns the original response.
^[A-Za-z0-9._:-]{1,200}$Path Parameters
Numeric scheduled call ID.
1 <= x <= 2147483647Body
UTC instant. Writes must include Z or an explicit offset.
Explicit record status, consistent with the existing app. Completed status alone is not proof of dialing. Cancelling a completed callback returns 409 through PATCH or DELETE.
Pending, Completed, Failed, Cancelled 16000Response
Scheduled call result.
UTC instant. Writes must include Z or an explicit offset.
Pending, Completed, Failed, Cancelled