Get current person-bound OIDC identity

POST

/v1/oauth/userinfo

const url = 'https://api.infiniteaudience.ai/v1/oauth/userinfo';
const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request POST \
  --url https://api.infiniteaudience.ai/v1/oauth/userinfo \
  --header 'Authorization: Bearer <token>'

POST form of OIDC UserInfo; accepts the MCP OAuth bearer in the Authorization header. Requires ‘openid’ scope.

Authorizations

oidcBearer

Responses

200

Current OIDC identity claims.

application/json

object

sub

required

Stable opaque subject for this person in this organization.

string

email

Current email when the email scope was granted.

string format: email

email_verified

Present only for a currently verified email.

boolean

Example

{
  "email_verified": true
}

401

RFC 6749-shaped OAuth protocol error — error is a fixed machine-readable code and error_description is a human-readable detail. Deliberately NOT this API’s usual {error, code, message} shape — this is the RFC’s own error contract, used only by /v1/oauth/authorize, /v1/oauth/device_authorization, /v1/oauth/token, and /v1/oauth/revoke.

application/json

RFC 6749 §5.2 / §4.1.2.1 error body — see the OAuthError response component.

object

error

required

string

Allowed values: invalid_request invalid_client invalid_client_metadata invalid_grant invalid_scope invalid_target invalid_token unsupported_response_type unsupported_grant_type authorization_pending slow_down access_denied expired_token server_error

error_description

required

string

Example

{
  "error": "invalid_request"
}