VoiceNotify API
Trigger automated outbound AI calls and receive structured call results for visualization, reporting, and workflow automation.
Endpoint
POST
https://api-v1.delight.fit/voicenotify
Headers
Content-Type: application/x-www-form-urlencoded
This defines how the request data is sent to the server.
Request Example
curl --location 'https://api-v1.delight.fit/voicenotify'
--header 'Content-Type: application/x-www-form-urlencoded'
--data-urlencode 'access_token=YOUR_ACCESS_TOKEN'
--data-urlencode 'rows=[{...}]'
Request Fields Explained
access_token
Your secure API key. This verifies that the request is authorized. Keep this confidential.
rows
An array of outbound call instructions. You can send multiple calls in one request.
message
The voice message the AI will speak during the call.
caller
The phone number displayed as the Caller ID.
phone
The destination phone number (the person being called).
language
Language used for the call (for example: "en" for English, "ja" for Japanese).
UTC
Timezone reference used for processing or scheduling.
callback_token
A custom identifier you define to match call results with your internal system (CRM, campaign ID, etc.).
callback_url
The URL where call results will be sent after the call is completed.
API Response Example
{
"success": "1",
"result": {
"count": "2",
"success_count": "2",
"errors_count": "0"
}
}
Response Fields
success
Whether the request was accepted (1 = success).
count
Total number of calls submitted.
success_count
Number of calls successfully processed.
errors_count
Number of failed calls.
Callback Response Example
{
"callee": "8190390456xx",
"caller": "8150505008xx",
"call_result_code": "200"
}
The call_result_code explains what happened during the call.
Call Result Codes
Below are the possible call_result_code values and what they mean.
200 – Call answered
Campaign type: Automated & Agent
The callee answered the call successfully.
1 – Voicemail detected
Campaign type: Automated & Agent
The call reached voicemail.
For agent campaigns, voicemail detection must be enabled in settings to classify it correctly.
2 – Initiated by the callee
Campaign type: Automated & Agent
The callee ended the call.
In agent campaigns, this may happen while the customer is waiting in queue.
3 – End of the scenario
Campaign type: Automated
The automated scenario reached its predefined ending point normally.
486 – The number is busy
Campaign type: Automated & Agent
The callee was already on another call.
408 / 487 / 500 – The callee didn’t answer
Campaign type: Automated & Agent
The phone was not answered or switched off.
603 – The call declined
Campaign type: Automated & Agent
The callee rejected or declined the call.
404 – Invalid number
Campaign type: Automated & Agent
The destination phone number is incorrect or does not exist.
480 – The callee is unavailable
Campaign type: Automated & Agent
The phone is switched off or out of network coverage.
403 – Call not allowed
Campaign type: Automated & Agent
The number is restricted or included in a Do Not Call (DNC) list.
0 – No call performed
Campaign type: Automated & Agent
The call was interrupted before reaching the callee.
4 – Call interrupted by Stop button
Campaign type: Automated
The call was manually stopped during scenario testing.
This does not appear in call history.
5 – Failed to reach an agent
Campaign type: Agent
The system could not connect the call to an available agent.
610 – Telecom operator error
Campaign type: Automated & Agent
The call failed due to telecom carrier issues.
How to Use Call Results for Action
You can use these result codes to:
• Automatically retry busy or unanswered calls
• Update CRM lead status
• Measure connection rate and contact rate
• Identify invalid numbers and clean your database
• Build dashboards for campaign performance
Every call becomes structured data.
Structured data becomes insight.
Insight becomes action.
