Learn and improve

Connect to what you already use. Replace nothing.

The platform exposes a REST API for contact import, campaign management, and conversation outcome retrieval. Connect your CRM, your marketing automation platform, or your internal tooling — without replacing anything in your existing stack.

See it in actionRead the docs
Integration capabilities
  • Contact import APIpush contacts from CRM without CSV upload
  • Campaign management APIcreate and update campaigns programmatically
  • Conversation outcome webhooksBOOKED, TIMED_OUT events pushed to your stack
  • Audit log exportfull compliance CSV — scoped to your client
  • Token-based authAPI keys per client — scoped access control
REST APIJSON endpoints for contacts, campaigns, and conversations
Webhooksconversation outcome events pushed to your endpoint in real time
CSV exportfull audit log — every message, decision, and change
Client-scopedAPI keys and exports scoped to client data — no cross-client access
How integration works

Push contacts in. Pull outcomes out. No manual handoffs.

The platform API lets you trigger campaign activity from your existing tools. Push contacts from your CRM directly via API instead of CSV upload. Receive conversation outcome webhooks in real time — BOOKED and TIMED_OUT events posted to your endpoint as they happen. Pull audit logs on demand.

  • Contact import via API — push directly from CRM without CSV export/upload cycle
  • Campaign creation and update via API — manage campaigns programmatically
  • Conversation outcome webhooks — BOOKED, TIMED_OUT, CLOSED events pushed in real time
  • Audit log export via API — full CSV on demand, date-range filterable
  • Token-based authentication — API keys scoped to client data
  • All API access subject to the same client scoping as the operator platform
CRM integration flow
  1. 1
    CRM identifies segment
    Reactivation list, speed-to-lead trigger, etc.
  2. 2
    Contacts pushed via API
    POST to contact import endpoint — validated, encrypted
  3. 3
    Campaign launched
    Via API or operator platform — same campaign config
  4. 4
    Conversations run
    AI handles qualification, booking, compliance
  5. 5
    Outcome webhook fires
    BOOKED event posted to CRM endpoint in real time
  6. 6
    CRM updated
    Contact status, booking date, qualification outcome synced
What you can integrate

Your stack. Your workflow. Our AI in the middle.

The API is built for common integration patterns — CRM triggers, marketing automation hand-offs, and compliance reporting. If your use case isn't covered, the REST API lets you build it.

CRM-triggered campaigns

Connect your CRM to push contacts into a campaign automatically when a trigger fires — a lapsed customer crosses a dormancy threshold, a new inbound lead arrives, a deal stalls in the pipeline. No manual CSV export required.

How it works: Contact import API accepts the same fields as CSV upload — validation, opt-out protection, and encryption all apply.

Booking outcome sync

When a contact reaches BOOKED state, the webhook fires immediately. Your CRM receives the contact ID, campaign name, and booking timestamp — and can update the contact record, create a deal stage, or trigger a calendar invite without human intervention.

How it works: Webhook fires on conversation state change — BOOKED, TIMED_OUT, CLOSED. Event includes enough data to action without a follow-up API call.

Compliance export

The audit log export API returns a full CSV of all messages, compliance decisions, AI directives, and campaign changes for your client — filterable by date range. Use it for internal compliance reporting or to satisfy regulatory inspection requests.

How it works: Export scoped to your client's data — client admins can export their own data, Friyay operators can export any client's data.

Access control

API keys are scoped per client. A client admin's API key cannot access another client's data, regardless of what endpoint is called. The same database-level client scoping that protects the operator platform applies to all API calls.

How it works: Client scoping enforced at the database query layer — not just the UI. Direct API requests are scoped correctly even if the caller constructs a request manually.

Want to connect your CRM
to the platform?

We'll walk through the API, configure a webhook endpoint, and test the integration end to end.

Book a discovery callTalk to the team