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

# Remove an API token

> DELETE /console/token/{key}/

Permanently revokes a Management API key. Like [creating a token](/api-reference/management-api/tokens/create), this lives on the **regular** Scanova API host (`qcg-api.scanova.io`) and is authenticated with your normal dashboard OAuth access token — not the key you're deleting.

## Request

```
DELETE https://qcg-api.scanova.io/console/token/{key}/
Authorization: Bearer <your_oauth_access_token>
```

<ParamField path="key" type="string" required>
  The full key value returned when the token was created (not a numeric ID).
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X DELETE "https://qcg-api.scanova.io/console/token/401f7ac837da42b97f613d789819ff93537bee6a/" \
    -H "Authorization: Bearer <your_oauth_access_token>"
  ```
</RequestExample>

<ResponseExample>
  ```text 204 No Content theme={null}
  ```
</ResponseExample>

## Behavior

* A successful removal returns `204 No Content` with an empty body.
* Once deleted, the key stops authenticating on the data host immediately — any in-flight or subsequent requests using it get `401`.
* You can only delete a key you own (or, for a shared user, a key that shared user created).

<Note>
  Deletion also re-checks plan quota using an `environment` value, defaulting to `sandbox` if you don't pass one — the same rule described on the [create token](/api-reference/management-api/tokens/create#listing-existing-tokens) page. This rarely matters in practice since plans that grant Management API access typically grant it across all environments, but pass `?environment=live` explicitly if you hit an unexpected `401` deleting a live-environment key.
</Note>

<Warning>
  There's no "disable" or "pause" state — removal is immediate and permanent. If you just need to stop a key from being used temporarily, don't delete it; create a new key and stop using the old one, or coordinate with the integration consuming it before deleting.
</Warning>

## Related

* [Management API overview](/api-reference/management-api/overview) — the two-host auth architecture this endpoint is part of.
* [Create an API token](/api-reference/management-api/tokens/create) — generate a replacement key, and see the listing/quota rules this endpoint shares.
* [Usage statistics](/api-reference/management-api/tokens/usage-stats) — check a key's usage before deciding whether to remove it.


## OpenAPI

````yaml api-reference/openapi/management-api.json DELETE /console/token/{key}/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    management.scanova.io (QR codes, folders, tags, leads, forms, analytics,
    plans, shared users & roles), plus the token-creation and usage-stats
    endpoints used to authenticate against it. Every path and request/response
    shape below was verified live against a real API key and the actual running
    backend (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://management.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /console/token/{key}/:
    delete:
      summary: Remove an API token
      operationId: removeApiToken
      parameters:
        - name: key
          in: path
          required: true
          schema:
            type: string
      responses:
        '204':
          description: Token removed
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Send your Management API key as the raw value of the Authorization
        header — no "Bearer " or "Token " prefix, and no other characters.
        Example: `Authorization: 401f7ac837da42b97f613d789819ff93537bee6a`. A
        header containing more than one space-separated part is rejected
        outright. Requests also require the request's Host header to be the
        management API host (e.g. management.scanova.io) — the same key sent to
        the regular API host will not authenticate.

````