Build customer compliance with one API

Fidera gives your product two durable operational objects:

Object	What it represents	What you do with it
Check	An immutable evaluation, policy snapshot, source versions, and evidence	Reconcile the decision into your product and retain the Check ID
Alert	An actionable hit created by a Check	Assign, investigate, escalate, dispose, and audit

Every Check belongs to an Applicant. For transactions and trades, the Applicant is your customer while the Check's typed subjects represent senders, receivers, intermediaries, companies, wallets, vessels, or aircraft.

Fidera does not create product-level cases. Group Fidera check_id, alert_id, applicant_id, and input_ref values in your own case or investigation system.

Make your first Check

Start with the five-minute quickstart. It creates a multi-party transaction Check, reads its decision, and shows how an actionable match becomes an Alert.

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

Choose an integration path

• Single and multi-party Checks — evaluate onboarding, ongoing, transaction, lookback, trade, and ad-hoc subjects.
• Batches — submit up to 1,000 records and download consolidated results.
• Monitors — keep a stable Applicant and subject set under recurring screening.
• Flows — run configured document, biometric, and risk-check journeys.
• Webhooks — receive Alert, disposition, batch, and monitor events with signed, retryable delivery.

API-first by design

The operator dashboard uses the same public /v1 operations available to your backend. Assignment, dispositions, policy changes, manual monitor runs, webhook retries, and evidence exports do not rely on private dashboard-only contracts.

Browse the complete API reference, generated from the same OpenAPI document used to generate the dashboard's TypeScript client types.

Documentation guarantees

This site is built from Markdown and OpenAPI committed with the application. CI checks internal links, stale endpoint names, public operation coverage, and the licenses of the documentation dependencies. Documentation changes ship through the same review and release process as API changes.