> ## Documentation Index > Fetch the complete documentation index at: https://docs.escrybe.com.br/llms.txt > Use this file to discover all available pages before exploring further. # Cancel a WhatsApp message > Provide either `outbox_id` or `message_id`. Messages can be cancelled while awaiting payment or queued (outbox status pending/processing, or message status 0/2). Credit refunds are issued only when an admin cancels a failed message paid with escrybe_credits. ## OpenAPI ````yaml /openapi/escrybe.en.yaml post /api/whatsapp/v1/cancel openapi: 3.1.0 info: title: Escrybe API version: 1.0.0 description: > REST API for the Escrybe platform — send physical letters, registered letters, telegrams and e-Carta through Brazilian Correios, dispatch legally registered e-mails, and send WhatsApp messages with certified timestamps. ## Authentication Every account has a personal **`securityToken`** (find it in the panel under *Account → API*). Three products use it differently: | Product | Scheme | How | |---------|--------|-----| | Letters / Telegram / e-Carta, Registered E-mail, Receipts | API token | Send `userSecurityToken` as a query/body parameter, or `securityToken` as a header | | WhatsApp | HTTP Basic | `Authorization: Basic base64(email:securityToken)` | > The letter and e-mail **read** routes (`get`, `balance`, `download`, > `delete`) take the token as the first URL **path** segment — e.g. > `/api/v2/get/{securityToken}/{job_id}`. ## Response envelopes Most endpoints reply with the standard envelope `{"status": , "status_message": "...", "data": ...}` — this covers Letters/Telegram, Registered E-mail, and the WhatsApp message and sender endpoints. The WhatsApp **template** endpoints (and template sync) use `{"code": , "status": "success|error", "message": "...", "data": ..., "request_id": "..."}`; the logo endpoint uses the same shape without `request_id`. See the schema of each endpoint. A request that is accepted returns an HTTP `200` with a success payload; validation problems return `400`, bad credentials `401`, and forbidden access `403`. Unsupported HTTP methods return `405`, repeated failed authentication attempts return `429`, and the letter and e-mail endpoints return `503` during maintenance windows. contact: name: Escrybe Support url: https://escrybe.com.br servers: - url: https://app.escrybe.com.br description: Production - url: https://homolog.escrybe.com.br description: Staging security: - securityTokenQuery: [] tags: - name: Letters & Telegram description: Create and manage letter, telegram and e-Carta orders (Correios). - name: Account & Favorites description: Account balance, saved contacts and sender logo. - name: Registered E-mail description: Send and track legally registered e-mails. - name: WhatsApp Messages description: Send WhatsApp messages and download certified-timestamp attestations. - name: WhatsApp Senders description: Manage WhatsApp Business numbers (senders). - name: WhatsApp Templates description: Create, sync and manage WhatsApp message templates. - name: Receipts description: Download legal receipts for any order. paths: /api/whatsapp/v1/cancel: post: tags: - WhatsApp Messages summary: Cancel a WhatsApp message description: > Provide either `outbox_id` or `message_id`. Messages can be cancelled while awaiting payment or queued (outbox status pending/processing, or message status 0/2). Credit refunds are issued only when an admin cancels a failed message paid with escrybe_credits. operationId: cancelWhatsappMessage requestBody: required: true content: application/json: schema: type: object properties: outbox_id: type: integer message_id: type: integer responses: '200': description: Cancelled content: application/json: schema: allOf: - $ref: '#/components/schemas/WaMessagesEnvelope' - properties: data: type: object properties: success: type: boolean message_id: type: integer outbox_id: type: integer status: type: string example: cancelled reimbursed: type: boolean reimbursed_amount: type: number '400': $ref: '#/components/responses/WaMsgBadRequest' '401': $ref: '#/components/responses/WaMsgUnauthorized' '403': $ref: '#/components/responses/WaMsgForbidden' '404': $ref: '#/components/responses/WaMsgNotFound' '500': $ref: '#/components/responses/WaMsgServerError' security: - basicAuth: [] components: schemas: WaMessagesEnvelope: type: object description: > Standard envelope used by the WhatsApp message and sender endpoints (same shape as the letters and e-mail envelopes). properties: status: type: integer example: 200 status_message: type: string data: oneOf: - type: object - type: string - type: 'null' responses: WaMsgBadRequest: description: Invalid request content: application/json: schema: $ref: '#/components/schemas/WaMessagesEnvelope' example: status: 400 status_message: Campos obrigatórios não preenchidos data: null WaMsgUnauthorized: description: Unauthorized — invalid credentials content: application/json: schema: $ref: '#/components/schemas/WaMessagesEnvelope' example: status: 401 status_message: Unauthorized - invalid credentials data: null WaMsgForbidden: description: Access denied content: application/json: schema: $ref: '#/components/schemas/WaMessagesEnvelope' WaMsgNotFound: description: Not found content: application/json: schema: $ref: '#/components/schemas/WaMessagesEnvelope' WaMsgServerError: description: Internal error content: application/json: schema: $ref: '#/components/schemas/WaMessagesEnvelope' securitySchemes: securityTokenQuery: type: apiKey in: query name: userSecurityToken description: >- Your account security token, sent as the `userSecurityToken` query or form parameter. basicAuth: type: http scheme: basic description: >- HTTP Basic where username is your account e-mail and password is your security token. ````