---
title: "Rotate Ro Key"
method: POST
path: "/readonly-keys/{key_id}/rotate"
---

# Rotate Ro Key

`POST /readonly-keys/{key_id}/rotate`

## Request

- Base URL: `https://api.tickwire.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.tickwire.io/readonly-keys/{key_id}/rotate`
- Auth: none declared

Issue a new value for a read-only key (same id, scope and accounts);
the old value stops working. The new ``key`` is shown once
(``key_notice``). With ``Idempotency-Key`` a replay rotates nothing and
answers ``key: null`` with a ``key_notice`` saying it was already shown;
the same ``Idempotency-Key`` on another key's rotate answers ``409
idempotency_conflict``.

## Path parameters

- `key_id` string, required

## Headers

- `Idempotency-Key` string, nullable
- `X-API-Key` string, nullable
- `Authorization` string, nullable
- `auth-token` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/tickwire/apis/tickwire-control-plane.md) · [All operations](https://skmtc.dev/tickwire/apis/tickwire-control-plane/llms.txt) · [OpenAPI document](https://skmtc.dev/tickwire/apis/tickwire-control-plane/revisions/a4d1386fa23e?raw)
