Introduction
Use Sailor’s public API to configure the phone-system outcomes agents can apply during and after calls.
You can create action buttons, create post-call dispositions, move contacted people between Smart Lists, and receive webhooks when an action runs.
The loop has three parts: your backend configures outcomes, Sailor shows them to agents, and Sailor sends events back when actions run.
What You Can Build
Create and manage the labels agents see during calls and after calls.
Add a contacted person to a Smart List, or remove them from every list or selected lists.
Receive the call, outcome, scope, and destination details when an action runs.
Use the exact request fields, response fields, validation rules, and webhook schemas.
Base URL
Supported Endpoints
Build against the documented endpoints in these guides and the API Reference. Undocumented paths can change without notice.
How The Loop Works
Configure outcomes
Create action outcomes for in-call controls and disposition outcomes for the required post-call step.
Agents apply outcomes
Sailor shows those outcomes inside the phone-system workflow for the active workspace.
Choose Your Path
Create an action, receive a webhook, add a disposition, and verify the result.
Learn the difference between actions, dispositions, destinations, and webhook events.
Build a webhook endpoint that accepts Sailor events without blocking agents.
Use the reference when you need the precise contract for an endpoint or payload.