---
title: "Change the person's password, with the current one. Every other session of the person is signed out (this one stays), and their pending email change and password reset links stop working"
method: POST
path: "/v1/me/password"
---

# Change the person's password, with the current one. Every other session of the person is signed out (this one stays), and their pending email change and password reset links stop working

`POST /v1/me/password`

## Request

- Base URL: `https://api.evictionsapi.com`
- URL: `https://api.evictionsapi.com/v1/me/password`
- Auth: HTTP bearer

## Request body

- object
  - `currentPassword` string, required
  - `newPassword` string, required

## Response `204`

The password changed.

## Other responses

- `400`: `invalid_request`: the new password is not 10 to 200 characters (`details.issues` names `newPassword`).
- `401`: The credential is missing or invalid.
- `403`: `account_kind`: the operator's and attorneys' accounts cannot change this here. `wrong_password`: the current password is not correct (5 wrong ones in 15 minutes lock the account, sign-in included). An API key or attorney token: `forbidden`.
- `404`: Not found.
- `409`: `no_password`: the account signs in with Google and has no password.
- `413`: The request body is too large.
- `422`: The case did not pass a check.
- `429`: `rate_limited`: 5 wrong current passwords for this account in 15 minutes; for an email change also more than 10 requests from one address in 10 minutes (counting `POST /v1/me/email/confirm`) or 3 links for the account in an hour. `Retry-After` gives the seconds to wait.
- `503`: `busy`: too many password checks are waiting. Nothing was changed. `Retry-After: 5` gives the seconds to wait; try again.

---

[API](https://skmtc.dev/evictionsapi/apis/evictions-api.md) · [All operations](https://skmtc.dev/evictionsapi/apis/evictions-api/llms.txt) · [OpenAPI document](https://skmtc.dev/evictionsapi/apis/evictions-api/revisions/28459213a1a3?raw)
