---
title: "Send the message for the setup of a new customer's password"
method: POST
path: "/tokens/{token_id}/actions/send-password-setup-email"
tags: ["Tokens"]
---

# Send the message for the setup of a new customer's password

`POST /tokens/{token_id}/actions/send-password-setup-email`

Send a message, that contains a link to set up a new customer password.
The use case [Forgotten password](https://www.crmcarecloud.com/build-a-mobile-app/#accordion-customer-use-case-customer-account-operations-4) shows how to use this action method.
⚠️ Endpoint is available only in the Customer interface.
⚠️ An extra setup of the Marketing Automation scenario in CareCloud could be necessary to make the endpoint work correctly. If so, don't hesitate to get in touch with the CareCloud administrator in your organization.

## Path parameters

- `token_id` string, required

## Headers

- `Accept-Language` string

## Request body

- object
  - `email` string — Message with a setup password link will be delivered to this email address. ⚠️This parameter is deprecated and will be removed in the future versions of CareCloud API.If possible do not use it.
  - `communication_channel_id` string — ID of communication channels that will be used for password setup. Parameter is required if `email` parameter is not set.The list of all available channels is provided here: [GET /communication-channels](https://carecloud.readme.io/reference/getcommunicationchannels) The possibility of a password setup message from a channel may vary depending on the project setup. For more information, please contact the CareCloud administrator.
  - `recipient` string — Recipient of the message with a password setup. The value of a parameter depending on `communication_channel_id`. Parameter is required if `email` parameter is not set.

## Response `204`

No Content

## Other responses

- `400` — Bad input parameter. The response body's `error.error_data.invalid_params[]` array lists the parameters that caused the failure, each carrying a `reason` code. See the `BadRequestErrorBody` schema for the generic reason taxonomy. Operations with domain-specific business rules document additional reasons at the operation level.
- `401` — The client has invalid credentials or auth token.
- `403` — The client does not exist or the client tried to access an unauthorized property or resource.
- `404` — The resource was not found.
- `405` — The resource does not support the specified HTTP method.
- `429` — Too many requests - more than the resource limit.
- `500` — Server is not working as expected.
- `503` — Temporary state when the service is temporarily unavailable, overloaded or there is a maintenance window.

---

[API](https://skmtc.net/crmcarecloud/apis/rest-api-reference.md) · [All operations](https://skmtc.net/crmcarecloud/apis/rest-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/crmcarecloud/rest-api-reference/revisions/329c06dbf8d9/schema)