Sign in
instance

Rotate the root change-token key.

Changed on

Mints a new root token key, retires the old one, and derives every subsequent change token under it.

WHAT IT DOES NOT TOUCH: no snapshot's content, no revision number, and no pinned input revision moves. It cannot - a change token is never stored, it is derived at read from the live key over the snapshot's delivery manifest, so there is no cache to invalidate and nothing to resume after a crash.

Every outstanding delivery cursor mismatches once and every consumer performs one full fetch. This is NOT a restart wave.

It rides rotate-dek: the capability set is closed and names four rotation atoms for five rotation verbs, and the root token key is a tier-3 key alongside the DEKs.

post/api/v1/instance/rotate-token-key

Request

  • Base URL: / (relative, and the document was published on a file host, not at the API’s origin)
  • URL: /api/v1/instance/rotate-token-key
  • Auth: HTTP bearer

Response

The rotation.

token_key_versioninteger required

The new root token key version. Operator bookkeeping only - the change token's public contract carries the SCHEME version, never the key version, because a consumer that could tell key versions apart could tell a rotation from a content change.

Changes

  • 54b2780eec85Revision changes
    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

    • info

      added the optional property / to the response with the status

  • f84a1cd8a05aRevision changes
    • warning

      added the new payload_too_large enum value to the / response property for the response status

    • warning

      added the new payload_too_large enum value to the / response property for the response status

    • warning

      added the new payload_too_large enum value to the / response property for the response status

    • warning

      added the new payload_too_large enum value to the / response property for the response status

    • warning

      added the new payload_too_large enum value to the / response property for the response status

    • warning

      added the new unprocessable enum value to the / response property for the response status

    • warning

      added the new unprocessable enum value to the / response property for the response status

    • warning

      added the new unprocessable enum value to the / response property for the response status

    • warning

      added the new unprocessable enum value to the / response property for the response status

    • warning

      added the new unprocessable enum value to the / response property for the response status