1
Create the verification
Your backend calls POST /v1/verifications with YOK_STUDENT, your own external reference, and an Idempotency-Key.
Use case
Student verification workflow
This flow is for products that need to confirm a person is an active student from an authentic E-Devlet sourced certificate before they unlock onboarding, pricing, or eligibility decisions.
Workflow
How the verification path runs
The shipped path is authenticity-first. The platform does not treat the uploaded PDF as trustworthy until it is matched against the upstream E-Devlet source document.
2
Upload the source PDF
The customer system sends the raw E-Devlet PDF to the signed upload target returned by the create response.
3
Confirm upload completion
The upload-complete call moves the job into processing after the stored object passes file, size, and safety checks.
4
Verify authenticity before extraction
The worker reads QR or barcode data, fetches the upstream source document, and rejects the flow if the uploaded file does not match that source.
5
Use the structured outcome
Your backend receives a signed webhook and can read status, reason_code, and structured student fields over REST for reconciliation.
Structured data
Fields your product can branch on
The current YOK flow returns enrollment-oriented fields that are more useful than generic OCR text when your product needs to make operational decisions.
full_nameregistered_ateducation_typestatusis_activeclassprogramuniversity_namefaculty_name
Decision model
Outcomes to expect in production logic
verified
verified_yok_student
Authenticity checks passed, the student schema validated, and extraction confidence cleared the automatic verification threshold.
review_required
yok_student_schema_invalid or yok_student_low_confidence
Authenticity passed, but the extracted schema is incomplete, invalid, or below the confidence threshold and should stay visible to operators.
rejected
authenticity_hash_mismatch and other source-verification failures
The uploaded PDF could not be trusted as the same document returned by the upstream E-Devlet source, so downstream extraction should not be treated as valid evidence.
Related pages
YOK_STUDENT docs
Document-type behavior, extracted fields, and reason-code outcomes.
Create verification docs
Request shape, idempotency, and signed upload target behavior.
Result retrieval docs
processing_result, extraction_result, and terminal status handling.
Talk to sales
Use this path for launch planning, volume pricing, and security review requirements.