Skip to main content
POST
Rotate the signing secret

Authorizations

Authorization
string
header
required

Same flow; ledger:write is required for any mutation.

Headers

Idempotency-Key
string

Required on writes. Stable identifier you choose. The same key always returns the same transaction, forever. Can also be supplied as idempotency_key in the request body. Header wins.

Allowed character set: A-Z, a-z, 0-9, _, :, ., -. Max 255 bytes. Replays of an accepted key return the original response with header Idempotent-Replayed: true so callers can tell a replay from a freshly-committed result.

Required string length: 1 - 255
Pattern: ^[A-Za-z0-9_:.\-]+$
Example:

"pi_acme_1234_capture"

Path Parameters

id
string<uuid>
required

Response

Rotated. Body includes one-time signing_secret.

object
enum<string>
required

Discriminator naming the shape of this resource (e.g. account, transaction).

Available options:
webhook_endpoint
Example:

"account"

id
string<uuid>
required
signing_secret
string
required

New plaintext signing secret. Shown only on this response.

previous_secret_expires_at
string<date-time>
required

UTC timestamp 24h in the future. The previous secret continues to verify inbound signatures until then.