Create signing secret
Create a signing secret: the shared 256-bit key that encrypts ledger traffic between Moov Money and you. Moov Money wraps each ledger request JWE with this key, and you encrypt your response JWE with it (A256KW + A256GCM). The plaintext secret is returned exactly once, in this response, and is never retrievable again.
From v2026.10.00 the created secret is nested under signingSecret. Before
that the 201 body is the secret object itself.
From v2026.10.00 send an X-Idempotency-Key header. The server echoes
that header on the response. The key is retained for 24 hours after
the create completes. Replaying the same key within that window returns
a 409 with error code idempotency-key-reused and never includes the
plaintext. After the window, the same key creates a new secret and
returns its plaintext exactly once. The earlier secret stays active
until you revoke it. Returns a 409 with error code
idempotency-request-in-progress when a request with this key is still
running. Returns 400 when the header is missing or malformed.
Multiple active secrets are supported at the same time, so you can rotate keys without downtime: create the new secret, deploy it, then revoke the old one.
Auth: API key or bearer token. The providerID in the path must be your
account.
{
"signingSecret": {
"createdOn": "2026-08-31T12:00:00Z",
"secret": "c2VjcmV0LXZhbHVlLWZvci1leGFtcGxlLW9ubHk",
"secretID": "sec_01HF5J9ZKQT4RXP8M2VYBN3D"
}
}Headers
X-Moov-Version
stringv2026.07.00). When omitted, the server applies its default version.X-Idempotency-Key
string
requiredPath parameters
providerID
string
requiredResponse
signingSecret
object
requiredsecret.Show child attributes
signingSecret
createdOn
string<date-time>
requiredrevokedOn
string<date-time> | null
requiredsecret
string
requiredsecretID
string
required