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

# Revoke Installation Credential

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

Retires a superseded installation credential, so a partner can complete a rotation it started with `POST /credentials/rotate` — the leaked credential stops working without the customer having to reinstall. Authenticated by a live installation credential plus the integration's client secret. The credential to retire is named in the body rather than being the one that authenticates, so the ordinary flow is: rotate, store the replacement, then authenticate with the replacement and revoke the old one. Refuses to retire an installation's last live credential. Rotation exists so remediation is not customer-visible; revoking the only credential would undo that and leave the install needing a reinstall.

## Path parameters

- `integrationConfigurationId` string, required

## Request body

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

## Response `200`

- object
  - `revoked` false | true, required
  - `already_revoked` false | true, 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.dev/vercel/apis/api.md) · [All operations](https://skmtc.dev/vercel/apis/api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/vercel/api/revisions/4191ba96b0c1/schema)