---
title: "Revoke a screen's signing key"
method: POST
path: "/v1/proof/keys/{keyId}/revoke"
tags: ["proof"]
---

# Revoke a screen's signing key

`POST /v1/proof/keys/{keyId}/revoke`

## Request

- Base URL: `https://api.brixsignage.com`
- URL: `https://api.brixsignage.com/v1/proof/keys/{keyId}/revoke`
- Auth: HTTP bearer

Marks one of a screen's signing keys as bad. Send the `screenId` in the body. From that time, plays signed with the key show as revoked, and the next new key from the screen registers as a replacement. Calling it again has no further effect. The change is recorded in the activity log.

## Path parameters

- `keyId` string, required

## Response `2XX`

Success. Body is `{ data: … }` unless the endpoint serves bytes. The shape of `data` is not yet modelled for this operation.

## Other responses

- `4XX`: Client error. 404 rather than 403 for another tenant's resource, so account existence is not leaked.
- `5XX`: Server error. The body carries a `requestId` to quote to support.

---

[API](https://skmtc.dev/brixsignage/apis/brix-api.md) · [All operations](https://skmtc.dev/brixsignage/apis/brix-api/llms.txt) · [OpenAPI document](https://skmtc.dev/brixsignage/apis/brix-api/revisions/02fd3665dc7d?raw)