> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pilotstatus.com.br/llms.txt
> Use this file to discover all available pages before exploring further.

# Purge number

> PERMANENTLY destroys the number, immediately — IRREVERSIBLE, there is no restore afterwards. Erases the number and everything under it (message history, chats, templates, webhooks scoped to it, its API keys) and deregisters a Meta number at Meta. Accepts a number already deleted with `DELETE /v1/numbers/{id}` (the usual flow: delete, then purge) or an active one. Use it when the SAME phone has to be created again right away. It saves nothing on the bill compared to `DELETE`. Use a TENANT-scoped key: a key bound to the deleted number stops authenticating once the number is deleted. With an OAuth/MCP token, only the workspace OWNER may purge (`403 PERMISSION_DENIED` otherwise).



## OpenAPI

````yaml openapi.json DELETE /v1/numbers/{id}/purge
openapi: 3.1.0
info:
  title: Pilot Status API
  version: 1.0.0
  license:
    name: Pilot Status Terms of Service
    url: https://pilotstatus.com.br/terms
  description: >-
    Public REST API for Pilot Status. Authenticate with the `x-api-key: ps_...`
    header (or `x-api-key-id`). Base URL: https://pilotstatus.com.br
servers:
  - url: https://pilotstatus.com.br
security:
  - apiKey: []
  - apiKeyId: []
paths:
  /v1/numbers/{id}/purge:
    delete:
      tags:
        - Numbers
      summary: Purge number (permanent delete)
      description: >-
        PERMANENTLY destroys the number, immediately — IRREVERSIBLE, there is no
        restore afterwards. Erases the number and everything under it (message
        history, chats, templates, webhooks scoped to it, its API keys) and
        deregisters a Meta number at Meta. Accepts a number already deleted with
        `DELETE /v1/numbers/{id}` (the usual flow: delete, then purge) or an
        active one. Use it when the SAME phone has to be created again right
        away. It saves nothing on the bill compared to `DELETE`. Use a
        TENANT-scoped key: a key bound to the deleted number stops
        authenticating once the number is deleted. With an OAuth/MCP token, only
        the workspace OWNER may purge (`403 PERMISSION_DENIED` otherwise).
      operationId: delete_numbers_id_purge
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          example: num_01HZX...
          description: Id of the number to destroy (active or already deleted).
      responses:
        '200':
          description: Number purged
          content:
            application/json:
              example:
                ok: true
        '401':
          description: Missing or invalid `x-api-key` / `x-api-key-id` header
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                  code:
                    type: string
              example:
                error: Unauthorized
        '403':
          description: OAuth/MCP token of a user who is not the workspace OWNER
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                  code:
                    type: string
              example:
                error: >-
                  Your workspace role does not allow this action
                  (numbers:purge).
                code: PERMISSION_DENIED
        '404':
          description: Unknown id, or already purged
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                  code:
                    type: string
              example:
                error: Not found
        '429':
          description: Rate limit exceeded
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                  code:
                    type: string
              example:
                error: Too many requests
components:
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key
      description: Your ps_ API key
    apiKeyId:
      type: apiKey
      in: header
      name: x-api-key-id
      description: API key id (alternative to x-api-key)

````