---
title: "Validate the proposed password"
method: POST
path: "/v2/users/self/password/validate"
tags: ["Users"]
---

# Validate the proposed password

`POST /v2/users/self/password/validate`

validate the password and return a score

## Request body

- PasswordRequest
  - `password` string, required — a password that passes validation

## Response `200`

the password was checked and a score returned

- ValidatePasswordResponse
  - `score` integer — More secure passwords are given a higher score. <P> For a password to be acceptable for use in Velo, it must score at least 3
  - `valid` boolean — if true then the password can be accepted
  - `warning` string — Any warning message as a reason for the given score.
  - `suggestions` string[]

## Other responses

- `400` — Invalid request. See Error message payload for details of failure
- `401` — Invalid access token. May be expired or invalid
- `403` — The authentication does not have permissions to access the resource This usually occurs when there is a valid authentication instance (client or user) but they do not have the required permissions

---

[API](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis.md) · [All operations](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/velopaymentsapi/velo-payments-apis/versions/05c3f09fc50a/schema)