PASSID
PASSID API Docs Partner-ready reference
Quickstart Integration Guide Security Request Sandbox Access
Live API Reference

Browse PASSID endpoints, auth, schemas, and examples in one place.

This reference is rendered from the current PASSID OpenAPI contract and bundled directly into the docs page. It covers institution verification flows, bridge share lifecycle endpoints, request and response examples, authentication requirements, and the schema objects partner teams need to integrate with confidence.

Institution auth X-Institution-Key and institution JWT flows
User wallet auth Authorization: Bearer <user JWT>
Decisioning PASSID verifies claims, institutions keep final approval
Coverage
Endpoints, auth models, schemas, request bodies, response bodies, examples, and verification semantics.
Environments
Production, sandbox, and local development are all documented directly from the same source contract.
Partner posture
PASSID returns verified credential signals. Eligibility, onboarding, and underwriting decisions stay with the institution.
Try the verify flow

Try the verify flow

PASSID is easiest to understand as one clean handoff. The user creates a scoped share token, the institution sends that token to /api/v1/bridge/verify, PASSID returns verified credential signals, and the institution keeps the final underwriting or onboarding decision.

Create share
Verify token
Return claims
Institution decides
Step 1 User creates a PASSID share token

The wallet creates a scoped share the applicant can hand to a verifier without exposing raw bank statements or repeated document uploads.

Step 2 Institution sends token to /api/v1/bridge/verify

The bank, lender, or platform submits the received token with its institution key so the verification is attributed correctly.

Step 3 PASSID returns verified claims

The response includes credential signals like income verification, identity status, fraud risk, payment reliability, and compatibility scoring fields.

Step 4 Institution makes the decision

PASSID does not approve or reject the applicant. The institution uses the verified claims in its own underwriting, onboarding, or risk engine.

Sample request Send the token to PASSID verify
POST /api/v1/bridge/verify
{
  "token": "PASSID-EXAMPLE-TOKEN"
}
Sample response Verified claims returned to the institution
200 Response
{
  "success": true,
  "data": {
    "valid": true,
    "token": "PASSID-EXAMPLE-TOKEN",
    "verifiedAt": "2026-04-09T14:12:00Z",
    "claims": {
      "income_verified": true,
      "income_stability": "stable",
      "fraud_risk": "low",
      "identity_verified": true,
      "payment_reliability": 0.91,
      "savings_consistency": 0.74,
      "fsi_score": 812,
      "tier": "B"
    }
  }
}
fsi_score = credential strength
tier = credential band
PASSID returns verified credential signals. Final decisioning remains with the institution.
Rendered inside PASSID, backed by the current OpenAPI source of truth. The page below is generated from the active PASSID API contract and rendered in-app. It is designed for partner engineers, solution architects, and risk teams reviewing endpoint behavior before a pilot or production launch.
Embedded spec loaded in-app
PASSID Reference Endpoints, auth, request examples, response examples, and schemas rendered with Redoc.
/docs mounted route
No raw spec download link
Mobile-friendly layout
Loading PASSID API reference...