Skip to main content
GET
Get Credential

Headers

API-Version
string

Pin request, response, and webhook shapes to a specific dated API version (YYYY-MM-DD). Omit to use the version pinned to your API key (set when the key is created; new keys default to the latest version). New integrations should target the latest version.

Pattern: ^\d{4}-\d{2}-\d{2}$
Example:

"2026-07-06"

Path Parameters

credentialId
string
required

URN of the credential to retrieve

Example:

"urn:via:credential:550e8400-e29b-41d4-a716-446655440000"

Response

The credential, including its W3C Verifiable Credential and the latest grantor decisions.

id
string
required

URN of the credential.

Example:

"urn:via:credential:550e8400-e29b-41d4-a716-446655440000"

resourceType
string
required

The type of resource for this credential (e.g., DOCUMENT, CONSENT, FORM)

Example:

"DOCUMENT"

status
enum<string>
required

The status of the credential

Available options:
DRAFT,
ACTIVE,
REJECTED,
CANCELED,
REVOKED,
EXPIRED
Example:

"DRAFT"

w3cCredential
object
required

The W3C Verifiable Credential following the VIA protocol specification.

While the credential is in DRAFT status, this object is in building mode: evidences, proofs, and other fields may still be attached or modified as grantors review and decide. The proofs array will be empty at this stage.

Once all grantors have accepted (or the request window expires), the status transitions out of DRAFT and cryptographic signature proofs are attached. At that point the credential is fully sealed and can be passed for verification as defined by the VIA protocol.

Example:
decisions
array[]
required

Whether each grantor accepted or rejected the credential and information about the grantor contact. The id field carries the grantor's DID. Always an array (empty when there are no decisions yet).

Example:
name
string

Human-readable name of the credential; null when unset.

Example:

"Credential Name"

description
string

Free-text description of the credential; null when unset.

Example:

"Document to be requested on onboarding"

internalId
string

Identifier to help you identify the credential in your own system. We recommend using a unique value.

Example:

"internal-12345"

tags
string[]

Free-form labels attached to the credential.

Example: