> ## 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 preferences via a signed token

> Public, no-auth endpoint backing the hosted preference center. Given the signed token from a preference link, it returns the contact's current channel and topic subscriptions, allowed channels, and recent consent history so the hosted page can render. Email and phone are masked; an expired or invalid token returns 401.



## OpenAPI

````yaml /openapi.yaml get /api/v1/compliance/preferences/{token}
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/compliance/preferences/{token}:
    get:
      tags:
        - Compliance
      summary: Get a contact's preferences via a signed token
      description: >-
        Public, no-auth endpoint backing the hosted preference center. Given the
        signed token from a preference link, it returns the contact's current
        channel and topic subscriptions, allowed channels, and recent consent
        history so the hosted page can render. Email and phone are masked; an
        expired or invalid token returns 401.
      parameters:
        - schema:
            type: string
          in: path
          name: token
          required: true
          description: The signed preference token from the preference-center link.
      responses:
        '200':
          description: The contact's current preferences for the hosted page.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      contactId:
                        type: string
                      displayName:
                        type: string
                        nullable: true
                      email:
                        type: string
                        nullable: true
                        description: Masked email address.
                      phone:
                        type: string
                        nullable: true
                        description: Masked phone number.
                      channelPreferences:
                        type: object
                        additionalProperties:
                          type: string
                      frequencyPreference:
                        type: string
                      channels:
                        type: array
                        items:
                          type: string
                      topics:
                        type: array
                        items:
                          type: object
                      topicPreferences:
                        type: object
                        additionalProperties:
                          type: string
                  meta:
                    $ref: '#/components/schemas/ResponseMeta'
              example:
                data:
                  contactId: contact_1a2b3c4d5e6f
                  displayName: Jane D.
                  email: j***@example.com
                  phone: +1415*****23
                  channelPreferences:
                    sms: opted_in
                    email: opted_out
                  frequencyPreference: weekly
                  channels:
                    - sms
                    - email
                  topics:
                    - id: product_updates
                      name: Product updates
                      defaultOptIn: false
                  topicPreferences:
                    product_updates: opted_in
                meta:
                  request_id: req_1a2b3c4d5e6f
                  timestamp: '2026-08-07T12:00:00.000Z'
components:
  schemas:
    ResponseMeta:
      type: object
      required:
        - request_id
        - timestamp
      additionalProperties: false
      properties:
        request_id:
          type: string
          description: Unique request identifier (also returned as X-Request-Id header)
        timestamp:
          type: string
          format: date-time
        docs_url:
          type: string
          format: uri
          nullable: true
  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_*)

````