Lazily migrate a legacy password

POST

/api/auth/migrate-password

Transition helper for accounts created on the platform's previous identity system. When a returning user signs in with email and password but no password is yet stored in the current auth backend, this endpoint verifies the supplied password against the legacy system (read-only) and, on success, sets the same password in the current system so the original credentials keep working with no reset email. The caller should then retry the normal sign-in. Always returns HTTP 200; the boolean result tells the caller whether to retry.

Request

Authorization

API Key

Add parameter in header

X-API-Key

Example:

X-API-Key: ********************

Body Params application/jsonRequired

Examples

Responses

🟢200

application/json

Migration outcome. migrated: true means the password was valid in the legacy system and has now been set in the current system — the caller should retry sign-in. migrated: false means migration was not possible (legacy migration not configured, no matching legacy account, password disabled, or the password did not verify) — the caller should surface the original invalid-credentials error.

Bodyapplication/json

🟠400

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://api.snakk.ai/api/auth/migrate-password' \
--header 'X-API-Key: <api-key>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "email": "user@example.com",
    "password": "s3cret-passw0rd"
}'

Response Example

200 - Password migrated — retry sign-in

{
    "migrated": true
}

Modified at 2026-07-08 19:01:40

Generate a comprehensive agent from detailed inputs