If your project has a custom domain configured, this endpoint will also be available at https://{customdomain}/v1/oauth2/register.
Register a new OAuth 2.0 client dynamically with Stytch. This endpoint allows client applications to register themselves without requiring manual configuration through the Dashboard.
This feature must be enabled at the project level in the Connected Apps section of the Dashboard.
This endpoint creates or returns an existing Third Party Public Connected App client. If a client with identical metadata already exists, the same client ID will be returned. Otherwise, a new client will be created.
No authorization is needed for this endpoint.
This endpoint implements the OpenID Connect Dynamic Client Registration specification and is compatible with the OAuth 2.0 Dynamic Client Registration specification.
Client Deduplication
To prevent duplicate clients, Stytch computes a hash of the submitted client metadata. If the metadata matches an existing client exactly, the existing client ID is returned instead of creating a new one. This ensures that multiple instances of the same application (like MCP clients) can be administered as a single client identity.
Supported Client Types
Only Third Party Public clients are supported through dynamic registration. All dynamically registered clients will have:
- grant_types: ["authorization_code", "refresh_token"]
- response_types: ["code"]
- token_endpoint_auth_method: "none"
PKCE is required for all authorization flows using dynamically registered clients.