---
title: "Delete OAuth 2.0 Client using the OpenID Dynamic Client Registration Management Protocol"
method: DELETE
path: "/oauth2/register/{id}"
tags: ["oidc"]
---

# Delete OAuth 2.0 Client using the OpenID Dynamic Client Registration Management Protocol

`DELETE /oauth2/register/{id}`

This endpoint behaves like the administrative counterpart (`deleteOAuth2Client`) but is capable of facing the
public internet directly and can be used in self-service. It implements the OpenID Connect
Dynamic Client Registration Protocol. This feature needs to be enabled in the configuration. This endpoint
is disabled by default. It can be enabled by an administrator.

To use this endpoint, you will need to present the client's authentication credentials. If the OAuth2 Client
uses the Token Endpoint Authentication Method `client_secret_post`, you need to present the client secret in the URL query.
If it uses `client_secret_basic`, present the Client ID and the Client Secret in the Authorization header.

OAuth 2.0 clients are used to perform OAuth 2.0 and OpenID Connect flows. Usually, OAuth 2.0 clients are
generated for applications which want to consume your OAuth 2.0 or OpenID Connect capabilities.

## Path parameters

- `id` string, required

## Response `204`

Empty responses are sent when, for example, resources are deleted. The HTTP status code for empty responses is
typically 204.

## Other responses

- `default` — genericError

---

[API](https://skmtc.net/ory/apis/ory-hydra.md) · [All operations](https://skmtc.net/ory/apis/ory-hydra/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ory/ory-hydra/versions/a302a90a0e8a/schema)