Post v1secrets rotate
Rotate a secret to a new value within the caller’s organization, storing it as a new version. The new value is not returned.
Retries are safe with an idempotency-key header: repeating the request with the same key and
the same value returns the secret’s current metadata instead of rotating a second time, and
reusing a key with a different value (or another secret) fails with idempotency_conflict.
Without a key, every call mints a new version.
Authorizations
Hiloop API key sent as an HTTP Bearer token.
Headers
Optional idempotency key for this mutation. The server records the result from execution start. For at least 72 hours, reuse by the same organization and route replays the original status and body. A matching request still in flight or reuse for different input returns 409 idempotency_conflict. Keys are scoped by organization and route and contain 1-255 characters.
1 - 255Path Parameters
The secret id to rotate.
Body
Response
OK
The rotated secret's metadata (with the new current_version and rotated_at set).