Skip to content
Kubali

For developers

API first. Everything the dashboard does, you can do. The dashboard, the SMS flows and the hosted pages are clients of the same public API. Add consent to your software without building a consent screen of your own.

curl https://api.kubali.example/v1/consents/check \
  -H "Authorization: Bearer kb_sandbox_…" \
  -d phone=+2547XXXXXXXX -d purpose=photos

{ "allowed": false, "state": "refused" }

Examples

Four calls cover most integrations.

Call this before you message someone or publish their image. It answers in one line.

curl "$API/v1/consents/check?phone=%2B2547XXXXXXXX&purpose=marketing_sms" \
  -H "Authorization: Bearer $KUBALI_KEY"

{"allowed": false, "state": "refused", "since": "2026-11-22T06:14:00Z"}

Built to be relied on

Conventions you would expect.

JSON over HTTPS

International phone numbers, cursor pagination and one error shape, with the consent rule that blocked a call named in `rule`.

Keys with scopes

Per organisation, scoped to read, request, record and more, in sandbox and live modes.

Idempotency on every POST

Retry safely. A repeated call never sends a second message.

Rules enforced for everyone

No reply is never a yes. One answer per purpose. Withdrawal works on every channel. The record cannot be edited.

Webhooks and SDKs

Signed events when someone grants, refuses or withdraws, and SDKs for Go, Python, JavaScript and PHP.

Coming

Consent-checked sends

Send through Kubali and recipients without a matching yes are dropped before anything leaves.