> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/core-api-reference/customer_password_resets.md).

# Customer password resets

The customer password reset object and the allowed CRUD operations on the related resource endpoint

Registered customer passwords can be reset in three steps:

1. [Create a new customer password reset](/core-api-reference/customer_password_resets/create.md) with the customer's email.
2. Get the reset password token from the response.
3. [Update the customer password reset](/core-api-reference/customer_password_resets/update.md) resource passing the token and the new password.

{% hint style="info" %}
Reset password tokens expires after **6 hours**.
{% endhint %}

{% hint style="warning" %}
It's your responsibility to verify the customer's identity before the third step. A typical flow is to send an email to the customer with a verification link that includes the reset password token.
{% endhint %}

{% hint style="info" %}
If the customer is a guest (i.e. has no password associated yet) there's no need to use the customer password reset resource. To set a password for a guest customer just [update the customer](/core-api-reference/customers/update.md) resource passing the desired password.
{% endhint %}

For security reasons, customer passwords must be managed using [integration](/core/api-credentials.md#integration) API credentials only. [Sales channels](/core/roles-and-permissions.md#sales-channel) are only allowed to perform update actions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.commercelayer.io/core-api-reference/customer_password_resets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.