Get desktop application:
View/edit binary Protocol Buffers messages
Accept an offer to exchange a credential
The JSON document that contains the credential offer
The ID of the credential offer (Parameter ID inside the JSON document)
The ID of the item in the wallet that contains the issued credential
The JSON document that contains the issued credential. This item is already stored in the wallet.
Check credential status in the revocation registry
Request to check a credential's revocation status
Credential Status ID to check. This is not the same as the credential's ID.
Response to `CheckStatusRequest`
The credential's revocation status
Create credential offer
ID of template to use
JSON document string with keys corresponding to the fields of the template referenced by `template_id`
If true, the credential will be issued with holder binding by specifying the holder DID in the credential subject
If true, the issued credential will contain an attestation of the issuer's membership in the ecosystem's Trust Registry.
If true, a short URL link will be generated that can be used to share the credential offer with the holder. This link will point to the credential offer in the wallet app.
The type of signature to use when signing the credential. Defaults to `EXPERIMENTAL`.
The JSON document that contains the credential offer
If requested, a URL that can be used to share the credential offer with the holder. This is a short URL that can be used in a QR code and will redirect the holder to the credential offer using the wallet app.
Create a proof from a signed document that is a valid verifiable credential and contains a signature from which a proof can be derived.
Request to create a proof for a Verifiable Credential using public key tied to caller. Either `item_id`, or `document_json` may be provided, not both.
Selective disclosure specification. If nothing is provided, the entire proof is returned. Either a custom JSON-LD frame is provided, or a list of attributes is provided for selective disclosure
A valid JSON-LD frame describing which fields should be revealed in the generated proof. If unspecified, all fields in the document will be revealed
Information about what sections of the document to reveal
Id of verification template with which to construct the JSON-LD proof document
Specify the input to be used to derive this proof. Input can be an existing item in the wallet or an input document
ID of wallet item stored in a Trinsic cloud wallet
A valid JSON-LD Verifiable Credential document string with an unbound signature. The proof will be derived from this document directly. The document will not be stored in the wallet.
Wrap the output in a verifiable presentation. If the credential used in the proof is bound to the holder DID, the output will always use a verifiable presentation and this field will be ignored.
Nonce value used to derive the proof. If not specified, a random nonce will be generated. This value may be represented in base64 format in the proof model.
Response to `CreateProofRequest`
Valid JSON-LD proof for the specified credential
Sign and issue a verifiable credential from a pre-defined template. This process will also add schema validation and revocation registry values to the credential.
Request to create and sign a JSON-LD Verifiable Credential from a template using public key tied to caller
ID of template to use
JSON document string with keys corresponding to the fields of the template referenced by `template_id`
Save a copy of the issued credential to this user's wallet. This copy will only contain the credential data, but not the secret proof value. Issuers may use this data to keep track of the details for revocation status.
The ISO8601 expiration UTC date of the credential. This is a reserved field in the VC specification. If specified, the issued credential will contain an expiration date. https://www.w3.org/TR/vc-data-model/#expiration
If true, the issued credential will contain an attestation of the issuer's membership in the ecosystem's Trust Registry.
The type of signature to use when signing the credential. Defaults to `EXPERIMENTAL`.
Response to `IssueFromTemplateRequest`
Verifiable Credential document, in JSON-LD form, constructed from the specified template and values; signed with public key tied to caller of `IssueFromTemplateRequest`
Reject an offer to exchange a credential
The JSON document that contains the credential offer
The ID of the credential offer (Parameter ID inside the JSON document)
(message has no fields)
Sends a document directly to a user's email within the given ecosystem
Request to send a document to another user's wallet
Email address of user to whom you'll send the item
Wallet ID of the recipient within the ecosystem
DID URI of the recipient
SMS of user to whom you'll send the item
Send email notification that credential has been sent to a wallet
JSON document to send to recipient
Response to `SendRequest`
(message has no fields)
Update credential status by setting the revocation value
Request to update a credential's revocation status
Credential Status ID to update. This is not the same as the credential's ID.
New revocation status of credential
Response to `UpdateStatusRequest`
(message has no fields)
Verifies a proof by checking the signature value, and if possible schema validation, revocation status, and issuer status against a trust registry
Request to verify a proof
JSON-LD proof document string to verify
Response to `VerifyProofRequest`
Whether all validations in `validation_results` passed
Results of each validation check performed, such as schema conformance, revocation status, signature, etc. Detailed results are provided for failed validations.
Used in:
A list of document attributes to reveal. If unset, all attributes will be returned.
Used in: ,
The signature type is not specified. The experimental signature type will be used.
The signature type uses EdDSA with the Ed25519 curve (NIST compliant). This type of signature does not support selective disclosure of attributes.
The signature type uses BBS signatures with BLS12-381 curve (experimental). This type of signature allows for selective disclosure of attributes.
Result of a validation check on a proof
Used in:
Whether this validation check passed
If validation failed, contains messages explaining why