Staging environment — data here is not production data
Browse documentation

Fidera documentation

Screening infrastructure for customer-owned compliance

Run identity and screening Checks, retain immutable evidence, and detect changes without outsourcing your investigation workflow.

Fidera is screening infrastructure. It executes Checks, records evidence, and runs recurring Monitors. Your systems remain the source of truth for investigation and case workflow.

Object What it represents
Applicant Your durable customer record and owner of every Check
Check One immutable evaluation with policy, data versions, nested match evidence, result, and lineage
Monitor A managed recurring Check definition with change detection
Batch A bulk collection of Applicant-owned Check executions
Flow A configured identity-verification journey that can produce Checks

Make your first Check

Start with the five-minute quickstart. It creates a multi-party transaction Check and reads its nested match evidence.

curl https://api.fideralabs.com/v1/checks \
  --request POST \
  --header "Authorization: Bearer $FIDERA_API_KEY" \
  --header "Idempotency-Key: payment-9842-screen-v1" \
  --header "Content-Type: application/json" \
  --data @check.json

The ownership boundary

Fidera owns execution, normalized evidence, screening policy and source versions, recurring scheduling, change detection, webhook delivery, and technical audit.

You own assignment, investigation, SLA, escalation, disposition, four-eyes approval, cases, narratives, and regulatory workflow. Retain Fidera resource IDs in those customer-owned records.

API-first by design

The dashboard is a screening-observability client over the same public /v1 API available to your backend. It does not hide a private review workflow.

The Check detail supports HTTP content negotiation:

curl https://api.fideralabs.com/v1/checks/$CHECK_ID \
  --header "Authorization: Bearer $FIDERA_API_KEY" \
  --header "Accept: text/markdown"

Dashboard URLs ending in .json, .md, or .pdf send the equivalent Accept header.

Portable, open-source documentation

Guides are Git-owned Markdown and the reference is generated from FastAPI OpenAPI. The self-hosted docs use permissively licensed open-source parsing, syntax-highlighting, and type-generation tools; search remains browser-local. CI verifies links, OpenAPI drift, reference coverage, and dependency licenses.

Browse the API reference or read about Applicants and Checks.