User info
OpenID Connect 1.0 endpoint for obtaining attributes of a Human Service Consumer conform scope defined in access token.
Request
HTTP methods
POST
Parameters
Example
Response
Headers
Content-Type
String.
Defines response body content type. MUST be equal to application/jwt.
HTTP status codes
200 OK
When a valid request is sent an OK result should be returned.
400 Bad Request
When an access token is valid but request itself is invalid.
401 Unauthorized
When
Authorization
header is either missing, invalid or token has already expired.
Parameters
first_name
String. Optional.
First name of the human who’s access token is used.
last_name
String. Optional.
Last name of the human who’s access token is used.
gender
String. Optional.
Gender of the human who’s access token is used. Available values are male, female, TBD.
company_id
String. Optional.
TBD.
company_name
String. Optional.
TBD.
200 OK Example
Decoded JWT Payload
Last updated