Overview
After presenting the request to the youth, retrieve the verification result. The recommended approach is to use webhooks to be notified when the youth responds. As a fallback, you can poll this endpoint.Endpoint
Request
id returned in Step 2.
Response
HTTP 200 OKprogrammeName, completionDate, and fullName. Her assessmentScore and skillsCovered are not present because she withheld them. This is selective disclosure in action.
Status Values
Credential Validation Fields
Checking Validity
Always check both conditions before trusting the presented data:status === "ANSWERED"— the youth respondedcredentials[].isValid === true— the credential is cryptographically authentic
isValid field confirms that:
- The credential hasn’t been tampered with
- The issuer’s decentralized identifier (DID) is legitimate
- The credential is cryptographically signed and authentic
- The credential has not been revoked
Webhooks (Recommended)
For production integrations, use webhooks instead of polling. Register a webhook endpoint once, and your application is notified automatically when:- The youth presents their credentials (
openid4vc.presentation.verified) - The youth declines the request (
openid4vc.presentation.failed) - The request expires (
openid4vc.presentation.expired)
Polling (Fallback)
If webhooks aren’t feasible, poll this endpoint every 2–3 seconds until the status changes fromrequested. This approach works for testing but creates unnecessary load at scale.
The verification workflow is complete. Use the
attributes from the response to process the verified youth data in your application — for job placement, scholarship eligibility, or any other decision that previously required manual document verification.
