---
title: "List forensic reports"
method: GET
path: "/api/v1/forensic-reports"
tags: ["Forensic Reports"]
---

# List forensic reports

`GET /api/v1/forensic-reports`

## Request

- Base URL: `https://api.dmarc-examiner.com`
- URL: `https://api.dmarc-examiner.com/api/v1/forensic-reports`
- Auth: API key in header `X-API-Key`

Returns DMARC RUF (forensic) reports with optional filtering and pagination.

Returns `403 Forbidden` if the organization's plan does not include forensic reports.

## Query parameters

- `domain_id` string, uuid
- `date_from` string
- `date_to` string
- `source_ip` string
- `auth_failure` 'dmarc' | 'spf' | 'dkim'
- `page` integer
- `limit` integer

## Response `200`

Paginated list of forensic reports

- object
  - `data` ForensicReport[], required
    - `id` string, uuid, required
    - `domain` object
      - `id` string, uuid, required
      - `name` string, required
    - `source_ip` string, required
    - `original_mail_from` string, nullable
    - `reported_domain` string, required
    - `auth_failure` 'dmarc' | 'spf' | 'dkim', required
    - `delivery_result` string, nullable
    - `dkim_result` string, nullable
    - `spf_result` string, nullable
    - `arrival_date` string, date-time, required
    - `created_at` string, date-time, required
  - `pagination` Pagination, required
    - `total` integer, required: Total number of results.
    - `page` integer, required: Current page number.
    - `limit` integer, required: Results per page.
    - `total_pages` integer, required: Total number of pages.

## Other responses

- `400`: Request payload, body field, or query parameter is missing, malformed, outside documented bounds, or fails type/enum validation. Two body shapes can occur: - **Body validation errors** (e.g. missing `name`, wrong type) come from the controller and have the form `{"message": "..."}`. - **Query parameter errors** (e.g. `limit` out of range, `auth_failure` off-enum, `domain_id` not a UUID) flow through the API exception subscriber and add an `error: "bad_request"` machine-readable code: `{"error": "bad_request", "message": "Query parameter \"limit\" must be between 1 and 100, got 999"}`.
- `401`: Authentication failed. Two shapes are possible depending on cause: - **Invalid or revoked key** — body is `{"message": "..."}` only. - **Missing `X-API-Key` header** — body adds an `error: "unauthorized"` machine-readable code. Clients should treat both as the same outcome and read `message` for display.
- `403`: The organization's current plan does not include the feature required by this endpoint (e.g. `apiAccess`, `forensicReports`, `advancedAlerts`). Distinct from `PlanLimitExceeded` (HTTP 402), which signals a *quota* exhausted on a feature the plan does include. If a customer downgrades to Free, all `/api/v1/*` requests will start returning this response.
- `429`: Rate limit exceeded.
- `500`: Internal server error.

---

[API](https://skmtc.dev/dmarc-examiner/apis/dmarc-examiner-api.md) · [All operations](https://skmtc.dev/dmarc-examiner/apis/dmarc-examiner-api/llms.txt) · [OpenAPI document](https://skmtc.dev/dmarc-examiner/apis/dmarc-examiner-api/revisions/92f3f57969f5?raw)