---
title: "Rotate Installation Credential"
method: POST
path: "/v1/installations/{integrationConfigurationId}/credentials/rotate"
tags: ["marketplace"]
---

# Rotate Installation Credential

`POST /v1/installations/{integrationConfigurationId}/credentials/rotate`

Issues a replacement access token for an installation, so a partner can rotate a credential it believes is compromised without the customer having to reinstall. Authenticated by the credential being replaced plus the integration's client secret: a leaked access token on its own cannot rotate itself, which would otherwise let an attacker take over the installation and lock the partner out. The previous credential intentionally stays valid so in-flight requests keep working. Retiring it is a separate, explicit operation — a partner is never left mid-rotation without a working credential.

## Path parameters

- `integrationConfigurationId` string, required

## Request body

- object
  - `client_secret` string, required
  - `client_id` string

## Response `200`

- object
  - `scope` string, required
  - `expires_in` number, required
  - `access_token` string, required
  - `token_type` 'oauth2-token', required

## Other responses

- `400` — One of the provided values in the request body is invalid. One of the provided values in the request query is invalid.
- `401` — The request is not authorized.
- `403` — You do not have permission to access this resource.
- `404`
- `409`
- `410`

---

[API](https://skmtc.net/vercel/apis/api.md) · [All operations](https://skmtc.net/vercel/apis/api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/vercel/api/revisions/4c652701e115/schema)