> ## 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. # Resolve the verb sequence for an inbound call > Internal jambonz call-hook that every inbound INVITE fetches its verb sequence from. It resolves the dialed number (DNIS) to the owning organization and inbound route, applies the org/number blocking, schedule, and DND gates, then builds the jambonz verbs for that route — a greeting, an IVR menu, an ACD queue, a forward-to-number, or voicemail. Signed with the jambonz webhook HMAC and not intended for direct client use. Bounded by a handler deadline and fails OPEN with safe-default verbs (HTTP 200) so a transient dependency wobble plays a polite greeting rather than dropping the live caller. ## OpenAPI ````yaml /openapi.yaml post /api/v1/jambonz/lookup 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/lookup: post: summary: Resolve the verb sequence for an inbound call description: >- Internal jambonz call-hook that every inbound INVITE fetches its verb sequence from. It resolves the dialed number (DNIS) to the owning organization and inbound route, applies the org/number blocking, schedule, and DND gates, then builds the jambonz verbs for that route — a greeting, an IVR menu, an ACD queue, a forward-to-number, or voicemail. Signed with the jambonz webhook HMAC and not intended for direct client use. Bounded by a handler deadline and fails OPEN with safe-default verbs (HTTP 200) so a transient dependency wobble plays a polite greeting rather than dropping the live caller. requestBody: content: application/json: schema: type: object properties: call_sid: type: string description: jambonz call SID of the inbound leg. to: type: string description: Dialed number (DNIS) in E.164. from: type: string description: Caller ANI. direction: type: string description: Call direction as reported by jambonz. originating_sip_trunk_name: type: string description: Name of the carrier / trunk the call arrived on. example: call_sid: 5f9c3b1a-2d4e-4f6a-8b0c-1e2d3f4a5b6c to: '+14155550100' from: '+14155550132' direction: inbound responses: '200': description: >- The jambonz verb array to run for the inbound call (greeting, IVR, enqueue, dial, or voicemail). On any internal error a safe-default verb sequence is returned so the caller is never dropped. content: application/json: schema: type: array description: jambonz verb array for the inbound call. items: type: object properties: verb: type: string example: - verb: say text: Thanks for calling Acme. Please hold while we connect you. - verb: enqueue name: support 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_*) ````