Admin

Webhooks & API keys

Push leads into SigmaDSA from your website, landing pages or ad platforms — webhook endpoints for creating leads and logging call attempts, secured with an API key.

Webhooks & API Keys lets other systems put leads into SigmaDSA directly. If leads currently arrive by email or WhatsApp and someone retypes them, this is how you stop that.

Webhooks and API Keys page with the endpoints and API key sections highlighted
Webhooks & API Keys: (1) Webhook Endpoints with example payloads, (2) API Keys with Generate API Key.

The endpoints

EndpointWhat it does
Create / Update lead (POST)Creates a lead, or updates the existing one when the phone number already exists — so re-posting doesn't produce duplicates.
Log call attempt (POST)Records a call against a lead. For diallers and call-centre tooling that should write activity back into the CRM.

Each endpoint has an example payload and a field reference on the page, and there's an Integration Guide (PDF) to hand your developer.

API keys

Generate API Key issues the credential the endpoints authenticate with.

The key acts as your tenant. Keep it server-side — a form backend, an integration platform's credential store, your own API. Never put it in front-end JavaScript, where any visitor can read it.

Typical setups

  • Website contact form → your form backend posts to the create-lead endpoint → the lead appears in Leads and is auto-assigned.
  • Landing page or ad platform → connected through Zapier/Make → same endpoint.
  • Dialler → posts call attempts so activity lands on the lead without anyone logging it.

Leads arriving this way behave like any other: auto-assignment, notifications, and the AI Employee's follow-up all apply. Set the lead source in the payload and your source reporting stays honest.

Next steps