Build on SmartDivert

The real integration surface today, and the contracts still missing.

This page is intentionally strict. It separates what SmartDivert already exposes from the public integration layer that still needs to be formalized.

Current live routes

Existing backend surfaces

  • /graphql/ Primary application API surface
  • /api/token/ JWT token obtain, refresh, and blacklist endpoints
  • /oidc/ and /openid/ Identity and OIDC provider surfaces
  • /webhooks/twilio/inbound/ Inbound telephony entrypoint
  • /webhooks/twilio/status/ Call status callback
Current telephony flow

Webhook-first, deterministic execution

Inbound calls are accepted through provider webhooks, signature-validated, matched against routing or divert rules, and then advanced through deterministic route execution and fallback logic.

Current AI boundary

Advisory AI, deterministic route execution

The platform direction is to let AI capture intent, suggest the best route, and summarize the call while keeping actual route execution under normal application control.

Already real

What partners can reasonably count on today

  • OIDC-based login and authorization surfaces exist.
  • GraphQL is part of the live application surface.
  • Twilio webhook entrypoints and continuation routes are already wired into the backend.
  • Routing, status callbacks, and post-call handling are first-class backend concerns.
Still missing

What should not be oversold yet

  • A versioned public REST API contract.
  • A formal external webhook event catalog with retry guarantees.
  • Published idempotency and ordering guarantees for partner integrations.
  • An official SDK or self-serve developer quickstart.
Draft external events

First webhook-doc pass

The current first draft for external webhook events lives on a dedicated page and sketches the most natural future event family and payload shape without pretending it is a finalized public contract yet.

Read the webhook event draft

Reliability expectations

What serious buyers will ask

Production integrations need clear statements on retries, duplicate delivery, ordering, and support response. Until those are documented, this page should remain explicit about that gap.

Build direction

Where the partner story should go next

The strongest next step is a real partner-facing docs layer with event schemas, payload examples, auth guidance, and a minimal working integration tutorial.