---
title: "POST /v2/admin/deep-link-keys/{id}/revoke"
method: POST
path: "/v2/admin/deep-link-keys/{id}/revoke"
tags: ["Admin"]
---

# POST /v2/admin/deep-link-keys/{id}/revoke

`POST /v2/admin/deep-link-keys/{id}/revoke`

## Request

- Base URL: `https://api.peer.xyz`
- URL: `https://api.peer.xyz/v2/admin/deep-link-keys/{id}/revoke`
- Auth: HTTP bearer

Requires a support Admin's Privy access token as a Bearer token; API keys are not accepted. Each change posts to #humans-cybersec. Mints and escalations are refused when that alert cannot be sent; revocations and narrower grants are saved and answer alertSent: false.

## Path parameters

- `id` integer, required

## Response `200`

Deep-link key revoked

- object
  - `success` boolean, required
  - `message` string, required
  - `responseObject` object
    - `id` integer, required
    - `name` string, required
    - `keyPrefix` string, required
    - `isActive` false, required
    - `revokedAt` string, date-time, required
    - `alertSent` boolean, required: False when a reduction was saved but its #humans-cybersec alert could not be sent
  - `statusCode` number, required
  - `errorCode` string

## Other responses

- `401`: Not signed in as support staff
- `403`: Not a support Admin
- `503`: Staff check or alert unavailable, so nothing changed; or the change is saved but the key cache was not cleared, so retry

## Changes

- **2026-11-02** `ef91955315e2`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/peer/apis/swagger-api/changes/v2/admin/deep-link-keys/:id/revoke/post.md)

---

[API](https://skmtc.dev/peer/apis/swagger-api.md) - [All operations](https://skmtc.dev/peer/apis/swagger-api/llms.txt) - [OpenAPI document](https://skmtc.dev/peer/apis/swagger-api/revisions/ef91955315e2?raw)