---
title: /oauth2/register
description: The /oauth2/register endpoint is defined in:
component: pingam
version: 7.4
page_id: pingam:am-oidc1:rest-api-oauth2-register-endpoint
canonical_url: https://docs.pingidentity.com/pingam/8.1/am-oidc1/rest-api-oauth2-register-endpoint.html
llms_txt: https://docs.pingidentity.com/pingam/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
keywords: ["OpenID Connect (OIDC)", "Standards", "Endpoints", "Self-Service"]
page_aliases: ["oidc1-guide:rest-api-oauth2-register-endpoint.adoc"]
superseded_by: https://docs.pingidentity.com/pingam/8.1/am-oidc1/rest-api-oauth2-register-endpoint.html
---

# /oauth2/register

The `/oauth2/register` endpoint is defined in:

* [OpenID Connect Dynamic Client Registration 1.0 incorporating errata set 1](https://openid.net/specs/openid-connect-registration-1_0.html)

* RFC 7591: [OAuth 2.0 Dynamic Client Registration Protocol](https://www.rfc-editor.org/rfc/rfc7591.html)

* RFC 7592: [OAuth 2.0 Dynamic Client Registration Management Protocol](https://www.rfc-editor.org/rfc/rfc7592.html)

Use this endpoint to create, read, update, and delete client application profiles.

Specify the realm in the request URL; for example:

```none
https://openam.example.com:8443/openam/oauth2/realms/root/realms/alpha/register
```

The endpoint supports the following HTTP methods:

* `POST`

  Create a client profile.

* `GET`

  Read a client profile.

* `PUT`

  Update a client profile.

* `DELETE`

  Delete a client profile.

PingAM requires configuration to allow dynamic registration. For details, refer to [Dynamic client registration](oauth2-dynamic-client-registration.html).