---
title: "Patch an existing charge auth token"
method: PATCH
path: "/api/v1/charge-auth-tokens/{chargeAuthTokenId}"
tags: ["Charge Auth Tokens"]
---

# Patch an existing charge auth token

`PATCH /api/v1/charge-auth-tokens/{chargeAuthTokenId}`

Required scope: `charge-auth-tokens:write` </br>Organization authorization: `supported`

## Path parameters

- `chargeAuthTokenId` integer, required

## Request body

- PatchChargeAuthToken
  - `teamId` integer, nullable — Id of the team the charge auth token belongs to
  - `userId` integer, nullable — Id of the user the charge auth token should be associated to
  - `vehicleId` integer, nullable — Id of the vehicle to link to this charge auth token
  - `name` string, nullable — Name of the charge auth token
  - `montaNetwork` boolean, nullable — If the charge auth token should be active in the Monta network
  - `roamingNetwork` boolean, nullable — If the charge auth token should be active in the Roaming network
  - `operatorNetwork` boolean, nullable — Indicates that the charge auth token can be used on other teams charge points underthe same operator
  - `activeUntil` string, date-time, nullable — Indicates until when this charge auth token is active, null means indefinitely. Note: Use `../block` and `../unblock` endpoints to (un)block a charge auth token.
  - `partnerExternalId` string, nullable — External Id of this entity, managed by you.
  - `partnerCustomPayload` object[], nullable — Custom JSON payload for this entity, managed by you.

## Response `200`

Charge auth token updated

- ChargeAuthToken
  - `id` integer — The id of the charge auth token
  - `identifier` string, required — The identifier of the charge auth token, Note: without prefix e.g `VID:`
  - `type` 'vehicleId' | 'rfid', required — The method type used for this charge auth token
  - `teamId` integer — Id of the team that the charge auth token belongs to
  - `userId` integer, nullable — Id of the user that the charge auth token is associated to
  - `vehicleId` integer, nullable — Id of the vehicle linked to this charge auth token
  - `partnerExternalId` string, nullable — External Id of this entity, managed by you.
  - `partnerCustomPayload` object[], nullable — Custom JSON payload for this entity, managed by you.
  - `name` string, nullable — Name of the charge auth token
  - `operator` Operator
    - `id` integer — ID of the operator
    - `name` string, required — Name of operator
    - `identifier` string, required — Identifier of operator
    - `partnerId` integer, nullable — Id of the partner
    - `vatNumber` string, nullable — VAT number
  - `montaNetwork` boolean — If the charge auth token is active in the Monta network
  - `roamingNetwork` boolean — If the charge auth token is active in the Roaming network
  - `operatorNetwork` boolean — Allow this charge auth token to be used on other teams charge points under the same operator
  - `activeUntil` string, date-time, nullable — Indicates until when this charge auth token is active, null means indefinitely
  - `blockedAt` string, date-time, nullable — If the charge auth token is blocked, it will not be able to charge. * `null` = not blocked * date-time = blocked since date-time
  - `createdAt` string, date-time, required — Creation date of this charge auth token
  - `updatedAt` string, date-time, required — Update date of this charge auth token
  - `deleted` boolean — If the charge auth token is deleted

## Other responses

- `400` — The request is invalid
- `401` — Consumer with provided credentials was not found
- `403` — Operator doesn't have access to resource
- `404` — Entity with the provided id was not found

---

[API](https://skmtc.net/monta/apis/monta-partner-api.md) · [All operations](https://skmtc.net/monta/apis/monta-partner-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/monta/monta-partner-api/versions/517e18f11015/schema)