Skip to main content

Overview

A credential template defines the schema for a verifiable credential — what attributes it contains, which are required, and which are always disclosed to verifiers. Templates are reusable: create one “Web Development Completion” template and use it to credential hundreds of youth.
You provide a human-readable code. The API uses it to generate a Verifiable Credential Type (VCT) URI — the unique identifier that connects issuers to verifiers across the ecosystem. Share this type URI with any verifying partner who needs to request credentials of this type.

Endpoint

Request

Request Body Fields

Attribute Fields

Each attribute in the template defines a data field on the credential:

Selective Disclosure Design

Think carefully about alwaysDisclosed. This is a first-class concept, not a footnote:
  • alwaysDisclosed: true — The attribute is always visible to verifiers. Use for essential information like programme name and completion date.
  • alwaysDisclosed: false — The youth chooses whether to share this attribute. Use for sensitive information like assessment scores, personal identifiers, or anything the youth might reasonably want to keep private.
In the example above, Thandi can share her “Web Development Completion” credential with an employer while withholding her assessment score — that’s her choice, not the issuer’s or the verifier’s.

Response

HTTP 200 OK

Key Response Fields

Save the id (needed for Step 3: Issue a Credential) and the type URI (share with verifying partners).

Listing Credential Templates

Retrieve all credential templates for your organisation:
Returns an array of all templates with their id, name, type, status, and attributes.

Ecosystem Presets

YoID provides ecosystem presets — standardised credential structures for common use cases. Partners can create a template directly from a preset, or customise one based on a preset.