Prelude Documentation

Prelude v1.0 · Authentication & Token Rotation

Headers

All protected routes require `X-API-Token` with a server-issued static token.

Token rotation

  1. Set `NEXT_API_TOKEN` in the environment.
  2. Deploy (both ACTIVE and NEXT tokens are accepted).
  3. Update clients to use the new token.
  4. Move NEXT → API token, clear `NEXT_API_TOKEN`, redeploy.
  5. Rollback: reapply previous ENV values and redeploy.

Compromise handling

Immediately set `NEXT_API_TOKEN`, redeploy, then promote and remove the compromised value.