curl --request POST \
--url https://api.sandbox.humanity.org/v2/oauth/authorize/approve \
--header 'Content-Type: application/json' \
--data '
{
"authorization_id": "<string>",
"scopes": [
"<string>"
]
}
'{
"authorization_id": "<string>",
"status": "<unknown>",
"code": "<string>",
"code_expires_at": "<string>",
"scopes": [
"<string>"
],
"granted_scopes": [
"<string>"
],
"app_scoped_user_id": "<string>",
"organization_id": "<string>",
"redirect_uri": "<string>",
"client_id": "<string>",
"state": "<string>"
}curl --request POST \
--url https://api.sandbox.humanity.org/v2/oauth/authorize/approve \
--header 'Content-Type: application/json' \
--data '
{
"authorization_id": "<string>",
"scopes": [
"<string>"
]
}
'{
"authorization_id": "<string>",
"status": "<unknown>",
"code": "<string>",
"code_expires_at": "<string>",
"scopes": [
"<string>"
],
"granted_scopes": [
"<string>"
],
"app_scoped_user_id": "<string>",
"organization_id": "<string>",
"redirect_uri": "<string>",
"client_id": "<string>",
"state": "<string>"
}authorization_id plus an optional subset of scopes to grant. The response returns an authorization code and all metadata necessary for /oauth/token.
Most consumer flows should rely on the hosted consent screen; this API is intended for regulated partners that need to stitch Humanity into an existing adjudication queue.