---
title: "Revoke connection"
method: GET
path: "/vault/revoke/{service_id}/{application_id}"
tags: ["Connections"]
---

# Revoke connection

`GET /vault/revoke/{service_id}/{application_id}`

__In most cases the authorize link is provided in the ``/connections`` endpoint. Normally you don't need to manually generate these links.__

Use this endpoint to revoke an existing OAuth connector.

Auth links will have a state parameter included to verify the validity of the request. This is the url your users will use to activate OAuth supported integration providers.

Vault handles the complete revoke flow for you and will redirect you to the dynamic redirect uri you have appended to the url.

## Path parameters

- `service_id` string, required
- `application_id` string, required

## Query parameters

- `state` string, required
- `redirect_uri` string, required

## Response `default`

Unexpected error

- UnexpectedErrorResponse
  - `status_code` number — HTTP status code
  - `error` string — Contains an explanation of the status_code as defined in HTTP/1.1 standard (RFC 7231)
  - `type_name` string — The type of error returned
  - `message` string — A human-readable message providing more details about the error.
  - `detail` union — Contains parameter or domain specific information related to the error and why it occurred.
    - string
    - object
  - `ref` string — Link to documentation of error type

## Other responses

- `301` — redirect
- `400` — Bad Request
- `401` — Unauthorized
- `402` — Payment Required
- `404` — The specified resource was not found
- `422` — Unprocessable

---

[API](https://skmtc.net/apideck-libraries/apis/vault-api.md) · [All operations](https://skmtc.net/apideck-libraries/apis/vault-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/apideck-libraries/vault-api/versions/1b8e8b6feb36/schema)