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

Credential endpoint

Last updated on 
POST 
/conformance/v3/issuer-mock/credential

The client proceeds with the code flow, and calls the Token Endpoint with the required details and signs client_assertion JWT with client's private keys, which public key counterparts are resolvable through jwks_uri or is in the Client Metadata shared in the pre-registration step.

Request​

Body

    format stringrequired

    Possible values: [jwt_vc]

    REQUIRED. Format in which the VCs should be issued. It MUST be jwt_vc. If not specified, the issuer default format is used.

    types string[]required

    Type to the credential being requested.

    The value MUST match the 'types' property in the request.

    proof objectrequired
    proof_type string

    Possible values: [jwt]

    JSON string denoting proof type.

    MUST be jwt

    jwt JWS

    A signature performed by a key that can be obtained by an identifier in verificationMethod.

    MUST be JWS. See Proof Object schema.

Responses​

OK

Schema
    format string

    Possible values: [jwt_vc]

    JSON string denoting the credential format. It MUST be jwt_vc

    credential string

    The value of the credential claim in the Credential Response MUST be a JSON string. Credentials of this format are already a sequence of base64url-encoded values separated by period characters and MUST NOT be re-encoded. MUST be present when acceptance_token is not returned.

    acceptance_token string

    A JSON string containing a security token subsequently used to obtain a Credential. MUST be present when credential is not returned.

Loading...