Skip to main content
European CommissionEBSI European Blockchain
Select the Environment you want to work withEnvironment:

Token Endpoint

Last updated on
POST 

/authorisation/v3/token

Users receive access tokens after they present a valid EBSI Verifiable Credential and prove ownership over their DID.

Request

Body

required
    grant_type stringrequired

    MUST be set to "vp_token"

    vp_token stringrequired

    Signed Verifiable Presentation. See also the VP Token schema definition.

    presentation_submission stringrequired

    Descriptor for the vp_token, linked by presentation_definition. See also the Presentation Definition schema.

    scope stringrequired

    Possible values: [openid didr_write, openid didr_invite, openid tir_write, openid tir_invite]

    OIDC scope

Responses

Success

Schema
    access_token ^(([A-Za-z0-9\-_])+\.)([A-Za-z0-9\-_]+)(\.([A-Za-z0-9\-_]+)?$required

    The access token issued by the authorization server in JWS format. See also the "Access Token" schema definition

    token_type stringrequired

    Possible values: [Bearer]

    MUST be Bearer

    expires_in integer

    Possible values: >= 1

    The lifetime in seconds of the access token

    scope stringrequired

    Possible values: [openid did_write, openid tir_write]

    The scope of the access token

    id_token ^(([A-Za-z0-9\-_])+\.)([A-Za-z0-9\-_]+)(\.([A-Za-z0-9\-_]+)?$required

    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.

Loading...