Check evidence

Fidera returns screening observations without owning your investigation workflow. Use a Check's nested matches array as immutable evidence input to your system of record.

Find Checks with relevant evidence

GET /v1/checks is cursor paginated and supports:

• applicant_id, monitor_id, batch_id, and flow_id;
• use_case, dataset, decision, and reconciliation reference;
• has_matches and match_change_type;
• full-text search;
• limit and after.

curl "https://api.fideralabs.com/v1/checks?monitor_id=$MONITOR_ID&match_change_type=new" \
  --header "Authorization: Bearer $FIDERA_API_KEY"

List results include match_count and match_change_counts but omit the potentially larger matches array. Retrieve the selected Check at GET /v1/checks/{check_id} for its complete evidence.

Reconcile into customer workflow

Store at least:

• Fidera check_id;
• nested evidence key for continuity across Monitor runs;
• material_hash to identify evidence changes;
• your own case, assignee, SLA, disposition, approvers, and narrative.

There is no Match mutation or disposition endpoint. Your decision must not change what a future Check reports.

Monitor deltas

For new, create or update work according to your policy. For changed, refresh the evidence attached to existing work. For unchanged, no workflow change is normally necessary. For removed, record that the source match is no longer present without deleting the prior Check.

Use monitor.matches_changed as an acceleration signal, then retrieve the referenced Check and reconcile its nested evidence.