Check representations

The Check is the canonical resource. Select its representation with the HTTP Accept header:

curl "https://api.fideralabs.com/v1/checks/$CHECK_ID" \
  --header "Authorization: Bearer $FIDERA_API_KEY" \
  --header "Accept: application/pdf" \
  --output check-evidence.pdf

Accept	Best for
application/json	Machine reconciliation and long-term structured retention
text/markdown	Human review, version control, and portable text
application/pdf	Fixed attachments for examiner or customer-owned case files

JSON is the default. Responses include Vary: Accept and Cache-Control: private, no-store. PDF responses use an inline check-{check_id}.pdf filename. Unsupported media types return 406 with the supported values.

There is no /export endpoint and no CSV representation. Batch result downloads remain separate because they represent a collection, not one Check.

Dashboard convenience URLs

On the dashboard origin, /checks/{check_id}.json, /checks/{check_id}.md, and /checks/{check_id}.pdf translate the suffix to the corresponding Accept header. The public API does not expose suffix routes.

Retention and reconciliation

Every representation captures the Check's submitted subjects, normalized query, policy snapshot and version, source and dataset versions, timings, nested match evidence, score contributions, decision evidence, and lineage.

If your program stores a rendered copy, retain its check_id, retrieval timestamp, and media type beside the artifact. Use your own case system for operational actions and investigation narrative.