> ## 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. # File a GDPR right-to-erasure request > Open a GDPR Article-17 right-to-erasure request for a contact. Unlike the immediate `DELETE /:id/gdpr/delete` cascade, this starts a cancellable cooling-off period (per-tenant, default 7 days) after which the webhook-worker scheduler hard-deletes the contact and writes a per-resource audit chain. Returns 202 with the created request (including `cooling_off_ends_at`), 404 if the contact does not exist, and 409 ERASURE_COOLING_OFF_ACTIVE when a request is already pending or executing. ## OpenAPI ````yaml /openapi.yaml post /api/v1/contacts/{id}/gdpr/erasure-request 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}/gdpr/erasure-request: post: tags: - Contacts summary: File a GDPR right-to-erasure request description: >- Open a GDPR Article-17 right-to-erasure request for a contact. Unlike the immediate `DELETE /:id/gdpr/delete` cascade, this starts a cancellable cooling-off period (per-tenant, default 7 days) after which the webhook-worker scheduler hard-deletes the contact and writes a per-resource audit chain. Returns 202 with the created request (including `cooling_off_ends_at`), 404 if the contact does not exist, and 409 ERASURE_COOLING_OFF_ACTIVE when a request is already pending or executing. parameters: - schema: type: string in: path name: id required: true responses: '202': description: >- The accepted erasure request with its cooling-off window, wrapped in the standard `{ data, meta }` envelope. content: application/json: schema: type: object properties: data: type: object additionalProperties: true properties: id: type: string contact_id: type: string status: type: string cooling_off_ends_at: type: string format: date-time meta: type: object properties: request_id: type: string timestamp: type: string format: date-time example: data: id: erasure_01HZX8ERASE contact_id: contact_01HZX8Y7QJK4M status: pending cooling_off_ends_at: '2026-02-09T12:00:00.000Z' 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_*) ````