---
title: "Delete an authentication configuration"
method: DELETE
path: "/api/v3.1/auth_configs/{nanoid}"
tags: ["Auth Configs"]
---

# Delete an authentication configuration

`DELETE /api/v3.1/auth_configs/{nanoid}`

Soft-deletes an authentication configuration by marking it as deleted in the database. This operation cannot be undone. Pass `?revoke_on_delete=true` to also revoke the upstream credentials of every connection using this auth config via a background job.

## Path parameters

- `nanoid` string, authConfigId, required — The unique identifier of the authentication configuration to delete

## Query parameters

- `revoke_on_delete` boolean, nullable — When `true`, the delete also starts a background job that revokes the upstream credentials of every connected account in scope, and the response carries a `revoke_job_id`. Defaults to `false`. Revocation is irreversible — recovering a deleted entity does not restore working credentials.

## Response `200`

Successfully deleted auth config

- object
  - `revoke_job_id` string — Identifier of the background revoke job started for this delete. Present only when `revoke_on_delete=true`. Track the job and its per-connection results from the Composio dashboard — a programmatic endpoint to poll this job is not yet generally available.

## Other responses

- `400` — Bad request - Invalid auth config ID format
- `401` — Unauthorized - Authentication required
- `404` — Auth config not found - The specified configuration does not exist or was already deleted
- `500` — Internal server error - Something went wrong on the server

---

[API](https://skmtc.net/composiohq/apis/composio-platform-api-v3-1.md) · [All operations](https://skmtc.net/composiohq/apis/composio-platform-api-v3-1/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/composiohq/composio-platform-api-v3-1/versions/4239836857f8/schema)