POST/authorisation/v4/token
Users receive access tokens after they present a valid EBSI Verifiable Credential and prove ownership over their DID.
Request
- application/x-www-form-urlencoded
Body
required
MUST be set to "vp_token"
Signed Verifiable Presentation. See also the VP Token schema definition.
Descriptor for the vp_token, linked by presentation_definition. See also the Presentation Definition schema.
Possible values: [openid didr_write
, openid didr_invite
, openid tir_write
, openid tir_invite
]
OIDC scope
Responses
- 200
- 400
- 500
Success
- application/json
- Schema
- Example (from schema)
- Token Response
Schema
The access token issued by the authorization server in JWS format. See also the "Access Token" schema definition
Possible values: [Bearer
]
MUST be Bearer
Possible values: >= 1
The lifetime in seconds of the access token
Possible values: [openid did_write
, openid tir_write
]
The scope of the access token
ID Token value associated with the authenticated session. Presents client's identity. ID Token is issued in a JWS format. See also the "ID Token" schema definition.
{
"access_token": "32164be2809b7e8acdaf",
"token_type": "Bearer",
"expires_in": 7200,
"scope": "openid did_write",
"id_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzI1NksifQ.eyJpYXQiOjE2NDE1NTI2MDAsInN1YiI6Imh0dHA6Ly9sb2NhbGhvc3Q6MzAwMCIsImF1ZCI6Imh0dHA6Ly9sb2NhbGhvc3Q6MzAwMCIsImlzcyI6ImRpZDplYnNpOnoyMVNxTUo1M2ZZUzY5VlpSWVRVRURhZyJ9.YIdjUCinbG2DRU0VhFTOPcHK9D0iLcx6zBPmF94phfVOx8IVZwOLMfnEp_9xx87-UNODVCLWNR2UdjUgQyv14A"
}
Token Response
{
"access_token": "jwt",
"id_token": "jwt",
"token_type": "Bearer",
"scope": "openid tir_write",
"expires_in": 7200
}
Bad Request
- application/json
- Schema
- Example (from schema)
- Bad Request
Schema
Default value: about:blank
An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable documentation for the problem type.
A short summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
"type": "about:blank",
"title": "Internal Server Error",
"status": 500,
"detail": "Connection timeout",
"instance": "string"
}
{
"title": "Bad Request",
"status": 400,
"detail": "[\"grant_type must be equal to vp_token\",\"scope should not be null or undefined\",\"vp_token must be a jwt string\",\"presentation_submission must be a non-empty object)\"]",
"type": "about:blank"
}
Internal Server Error
- application/problem+json
- Schema
- Example (from schema)
- Internal Server Error
Schema
Default value: about:blank
An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable documentation for the problem type.
A short summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
"type": "about:blank",
"title": "Internal Server Error",
"status": 500,
"detail": "Connection timeout",
"instance": "string"
}
{
"title": "Internal error",
"status": 500,
"detail": "Internal error"
}