DCS Bonafide
DCS BonafideCredential Intelligence Platform
Sign inVerify a credential
AcademicEmploymentProfessionalHow it worksUniversitiesSchoolsEmployers & BGVPlatformsIntelligenceDevelopersTrust & SecurityCandidate RightsPlansSign in
API Reference

A clear API for cases, evidence and results.

Versioned REST contracts

The roadmap freezes the main external REST surface around cases, documents, source verification, intelligence, regulatory checks, rights workflows and receipts. Production contracts remain subject to Phase-0 reuse validation and implementation versioning.

Explore developer overview →How Bonafide works
REST surfaceCase and evidence resources
POST/v1/casesCreate case
POST/v1/cases/{id}/uploadsAdd evidence
GET/v1/cases/{id}/resultCurrent state
POST/v1/disputesCandidate dispute
GET/v1/receipts/{id}/verifyEvidence receipt
Source-firstAuthoritative routes outrank appearanceMinimum evidenceEscalate only what can resolve uncertaintyHuman gateSerious adverse outcomes require reviewAuditableMaterial actions preserve lineage
WHAT BONAFIDE DOES

Purpose-built verification capabilities.

Each capability is a visible part of the verification workflow—not a hidden AI score.

◇

Case resources

POST /v1/cases · GET /v1/cases/{id} · GET /v1/cases/{id}/result

✓

Evidence upload

POST /v1/cases/{id}/uploads

◎

Document verification

POST /v1/documents/{id}/verify

↗

Review & evidence

POST /v1/reviews/{id}/request-evidence · POST /v1/verification-requests

▦

Intelligence

GET /v1/issuers/search · GET /v1/employers/search · GET /v1/verification-routes/{entityType}/{id}

⌁

Rights & trust

GET /v1/regulatory/qualification-check · POST /v1/disputes · POST /v1/appeals · GET /v1/receipts/{id}/verify

EVIDENCE MODEL

Public API output never exposes restricted reference geometry.

Reference masters, typography maps, security regions and benchmark samples are crown-jewel assets. Customer APIs receive conclusions, reason codes and allowed evidence—not the details that would help a forger reproduce a template.

  • Tenant-scoped authentication and rate limits
  • Idempotency for external POST operations
  • Stable request IDs and correlation IDs
  • Short-lived signed object URLs for authorized evidence access
  • PII-minimized logs and auditable privileged access
REST surfaceCase and evidence resources
POST/v1/casesCreate case
POST/v1/cases/{id}/uploadsAdd evidence
GET/v1/cases/{id}/resultCurrent state
POST/v1/disputesCandidate dispute
GET/v1/receipts/{id}/verifyEvidence receipt
WORKFLOW

From input to defensible evidence.

Bonafide follows the strongest available verification route and resumes only the affected lane when new evidence arrives.

01Request→
02Authorize→
03Validate/idempotency→
04Process async lanes→
05Return versioned state
DESIGNED FOR

One evidence model. Role-specific operations.

The same underlying case can be viewed differently by institutions, employers, reviewers, operations and candidates.

01

Backend engineers

Integrate case lifecycle

02

Platform architects

Design async workflows

03

Security teams

Review data and auth boundaries

DECISION DISCIPLINE

Unknown ≠ fake.

Unmapped issuer, new template, legacy document or unavailable source must route to uncertainty/manual verification rather than an automatic accusation.

Authority VerifiedAuthoritative source evidence is consistent.
Highly ConsistentStrong supporting evidence; independent source not complete.
Evidence RequiredA targeted item can likely resolve the case.
Unable to DetermineEvidence remains insufficient; no fraud conclusion.
DCS BONAFIDE · CREDENTIAL INTELLIGENCE PLATFORM

Establish what is bona fide.
Preserve the evidence.

Verify a credentialOpen portal