Skip to main content
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

​
agent_id
string
required
The agent ID for which to delete scheduled calls
​
to_number
string
required
The phone number for which to delete the scheduled call. Can be in international format with or without ’+’ prefix.

​
Common Scenarios

{
  "to_number": "919876543210"
}
The number will be processed and scheduled call deleted for this phone number.
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

​
400
Bad Request
Missing required parameters
{"status": "error", "message": "Missing agent_id in request query"}
or
{"status": "error", "message": "Missing to_number in request"}
​
403
Forbidden
Invalid or missing API key
{"status": "error", "message": "Missing X-API-KEY in headers"}
​
500
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