Lead intake
Connect a consented enquiry to a bounded qualification workflow and a human follow-up task.
For developers, agencies, startups and technical teams connecting conversations to useful business workflows.
Developer access is reviewed, not an automatically provisioned public API or unrestricted sandbox. The existing workspace API requires authenticated account access and permissions.
Connect a consented enquiry to a bounded qualification workflow and a human follow-up task.
Map approved CRM, booking or support actions, including failed and duplicate delivery.
Build a scoped deployment for a client, with account isolation, provider checks and clear ownership.
The API validates a Supabase bearer session and account permissions. Keep provider keys on the server.
The workspace creates an agent and versions its instructions. Choose supported providers, attach approved knowledge and save required fields.
Confirm entitlement, contact permission, number ownership and provider readiness before an outbound dispatch.
Read call records and available intelligence. A queued response is not proof of audio, completion or a successful business action.
GET /api/v1/auth/me Authorization: Bearer <your authenticated session>
Run this against your authorized backend host from a trusted client. Never share a bearer token or paste a provider key into a public page. This example does not execute a request.
Endpoint reference · Agent setup guide
Attach reviewed business knowledge and map permitted runtime values. Validate missing inputs; a variable name is not authorization to read a customer's records.
Provider callback authentication belongs on the backend. Agree webhook destinations, allowed fields and retry behavior; verify signatures, deduplicate deliveries and handle out-of-order events before a business action. Review delivery failures in the workspace rather than treating a saved URL as a connected system.
No downloadable Dialit SDK, anonymous API key issuance or public call sandbox is currently offered here. Apply below for an integration review.
POST /api/v1/agents
Authorization: Bearer <your authenticated session>
Content-Type: application/json
{
"name": "Viewing-request agent",
"system_prompt": "Capture a viewing request. A person must confirm availability."
}This is an authenticated configuration example, not an executable sandbox. Account permissions and entitlements apply. Creating an agent does not initiate a call or establish a working telephony route.
GET /api/v1/agents reads your accessible agents.GET /api/v1/calls reads accessible call records.GET /api/v1/calls/{call_id}/intelligence reads available conversation and analysis data.POST /api/v1/calls/dispatch requests a permitted outbound call; it is a side effect, not a read-only test.Use the API reference for dispatch idempotency and failure handling. Treat provider and account availability as explicit states; never interpret a missing transcript as a successful call.