Skip to main content
POST
Rotate signing key

Authorizations

Authorization
string
header
required

Send Authorization: Bearer <credential> to https://customer-api.mountthor.com. People use the session that mthr login stores (a token starting mt_session_, valid for up to 12 hours). Automation uses a service-account credential (starting mt_sa_v1_, valid for 90 days) from Create credential. Each operation names the permission it needs. Service accounts hold permissions through custom roles, and some operations refuse them; those operations say so.

Path Parameters

name
string
required

The subscription's name.

Body

application/json

The rotation to make.

requestId
string
required

A UUID you generate for this rotation. Use it again only to retry the same rotation.

gracePeriod
string

Optional. How long the previous key keeps signing beside the new one, as a duration such as "3600s". 24 hours when omitted, and at most 24 hours. "0s" retires every earlier key at once.

Pattern: ^-?(?:0|[1-9][0-9]{0,11})(?:\.[0-9]{1,9})?s$

Response

OK

The new signing key.

hmacKey
string<bytes>

The new signing key, base64-encoded. Treat it as a secret.

previousKeyExpireAt
string<date-time>

When the previous key stops signing deliveries. Until then each delivery carries a signature from both keys. It is the rotation time when gracePeriod was "0s". Stop trusting the previous key after it.