> ## 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. # Get a contact's per-channel reachability state > Return a per-channel snapshot for a contact used by the Inbox composer and Customer 360 — SMS carrier and opt-out state, the WhatsApp 24-hour session window (open or closed plus its expiry) and call-permission grant, voice reachability with the last call outcome and total talk time, and email reachability plus suppression and last open/click/bounce timestamps. Pass an optional `conversation_id` to scope the WhatsApp window probe to the exact thread the operator has open. Results are cached briefly server-side. ## OpenAPI ````yaml /openapi.yaml get /api/v1/contacts/{id}/channel-state 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/contacts/{id}/channel-state: get: tags: - Contacts summary: Get a contact's per-channel reachability state description: >- Return a per-channel snapshot for a contact used by the Inbox composer and Customer 360 — SMS carrier and opt-out state, the WhatsApp 24-hour session window (open or closed plus its expiry) and call-permission grant, voice reachability with the last call outcome and total talk time, and email reachability plus suppression and last open/click/bounce timestamps. Pass an optional `conversation_id` to scope the WhatsApp window probe to the exact thread the operator has open. Results are cached briefly server-side. parameters: - schema: type: string in: path name: id required: true - schema: type: string in: query name: conversation_id required: false description: >- Optional inbox conversation id to scope the WhatsApp 24h window probe to that thread. responses: '200': description: The contact's per-channel reachability and window state. content: application/json: schema: type: object properties: data: type: object additionalProperties: true properties: contact_id: type: string sms: type: object additionalProperties: true whatsapp: type: object additionalProperties: true voice: type: object additionalProperties: true email: type: object additionalProperties: true meta: type: object properties: request_id: type: string timestamp: type: string format: date-time example: data: contact_id: contact_01HZX8Y7QJK4M sms: reachable: true carrier: Verizon mccmnc: '310012' number_type: mobile last_dlr_status: delivered last_dlr_at: '2026-02-01T18:22:00.000Z' opted_out: false whatsapp: reachable: true window_open: true window_expires_at: '2026-02-02T20:00:00.000Z' last_inbound_at: '2026-02-01T20:00:00.000Z' voice: reachable: true number_type: mobile last_call_outcome: completed last_call_at: '2026-01-28T14:05:00.000Z' total_seconds: 372 email: reachable: true suppressed: false last_open_at: '2026-01-30T09:00:00.000Z' last_click_at: null last_bounce_at: null meta: request_id: req_01HZX9MNOPQR timestamp: '2026-02-02T12:00:00.000Z' 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_*) ````