Restore editing access using a saved recovery code
POST/v2/profile/:slug/recover
No edit token or API key is required; the saved recovery code proves control. Atomically rotates both edit token and recovery code without changing profile or entrance details. Save both returned credentials. Invalidates all previously issued guest links; identical recovery retries preserve any links issued after the initial successful recovery. Generate and persist a UUID v4 before sending. Identical code/request ID retries return the same credentials for ten minutes after first success; retries do not extend the window. Different requests cannot reuse a consumed code. Later recovery, replacement, revocation, or deletion invalidates prior retries immediately. Lost responses cannot be recovered after the retry window. All responses use Cache-Control no-store. Requests are limited to 1 KiB and five concurrent calls per server instance.
Request
Responses
- 200
- 400
- 429
- 500
Store the replacement edit token and recovery code
INVALID_BODY for malformed, oversized, or extra JSON fields/values; RECOVERY_REQUEST_INVALID for an invalid or missing UUID v4; RECOVERY_CODE_INVALID for an unknown profile, invalid/disabled/consumed code, or an expired retry (indistinguishable).
Concurrency limit reached
Storage failure (INTERNAL); retry with the same request ID