Delete Schedule Call - CallKaro AI Docs

This endpoint deletes a scheduled call for a specific agent and phone number combination. Once deleted, the scheduled call will not be executed.

Quick Example

curl -X POST "https://api.callkaro.ai/call/delete-schedule-call?agent_id=YOUR_AGENT_ID" \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: YOUR_API_KEY" \
  -d '{
    "to_number": "919876543210"
  }'

Use Cases

Cancel follow-ups: Remove scheduled follow-up calls when customers request to be removed
Reschedule calls: Delete existing scheduled calls before creating new ones at different times
Prevent duplicates: Clean up duplicate scheduled calls before scheduling new ones
Campaign management: Remove specific phone numbers from scheduled campaign calls

Parameters

string

required

The agent ID for which to delete scheduled calls

string

required

The phone number for which to delete the scheduled call. Can be in international format with or without ’+’ prefix.

Common Scenarios

Delete scheduled call with Indian number

{
  "to_number": "919876543210"
}

The number will be processed and scheduled call deleted for this phone number.

Using form data instead of JSON

curl -X POST "https://api.callkaro.ai/call/delete-schedule-call?agent_id=YOUR_AGENT_ID" \
  -H "X-API-KEY: YOUR_API_KEY" \
  -F "to_number=919876543210"

Form data is also supported as an alternative to JSON body.

Response

Success (200 OK)

{
  "status": "success",
  "message": "Scheduled call deleted successfully"
}

Errors

Bad Request

Missing required parameters

{"status": "error", "message": "Missing agent_id in request query"}

{"status": "error", "message": "Missing to_number in request"}

Forbidden

Invalid or missing API key

{"status": "error", "message": "Missing X-API-KEY in headers"}

Server Error

Internal server error - contact support

{"status": "error", "message": "Internal server error"}

Best Practices

Always verify the agent_id exists before attempting to delete scheduled calls
Use this endpoint as part of your workflow when rescheduling calls to avoid duplicates
Consider implementing retry logic for network failures
Log successful deletions for audit purposes

​Quick Example

​Use Cases

​Parameters

​Common Scenarios

​Response

​Success (200 OK)

​Errors

​Best Practices

Quick Example

Use Cases

Parameters

Common Scenarios

Response

Success (200 OK)

Errors

Best Practices