Register Oauth Client

POST /oauth/register

RFC 7591. Refused unless MCP_DYNAMIC_REGISTRATION is on — see the service.

No credential

This operation is public: it authenticates by its own mechanism — a webhook signature or a channel token — rather than by a platform credential.

Request body — ClientRegistrationRequest

Field	Type		Notes
redirect_uris	string[]	required	—
client_name	string | null	optional	max length 200
token_endpoint_auth_method	string | null	optional	max length 40
scope	string | null	optional	max length 400
grant_types	string[] | null	optional	—
response_types	string[] | null	optional	—

Responses

Status	Description	Body
201	Successful Response	—
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/oauth/register \
  -H "Content-Type: application/json" \
  -d '{
       "redirect_uris": [
         "string"
       ]
     }'