Every conversation and call is filed under a customer, the same person on all your channels. Customers are matched only by details nobody can fake, such as the number they call from or the ID your site signs for a signed-in visitor; an email or phone number someone types in is kept on the profile, and your team merges customers on the dashboard. Your systems can read the customer library, keep it up to date and add what happens outside EvaSay.
| Method | Path | What it does |
|---|---|---|
| GET | /api/v1/voice/contacts | Customers, the most recently seen first: q searches names, emails, phones, companies and tags, segment_id keeps one group's, limit (up to 100) and offset page |
| GET | /api/v1/voice/contacts/{id} | One customer with their details, tags, consent and your own fields |
| PATCH | /api/v1/voice/contacts/{id} | Change name, email, phone, company, city, country, language, timezone, tags or attributes |
| GET | /api/v1/voice/contact-fields | Your own customer fields: each key, label, type and options |
| GET | /api/v1/voice/contacts/{id}/events | The customer's timeline, the newest first |
| POST | /api/v1/voice/contacts/{id}/events | Add an event from your own systems |
| GET | /api/v1/voice/contacts/{id}/consent | Every consent change, with where it came from and its evidence |
| POST | /api/v1/voice/contacts/{id}/consent | Record a consent change |
| GET | /api/v1/voice/segments | Customer groups; counts=true adds how many customers each has now |
curl https://evasay.com/api/v1/voice/contacts/CONTACT_ID \
-X PATCH \
-H "Authorization: Bearer sk-your-key" \
-H "Content-Type: application/json" \
-d '{ "company": "Acme Dental", "tags": ["vip"], "attributes": { "plan": "Gold" } }'
tags replaces all of the customer's tags. attributes takes the keys of your own fields (add them on the Customers page; GET /api/v1/voice/contact-fields lists them) with a value of the field's type; an empty string clears one. A value your team entered on the dashboard is kept: the API does not overwrite it, and neither does the agent. Changing an email or phone number does not merge the customer with another one who has it. The standard details (name, email, phone and the rest) are replaced as sent.
Send what happens in your own systems, such as a purchase, a visit or a renewal, so it shows on the customer's timeline:
curl https://evasay.com/api/v1/voice/contacts/CONTACT_ID/events \
-X POST \
-H "Authorization: Bearer sk-your-key" \
-H "Content-Type: application/json" \
-d '{ "event_id": "order-1042", "name": "order_paid", "subject": "Order 1042", "values": { "total": "89.00" } }'
name uses lower case letters, digits, _ and .. event_id is your own ID: the same event_id on the same customer is recorded once, so retrying is safe, and accepted is false for a repeat. values holds text, flags holds true or false, and appointment_at is a time in Unix milliseconds.
EvaSay keeps four kinds of consent apart: marketing_email, marketing_sms, marketing_calls and service_calls (the two kinds of calls include calls in an AI voice). Each is granted, withdrawn or, before any record, unknown. A change is never edited, only added to the history with its source and evidence:
{ "kind": "marketing_calls", "status": "granted", "note": "Ticked 'Call me about offers' on order 1042" }
Only keys of owners and admins can record consent, and note, your evidence, is required.
Groups are saved filters on the customer library: the ones every workspace has (all customers, VIP, new in the last 7 days and others), your industry's and the ones you make on the Customers page. GET /api/v1/voice/segments lists them with their id; pass it as segment_id to list a group's customers.
Your systems can also hear of changes as they happen: contact.created, contact.updated, contact.consent_changed and contact.merged are webhook events.