Contacts and call data

​

Who is calling: screen-pop

curl "https://api.your-host/api/v1/contacts/lookup?number=0412345678" \
  -H "authorization: Bearer $FIRETONE_KEY"

• the contact, including your external_ref;
• their open tickets;
• the last five conversation summaries;
• the last call.

​

Keep contacts in step with your CRM

curl -X PUT https://api.your-host/api/v1/contacts/by-reference/crm-4411 \
  -H "authorization: Bearer $FIRETONE_KEY" -H 'content-type: application/json' \
  -d '{ "e164": "+61412345678", "name": "Sam Taylor", "attributes": { "tier": "gold" }, "dnc": false }'

• Already known by that reference: it’s updated, and attributes merge into the ones it has.
• New reference, but someone already has the number: that contact takes the reference, so nothing is duplicated.
• Otherwise: it’s created (201), and contact.created is sent.
• A number that belongs to a contact with a different reference is refused with 409.

​

Export calls

curl "https://api.your-host/api/v1/cdrs/export?from=2026-09-01T00:00:00Z&to=2026-10-01T00:00:00Z&format=csv" \
  -H "authorization: Bearer $FIRETONE_KEY" -o september.csv

• Formats: CSV with a header row, or format=ndjson for one JSON object per line.
• At most 31 days per request, streamed oldest first.
• Columns:
  • the call: call_uuid, direction, the numbers, started_at, answered_at, ended_at, duration_sec, billsec, hangup_cause;
  • who handled it: agent, extension and team;
  • links: contact_id, campaign_id and your reference;
  • whether it was recorded;
  • the charge (sell_amount), which is empty unless the key may see billing.
• Scope: narrowed like the call list, so a supervisor’s key gets their teams’ calls.