cURL
# Replace example resource IDs and ownerId with values from your workspace.
: "${POWERDIALER_API_KEY:?Set POWERDIALER_API_KEY to your scoped API key}"
curl --request GET \
--url 'https://api.migration.powerdialer.ai/api/public/v2/scheduled-calls/123' \
--header "Authorization: Bearer $POWERDIALER_API_KEY"{
"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"
}
}Scheduled calls
Read 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. List filters use ownerId, status, and an optional inclusive from / exclusive to window on scheduledAt. Cursor pagination is ordered by numeric ID. Missing and inaccessible records return 404.
cURL
# Replace example resource IDs and ownerId with values from your workspace.
: "${POWERDIALER_API_KEY:?Set POWERDIALER_API_KEY to your scoped API key}"
curl --request GET \
--url 'https://api.migration.powerdialer.ai/api/public/v2/scheduled-calls/123' \
--header "Authorization: Bearer $POWERDIALER_API_KEY"{
"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.
Path Parameters
Numeric scheduled call ID.
Required range:
1 <= x <= 2147483647Response
Scheduled call result.
UTC instant. Writes must include Z or an explicit offset.
Available options:
Pending, Completed, Failed, Cancelled