Endpoints for submitting evidentiary documents and querying credential verification state.

Verification API

The Verification API manages the lifecycle of evidentiary proof submissions, automated checks, and badge issuance.

1. Request Credential Verification

Submits an evidentiary document (PDF, certificate scan, diploma) to verify a specific claim on a profile.

POST /api/request-verification

Request Headers

Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>

Request Payload

{
  "credentialType": "education",
  "credentialId": "edu_01",
  "documentUrl": "https://kfysrcdqszgkmusaiigh.supabase.co/storage/v1/object/public/files/verification/doc_99.pdf",
  "notes": "Official university diploma transcript copy."
}

Response Example (`201 Created`)

{
  "success": true,
  "data": {
    "ticketId": "ticket_77a912c",
    "status": "pending",
    "credentialId": "edu_01",
    "submittedAt": "2026-09-19T01:32:00Z"
  },
  "error": null,
  "meta": {
    "requestId": "req_5510b3",
    "timestamp": "2026-09-19T01:32:00Z"
  }
}

2. Check Verification Ticket Status

Query the real-time status of a submitted verification request.

GET /api/request-verification?ticketId=ticket_77a912c

Response Example (`200 OK`)

{
  "success": true,
  "data": {
    "ticketId": "ticket_77a912c",
    "status": "verified",
    "reviewedAt": "2026-09-19T01:45:00Z",
    "reviewerNotes": "Document validated against issuing authority registry.",
    "trustBadgeIssued": true
  },
  "error": null,
  "meta": {
    "requestId": "req_8819a1",
    "timestamp": "2026-09-19T01:45:00Z"
  }
}

3. Verification State Lifecycle

Status	Definition
`unverified`	Claim is self-reported by the user with no evidentiary document attached.
`pending`	Document uploaded; awaiting manual or automated validation.
`verified`	Evidentiary proof approved. Visual cryptographic badge active on profile.
`rejected`	Document rejected due to illegibility, expiration, or mismatch.

Verification API

On this page