eSeal a Verifiable Credential using your certificate

Request to sign a credential with DID's EIDAS associated keys. It requires providing the DID of the issuer, the payload to sign, the signature type and password to decode P12 file. Create an eIDAS eSeal signature using the associated eIDAS keys with a DID. Notice that you will have to previously associate your issuer did with a valid certificate. Notice that the certificate provided as example is only for test purposes, do not use it for your own certificates.

Request Body — REQUIRED
issuer string — REQUIRED DID of the Issuer
payload object — REQUIRED W3C Verifiable Credential or Credential (without Proof) to eSeal
password password Password to decode P12 file
expiresIn number expiration time in seconds

Responses
201 Created Schema id uri URI that is used to unambiguously refer to an object, such as a person, product, or organization. @context string[] — REQUIRED An ordered set where the first item is a URI https://www.w3.org/2018/credentials/v1. It is used to define terms and help to express specific identifiers in a compact manner. type string[] — REQUIRED Type of the object or the datatype of the typed value. issuer A URI or an object containing an id property. Example: DID of the verifiable credential/presentation issuer. credentialSubject object A set of objects that contain one or more properties that are each related to the subject of the credential. issuanceDate date-time Date and time at which the information associated with the verifiable credential/presentation becomes valid. validUntil date-time Date and time at which a credential/presentation ceases to be valid. proof object — REQUIRED
400 Bad Request Schema type uri An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable documentation for the problem type. title string A short summary of the problem type. status int32 Possible values: 400 ≤ value < 600 The HTTP status code generated by the origin server for this occurrence of the problem. detail string A human readable explanation specific to this occurrence of the problem. instance uri An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
401 Unauthorized Schema type uri An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable documentation for the problem type. title string A short summary of the problem type. status int32 Possible values: 400 ≤ value < 600 The HTTP status code generated by the origin server for this occurrence of the problem. detail string A human readable explanation specific to this occurrence of the problem. instance uri An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
403 Forbidden Schema type uri An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable documentation for the problem type. title string A short summary of the problem type. status int32 Possible values: 400 ≤ value < 600 The HTTP status code generated by the origin server for this occurrence of the problem. detail string A human readable explanation specific to this occurrence of the problem. instance uri An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
500 Internal Server Error Schema type uri An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable documentation for the problem type. title string A short summary of the problem type. status int32 Possible values: 400 ≤ value < 600 The HTTP status code generated by the origin server for this occurrence of the problem. detail string A human readable explanation specific to this occurrence of the problem. instance uri An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.