call.started

call.started is the first event of a call, sent when the call starts ringing. Its callSessionState is Ringing (or Dialing when Sautikit is dialling out).

Call events are POSTed to the events_url on the number's routing, which you set with PUT /v1/numbers/{id}/routing. They are not workspace webhooks: you cannot subscribe to them with POST /v1/webhooks.

Payload

The body is flat JSON.

{
  "callSessionState": "Ringing",
  "direction": "Inbound",
  "sessionId": "HD_24d73b4518bc",
  "callerNumber": "+254720000000",
  "clientDialedNumber": "+254720000001",
  "destinationNumber": "+254720000001",
  "callStartTime": "2026-06-27+10:00:00",
  "isActive": "1"
}

Other fields may be present.

Delivery

• Sent once. Each call event is POSTed to your events_url one time and is not retried. Respond within 5 seconds; the response body is ignored.
• Not signed. These posts carry no X-Sautikit-* headers and no signature. Use an events_url with a path that is hard to guess, and confirm anything that matters with GET /v1/calls/{id}, passing the sessionId.
• Read the state from the body. Every call event has the same shape. callSessionState says which one it is.

Example handler

import express from "express";
 
const app = express();
app.use(express.json());
 
app.post("/sautikit/events", (req, res) => {
  res.sendStatus(200); // answer first, then do the work
  const event = req.body;
  if (event.callSessionState === "Ringing") {
    console.log(`Call ${event.sessionId} started: ${event.direction} from ${event.callerNumber}`);
    // create the call in your own records
  }
});

Next steps

• Set events_url with PUT /v1/numbers/{id}/routing.
• Calls concepts
• The full call record is on GET /v1/calls/{id}.