Developers

Send data to Sissel without guessing.

Each integration spells out what it reads, what it can send, and which permissions it needs. Connecting a source never turns on live conversion delivery.

Events API

Inbound · Beta

Send outcomes from a trusted server. Use a workspace-scoped token with events:write and a stable deduplication key. Outcome means an event received from CRM, API, or Zapier; attribution happens separately.

Contract summarytext
POST /api/v1/events
Authorization: Bearer <workspace token>
Idempotency-Key: <stable source key>

Zapier

Inbound · Beta

Use the Sissel Zapier integration with a workspace token. Trigger and action payloads preserve the source and deduplication identity; reconnect the account if its token is revoked.

Contract summarytext
SISSEL_API_BASE_URL=https://app.sissel.app
Authentication: workspace token

Vigdis CRM

Inbound · Beta

Sissel verifies a read-only API key, reads entity types, fields and stages, then asks you to map identity fields and outcome meanings. Sync is cursor-based and starts with new changes.

Contract summarytext
Required: read-only API key for vigdis.app
Then: verify → map fields/stages → receive a test outcome

Meta Ads

Read + conversion delivery · Beta

OAuth reads account hierarchy and spend. Conversion delivery is configured per outcome as Not sent, Test, or Live. Live requires a fresh named reconciliation baseline, at least 98% parity, and no unexplained differences.

Contract summarytext
Required: owner/admin + ad account + dataset
Path: connect → map → test → reconcile → review → Live

Google Ads

Read + conversion delivery · Beta

OAuth reads accessible accounts, hierarchy and spend. Each active outcome requires its conversion action ID. Tests use validation before Live; the same reconciliation gate applies.

Contract summarytext
Required: owner/admin + operating account + conversion action IDs
Test: validateOnly before production delivery

TikTok Ads

Read + eligible CRM delivery · Private beta

OAuth reads one advertiser, campaign hierarchy, daily spend, and available website pixels or CRM Event Sets. The same connected account delivers eligible outcomes using the selected default or site route. Website delivery uses the selected pixel and consented customer or browser identifiers, including ttclid. CRM delivery uses a native TikTok lead ID or email/phone; ttclid is not a CRM match key.

Contract summarytext
Required: owner/admin + advertiser + CRM Event Management access
Path: connect → choose Event Set routes → validate access → reconcile → review → Live

These pages describe the checked-in beta implementation. Request and response schemas may change before general availability; production use requires an agreed change process.