Specify the schema that the Verifiable Credential adheres to
ProofOfEmployment
crossmint:bfb292e7-2700-4924-9213-478f3d71f2d8:ProofOfEmployment
.
CourseCompletionCertificate
crossmint:bfb292e7-2700-4924-9213-478f3d71f2d8:CourseCompletionCertificate
.
Membership
crossmint:bfb292e7-2700-4924-9213-478f3d71f2d8:Membership
.
EventParticipation
crossmint:bfb292e7-2700-4924-9213-478f3d71f2d8:EventParticipation
.
CourseCompletionCertificate
, for a credential that represents a course completion. The credential will contain two fields: course
and passed
.
createType.js
file in the tab above, add your API key to the X-API-KEY
header (or create one if you haven’t already) and run via node.
POST /credentials/types/
endpoint to generate a random uuid for the new credential type.
id
. The $id
will be included as the credentials
schema by Crossmint but should not be used to reference the type in Crossmint APIs."crossmint:bfb292e7-2700-4924-9213-478f3d71f2d8:CourseCompletionCertificate"
just created.
credentialSubject
as an object.credentialSubject.properties.id
will be automatically added with the type “string”, this is used to specify the wallet and therefore the identity of the subject.additionalProperties
should always be set to false
to prevent unauthorized fields from being added.required
unless they are optional. This ensures that missing fields will trigger an error during schema validation.additionalProperties
and required
apply only at the level they are specified. For nested objects, these need to be repeated.credentialSubject.properties.id
will not be added for imported schemas. If the original schema does not include this specification, the resulting credentials will not include the user wallet in the subject.id
. To know the subject of a credential, checking the NFT owner will be necessary.