> ## 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. # List a contact's consent history > Return the consent-record audit trail for a contact, most recent first, with cursor pagination. Optionally filter by channel. Each row carries the full consent event — state, source, lawful basis, proof URL, and metadata (including who recorded it) — so you can present a defensible GDPR/TCPA history. Identify the contact by `contact_id` or a freeform `identifier`; 404s when the contact does not exist. ## OpenAPI ````yaml /openapi.yaml get /api/v1/compliance/consent/history 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/consent/history: get: tags: - Compliance summary: List a contact's consent history description: >- Return the consent-record audit trail for a contact, most recent first, with cursor pagination. Optionally filter by channel. Each row carries the full consent event — state, source, lawful basis, proof URL, and metadata (including who recorded it) — so you can present a defensible GDPR/TCPA history. Identify the contact by `contact_id` or a freeform `identifier`; 404s when the contact does not exist. parameters: - schema: type: string minLength: 1 maxLength: 64 in: query name: contact_id required: false description: The contact whose history to return (supply this or `identifier`). - schema: type: string minLength: 1 maxLength: 320 in: query name: identifier required: false description: Freeform contact identifier (email / E.164 phone / WhatsApp id). - schema: type: string enum: - email - fax - instagram - line - messenger - push - rcs - sms - viber - voice - whatsapp in: query name: channel required: false description: Optional channel filter. - schema: type: integer minimum: 1 maximum: 100 default: 50 in: query name: limit required: false description: Max rows per page (1–100, default 50). - schema: type: string in: query name: cursor required: false description: >- Opaque forward-pagination cursor from a prior response's `next_cursor`. responses: '200': description: >- Consent history page — `{ contact_id, channel, items, next_cursor }`, most recent first. '404': description: No contact matches the supplied id/identifier. '422': description: >- Either `contact_id` or `identifier` is required, or the query is invalid. 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_*) ````