---
title: "Rotatecancel"
method: POST
path: "/v1/m2m/clients/{client_id}/secrets/rotate/cancel"
tags: ["Clients"]
---

# Rotatecancel

`POST /v1/m2m/clients/{client_id}/secrets/rotate/cancel`

## Request

- Base URL: `https://api.stytch.com`
- URL: `https://api.stytch.com/v1/m2m/clients/{client_id}/secrets/rotate/cancel`
- Auth: HTTP basic

Cancel the rotation of an M2M client secret started with the [Start Secret Rotation Endpoint](https://stytch.com/docs/b2b/api/m2m-rotate-secret-start) [Start Secret Rotation Endpoint](https://stytch.com/docs/api/m2m-rotate-secret-start).
After this endpoint is called, the client's `next_client_secret` is discarded and only the original `client_secret` will be valid.

## Path parameters

- `client_id` string, required: The ID of the client.

## Request body

- ApiM2mV1M2mClientsSecretsRotateCancelRequest: Request type

## Response `200`

Successful response

- ApiM2mV1M2mClientsSecretsRotateCancelResponse
  - `request_id` string, required: Globally unique UUID that is returned with every API call. This value is important to log for debugging purposes; we may ask for this value to help identify a specific API call when helping you debug an issue.
  - `m2m_client` ApiM2mV1M2MClient, required
    - `client_id` string, required: The ID of the client.
    - `client_name` string, required: A human-readable name for the client.
    - `client_description` string, required: A human-readable description for the client.
    - `status` string, required: The status of the client - either `active` or `inactive`.
    - `scopes` string[], required: An array of scopes assigned to the client.
    - `client_secret_last_four` string, required: The last four characters of the client secret.
    - `trusted_metadata` object: An arbitrary JSON object for storing application-specific data.
    - `next_client_secret_last_four` string: The last four characters of the `next_client_secret`. Null if no `next_client_secret` exists.
  - `status_code` integer, required: The HTTP status code of the response. Stytch follows standard HTTP response status code patterns, e.g. 2XX values equate to success, 3XX values are redirects, 4XX are client errors, and 5XX are server errors.

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `429`: Too Many Requests
- `500`: Internal server error

## Changes

- **2026-03-07** `110f26a94e5b`: 1 info
  - endpoint added
- **2026-03-06** `9cab20b8eca7`: 1 breaking
  - api path removed without deprecation
- **2026-01-09** `7dfcc14e566c`: 1 breaking, 1 warning
  - the `m2m_client/trusted_metadata` response's property type changed from `string` to `object` for status `200`
  - removed the request property `client_id`
- **2025-11-03** `b2acbf387799`: 1 breaking
  - added the new required request property `client_id`
- **2025-10-24** `69e827881158`: 1 warning
  - removed the request property `client_id`

[Operation history](https://skmtc.dev/stytch/apis/stytch-api/changes/v1/m2m/clients/:client_id/secrets/rotate/cancel/post.md)

---

[API](https://skmtc.dev/stytch/apis/stytch-api.md) - [All operations](https://skmtc.dev/stytch/apis/stytch-api/llms.txt) - [OpenAPI document](https://skmtc.dev/stytch/apis/stytch-api/revisions/6d1ff7474803?raw)