docufykit.comVerify. Extract. Deliver.
Sign inQuickstart

Use GET /v1/verifications/{verification_id} to fetch the latest known state of a verification job.

Signed webhooks should remain the primary async delivery path. REST result retrieval is the secondary lookup path for polling, reconciliation, and operator inspection.

Endpoint

GET https://api.docufykit.com/v1/verifications/{verification_id}

Example request

curl "https://api.docufykit.com/v1/verifications/<verification_id>" \
  -H "X-API-Key: <your-api-key>"

Response sections

Core verification fields

These top-level fields describe the current job state:

  • verification_id
  • status
  • reason_code
  • document_type
  • process_type
  • external_reference_id
  • metadata
  • verification_result
  • structured_data
  • created_at
  • updated_at

verification_result

This section carries the compact decision output:

  • verified
  • fraud_detected

structured_data

When document-type extraction completes, structured document fields are returned directly at structured_data.

Status model

The current public status flow is:

  • awaiting_upload
  • processing
  • verified
  • rejected
  • review_required
  • failed

Use reason_code as the stable machine-readable branch condition.

Example terminal response shape

{
  "verification_id": "ver_123",
  "document_type": "YOK_STUDENT",
  "status": "verified",
  "reason_code": "verified_yok_student",
  "process_type": "sync",
  "verification_result": {
    "verified": true,
    "fraud_detected": false
  },
  "structured_data": {
    "full_name": "Jane Customer"
  }
}

Related pages