---
title: "Edit a push token"
method: PUT
path: "/tokens/{token_id}"
tags: ["Tokens"]
---

# Edit a push token

`PUT /tokens/{token_id}`

Update a push token and installation setup.
⚠️ Endpoint is available only in Customer interface.

## Path parameters

- `token_id` string, required

## Headers

- `Accept-Language` string

## Request body

- object
  - `setup` Setup, required — Setup of a client's device.
    - `language_id` string, required — The unique ID of the language by ISO 639-1 code from [GET /languages](https://carecloud.readme.io/reference/getlanguages).
    - `allowed_gps` boolean, required — Permission to GPS tracking in the mobile application.
    - `allowed_notifications` boolean, required — Permission to the mobile application notifications.
  - `push_token` string — Push notification token (Apple or Google).

## 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)
