---
title: "Patch client by ID"
method: PATCH
path: "/api/v2/oauth/clients/{clientId}"
tags: ["OAuth2 Clients"]
---

# Patch client by ID

`PATCH /api/v2/oauth/clients/{clientId}`

Patch an existing OAuth 2.0 client by client ID. Updating an OAuth2 client uses a [JSON patch](https://datatracker.ietf.org/doc/html/rfc6902) representation of the desired changes. To learn more, read [Updates](https://launchdarkly.com/docs/api#updates). Only `name`, `description`, and `redirectUri` may be patched.

## Path parameters

- `clientId` string, string, required — The client ID

## Request body

- PatchOperation[]
  - `op` string, required — The type of operation to perform
  - `path` string, required — A JSON Pointer string specifying the part of the document to operate on
  - `value` string — A JSON value used in "add", "replace", and "test" operations

## Response `200`

OAuth 2.0 client response

- Client
  - `_links` object, required — The location and content type of related resources
  - `name` string, required — Client name
  - `description` string — Client description
  - `_accountId` string, required — The account ID the client is registered under
  - `_clientId` string, required — The client's unique ID
  - `_clientSecret` string — The client secret. This will only be shown upon creation.
  - `redirectUri` string, required — The client's redirect URI
  - `_creationDate` integer, required

## Other responses

- `400` — Invalid request
- `401` — Invalid access token
- `403` — Forbidden
- `404` — Invalid resource identifier

---

[API](https://skmtc.dev/launchdarkly/apis/launchdarkly-rest-api.md) · [All operations](https://skmtc.dev/launchdarkly/apis/launchdarkly-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/launchdarkly/launchdarkly-rest-api/revisions/69c5c9aafe78/schema)