Developers

Build on Sonaline

Sonaline's public APIs: text from your own software through a Bandwidth-compatible Messaging API, see and act on your calls through the Calls API, and have any phone system report its calls and recordings to a workspace.

Guides

• Messaging APISend and receive texts and pictures, list your message history and take delivery callbacks, with the same paths, bodies and callbacks as Bandwidth's Messaging API v2.
• Calls APISee the calls up on your lines and act on them (take over, transfer, park, hold, hang up), place calls from your CRM, follow presence and Do Not Disturb, read the call history and recordings, set lines up, and hear about every call through signed webhooks.
• Phone-system call logReport every call your phone system handles, and upload its recording, so each call is filed under the right person in Sonaline.

Getting credentials

Credentials belong to a workspace, and a workspace admin makes them in the Admin Center at sonaline.app/manage:

• Messaging API: Advanced › API & webhooks, in the API credentials section. Make API credentials gives a client ID and a client secret, and the page shows your account ID. Add an application under API applications for the callback URL your replies and delivery reports go to. The secret is shown once; if it is lost, rotate it.
• Calls API: the same API credentials section. Tick what each credential may do (see calls, move and place calls, presence, recordings, provisioning) when you make it, or later with Scopes. Call webhooks are added in the Call webhooks section beside it; each one's signing secret is shown once.
• Phone-system call log: Phone systems, then the phone system, then Connect under Call log from this phone system. The page shows the two URLs and a token, once.

A workspace connected through a partner makes its own Messaging API credentials the same way; the partner keeps the API's on/off switch.

Questions

Write to hello@sonaline.com.