OAuth2
Dynamically register an OAuth 2.0 client.
Dynamic Client Registration endpoint as defined by RFC 7591.
Allows OAuth clients (notably MCP clients) to register themselves without out-of-band coordination. The endpoint is unauthenticated; the workspace administrator can disable it through workspace preferences, in which case the endpoint returns 404.
Only the authorization_code grant type and the code response type are supported. Both public clients (token_endpoint_auth_method=none) and confidential clients (token_endpoint_auth_method=client_secret_post) are allowed.
post/v1/oauth/register
Request body
Example request
{
"client_name": "My MCP client",
"redirect_uris": [
"https://app.example.com/oauth/callback"
],
"grant_types": [
"authorization_code"
],
"response_types": [
"code"
],
"scope": "scan incidents:read"
}Example response
{
"client_id": "gg_client_AbCdEf123456",
"client_name": "My MCP client",
"redirect_uris": [
"https://app.example.com/oauth/callback"
],
"grant_types": [
"authorization_code"
],
"response_types": [
"code"
],
"token_endpoint_auth_method": "none",
"scope": "scan incidents:read",
"client_id_issued_at": 1716230400,
"client_secret": "gg_secret_AbCdEf123456"
}