> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Authorize an outbound INVITE from a registered endpoint

> Internal jambonz auth-hook fired before an outbound INVITE from a registered softphone leaves the edge. It validates that the credential's organization has outbound calling enabled, that the endpoint is not in DND, that the caller-ID being presented is owned by the org, that the destination is not a blocked country, and that the concurrent-call cap has room — returning the approved From number on success or a controlled 403 with a reason on rejection. Signed with the jambonz webhook HMAC and not intended for direct client use. Approval only — the call still exits via the Devotel softswitch (invariant #45). Fails CLOSED (403) on a transient dependency fault rather than leaking a 503 that drops the call.



## OpenAPI

````yaml /openapi.yaml post /api/v1/jambonz/dial-confirm
openapi: 3.1.0
info:
  title: Devotel CPaaS API
  description: Orbit by Devotel — Communications Platform as a Service API
  version: 1.0.0
  contact:
    name: Devotel
    url: https://devotel.io
    email: support@devotel.io
  license:
    name: Proprietary
servers:
  - url: https://api.orbit.devotel.io
    description: Production
security:
  - Bearer: []
  - ApiKey: []
tags:
  - name: Messages
    description: >-
      Send and manage messages across all channels (SMS, WhatsApp, RCS, Email,
      Viber, etc.)
  - name: Fax
    description: >-
      List and track fax (MMS/T.38) transmissions on Telnyx-backed fax numbers
      (sending flows through the Messaging API)
  - name: Agents
    description: AI agent creation, configuration, and execution
  - name: Voice
    description: Voice calls, IVR, conferencing, and SIP trunking
  - name: OnCall
    description: On-call rotations and escalation policy planning for incident alerting
  - name: Webhooks
    description: Webhook endpoint management and delivery logs
  - name: Numbers
    description: Phone number search, provisioning, and configuration
  - name: Brand Identity
    description: >-
      Unified cross-channel brand trust posture (10DLC, toll-free, WhatsApp,
      RCS, branded calling, number KYC)
  - name: Contacts
    description: Contact management, segmentation, and lifecycle tracking
  - name: Campaigns
    description: Marketing campaign orchestration and analytics
  - name: Flows
    description: Automation flow builder and execution engine
  - name: Templates
    description: Message template management and approval workflows
  - name: Settings
    description: Organization, channel, and user preference settings
  - name: Verify
    description: OTP generation and verification across channels
  - name: Push
    description: Push notification delivery via FCM and APNs
  - name: Integrations
    description: Third-party service connections and OAuth management
  - name: CDP
    description: >-
      Customer Data Platform — activation surface (CRM object sync, streaming
      destinations, ad-audience activation)
  - name: Files
    description: >-
      Server-to-server media upload, listing, retrieval, and deletion
      (signed-URL backed)
  - name: Commerce
    description: >-
      Omnichannel conversational-commerce — persistent cart + checkout state
      machine, channel-agnostic hosted pay-by-link, native WhatsApp checkout,
      and AP2-style agent payment mandates.
  - name: Sync
    description: >-
      Real-time shared-state primitive (Twilio Sync parity) — Documents, Maps,
      Lists, and ephemeral Streams, with change events relayed over the
      /api/v1/ws/sync WebSocket gateway
  - name: Risk
    description: >-
      Unified cross-channel Trust & Fraud risk scoring — fuses SMS-pumping,
      URL-reputation, Verify Fraud Guard, and Voice Biometrics signals into one
      composite verdict queryable before a send or a call.
  - name: Orby
    description: >-
      In-dashboard Orby operator assistant: streamed assistant turns,
      conversation threads, product knowledge-base search, and the tool-action
      approval gate. Available to signed-in operators only (dashboard session
      auth — API-key requests are rejected).
paths:
  /api/v1/jambonz/dial-confirm:
    post:
      summary: Authorize an outbound INVITE from a registered endpoint
      description: >-
        Internal jambonz auth-hook fired before an outbound INVITE from a
        registered softphone leaves the edge. It validates that the credential's
        organization has outbound calling enabled, that the endpoint is not in
        DND, that the caller-ID being presented is owned by the org, that the
        destination is not a blocked country, and that the concurrent-call cap
        has room — returning the approved From number on success or a controlled
        403 with a reason on rejection. Signed with the jambonz webhook HMAC and
        not intended for direct client use. Approval only — the call still exits
        via the Devotel softswitch (invariant #45). Fails CLOSED (403) on a
        transient dependency fault rather than leaking a 503 that drops the
        call.
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                call_sid:
                  type: string
                  description: jambonz call SID of the outbound leg.
                username:
                  type: string
                  description: SIP credential username originating the call.
                from:
                  type: string
                  description: Caller-ID the endpoint is presenting.
                to:
                  type: string
                  description: Dialed destination number.
                source_ip:
                  type: string
                  description: Source IP of the calling endpoint.
            example:
              call_sid: 5f9c3b1a-2d4e-4f6a-8b0c-1e2d3f4a5b6c
              username: alice-desk
              from: '+14155550100'
              to: '+14155550199'
      responses:
        '200':
          description: >-
            Authorization verdict. `status: ok` approves the INVITE and echoes
            the approved From number; a rejected call returns HTTP 403 with
            `status: fail` and a reason.
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    description: '`ok` when the INVITE is approved, `fail` otherwise.'
                  approved_from:
                    type: string
                    description: The caller-ID approved for the outbound leg.
                  organization_id:
                    type: string
                    description: Owning organization of the SIP credential.
              example:
                status: ok
                approved_from: '+14155550100'
                organization_id: org_9f3c2a1b
components:
  securitySchemes:
    Bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Dashboard JWT token from Clerk
    ApiKey:
      type: apiKey
      name: X-API-Key
      in: header
      description: Server-to-server API key (dv_live_sk_*)

````