---
title: "Auth Password Verify Create"
method: POST
path: "/auth/password-verify/"
tags: ["authentication"]
---

# Auth Password Verify Create

`POST /auth/password-verify/`

Step-up sudo re-auth — Phase 4 of the staff step-up auth rollout.

Caller is already JWT-authenticated. They submit their password to
refresh the "recently verified" cache flag that Phase 5's
``POST /auth/scope-up/`` reads as its gate before minting an
elevated JWT.

No JWT issued, no permission changed, no user state mutated — the
side effect is one Redis SET with a 5-minute TTL.

See implementation_logs/security/staff_step_up_auth_design.md §5.

## Headers

- `Authorization` string, required

## Response `200`

No response body

- AuthenticationAuthPasswordVerifyCreateResponse200 — Empty response body

---

[API](https://skmtc.net/keywordsai/apis/api-reference.md) · [All operations](https://skmtc.net/keywordsai/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/keywordsai/api-reference/versions/c26d550029f8/schema)