Setup
Send Superfone calls here
One endpoint, any field naming. Post a call event as JSON (or form-encoded) and it lands in your database within milliseconds.
1 · Your endpoint
{{ORIGIN}}/api/superfone/calls
Method POST · Content-Type application/json · a 200 reply means the row is stored.
2 · Secure it
Set SUPERFONE_WEBHOOK_SECRET in the Environment tab, then
send it on every request as the header
x-superfone-token
(Authorization: Bearer … and
?token=… also work).
3 · Point Superfone at it
- Direct: in the Superfone app open Settings → Integrations / Webhooks, add an outgoing webhook for call completed and missed call, and paste the URL above.
- Via Pabbly Connect: create a workflow with Superfone (or its incoming webhook) as the trigger, add an API / Webhook → POST action step, paste the URL, map the call fields and set the token header.
- From your phone system: any tool that can POST JSON works — the field names below are all recognised.
curl -X POST "{{ORIGIN}}/api/superfone/calls" \
-H "Content-Type: application/json" \
-H "x-superfone-token: YOUR_SECRET" \
-d '{
"call_id": "SF-88214",
"call_type": "incoming",
"call_status": "answered",
"customer_name": "Rohit Khandelwal",
"customer_number": "+919825114207",
"agent_name": "Sana Kulkarni",
"agent_number": "+918069992201",
"duration": 214,
"recording_url": "https://recordings.superfone.in/sf-88214.mp3",
"notes": "Asked for bulk pricing",
"start_time": "2026-11-18T10:42:00+05:30"
}'
4 · Send a test event
Writes one sample call into your database so you can see the shape of a stored row.
Open the console to see it at the top of the table.
Field mapping
| Stored column | Accepted keys in your payload |
|---|---|
| external_id | call_id, callId, id, uuid, sid, call_sid, reference — used to de-duplicate retries |
| direction | direction, call_type, type (incoming/outgoing, inbound/outbound, dialled) |
| status | status, call_status, disposition, result (answered, missed, busy, voicemail) |
| contact_name | customer_name, contact_name, caller_name, client_name, lead_name, name |
| contact_number | customer_number, contact_number, phone, mobile, from / to by direction |
| agent_name | agent_name, agent, user_name, answered_by, handled_by, team_member |
| agent_number | agent_number, superfone_number, virtual_number, business_number |
| duration_sec | duration, duration_sec, call_duration, talk_time, billsec (seconds or mm:ss) |
| recording_url | recording_url, recording, recording_link, audio_url |
| started_at | start_time, started_at, timestamp, call_time, created_at, epoch seconds or ms |
| notes | notes, note, remarks, comments, tags, summary |
| raw | the complete payload, kept verbatim for anything not mapped |
5 · Read your data back
For your CRM, dashboard or another Pabbly workflow:
GET {{ORIGIN}}/api/calls?limit=100&direction=inbound&status=missed
Header: x-superfone-token: YOUR_SECRET → { "ok": true, "count": n, "calls": [ … ] }
Or grab the whole table as a spreadsheet: export.csv
Your call history, finally yours.