> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pr.snh-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sample Pack

> Copy-paste Public Records evaluate payloads for common integrator scenarios

Use these staging-ready request bodies with `POST /evaluate`. Each file is a full JSON body — authenticate first ([Quickstart](/quickstart)), then send as the request payload.

<Tip>
  Prefer a UI? Load the traffic sample from the [quick-start](https://github.com/Theary-AI/quick-start) `/public-records` console (Reset sample), or copy a file from this pack into your client.
</Tip>

## Scenario index

| Scenario                      | Expected focus                            | Schema / path           | File                                                                        |
| ----------------------------- | ----------------------------------------- | ----------------------- | --------------------------------------------------------------------------- |
| Traffic / not reportable      | `Automation`, often `NOT_REPORTABLE`      | ScreeningResults XML    | [`traffic-not-reportable.json`](/samples/traffic-not-reportable.json)       |
| Reportable / auditor          | `Auditor`, `REPORTABLE` charge            | ScreeningResults XML    | [`reportable-auditor.json`](/samples/reportable-auditor.json)               |
| Insufficient data             | Missing disposition → review / validation | ScreeningResults XML    | [`insufficient-data.json`](/samples/insufficient-data.json)                 |
| JSON resubmit                 | Corrected mapped data                     | `record_json`           | [`resubmit-record-json.json`](/samples/resubmit-record-json.json)           |
| BackgroundReportPackage       | Alternate XML schema                      | BackgroundReportPackage | [`background-report-package.json`](/samples/background-report-package.json) |
| OrderXML                      | Alternate XML schema                      | OrderXML                | [`order-xml.json`](/samples/order-xml.json)                                 |
| With `cases[]` (1 charge)     | Your court/offense IDs                    | ScreeningResults XML    | [`with-cases-mapping.json`](/samples/with-cases-mapping.json)               |
| With `cases[]` (multi-charge) | Full mapping — same court ID can repeat   | ScreeningResults XML    | [`with-cases-multi-charge.json`](/samples/with-cases-multi-charge.json)     |

All samples:

* Use **one search per call** (`order_id` + `order_number` + `search_id`)
* Most **omit `cases[]`** (simplest path — evaluate every offense). Use the `with-cases-*.json` samples when you need explicit IDs (one row per charge, in record order).
* Are synthetic — safe for staging demos
* Also checked into `Theary-AI/quick-start` under `samples/`

Schema reference: [Supported XML Schemas](/xml-schemas).

<AccordionGroup>
  <Accordion title="1. Traffic / not reportable — ScreeningResults">
    Speeding / traffic-style charge. Typical outcome: **Automation** / **NOT\_REPORTABLE**.

    File: `samples/traffic-not-reportable.json`

    ```bash theme={null}
    curl -s "$PR_API_BASE/evaluate" \
      -H "Authorization: Bearer $PR_TOKEN" \
      -H "Content-Type: application/json" \
      --data @samples/traffic-not-reportable.json
    ```
  </Accordion>

  <Accordion title="2. Reportable / auditor — ScreeningResults">
    Recent theft conviction. Typical outcome: **REPORTABLE** with **Auditor** when identity matches.

    File: `samples/reportable-auditor.json`
  </Accordion>

  <Accordion title="3. Insufficient data / validation — ScreeningResults">
    Charge present but disposition empty — incomplete reportability / possible `validation.issues`.

    File: `samples/insufficient-data.json`
  </Accordion>

  <Accordion title="4. JSON resubmit — record_json">
    Corrected mapped criminal JSON. Requires `submission_type: "resubmit"` and sibling `candidate_info`.

    File: `samples/resubmit-record-json.json`

    Guide: [Resubmission Workflow](/guides/resubmission).
  </Accordion>

  <Accordion title="5. BackgroundReportPackage schema">
    Same evaluate contract; XML root `<BackgroundReportPackage>`.

    File: `samples/background-report-package.json`
  </Accordion>

  <Accordion title="6. OrderXML schema">
    Same evaluate contract; XML root `<OrderXML>`.

    File: `samples/order-xml.json`
  </Accordion>

  <Accordion title="7. With cases[] — single charge">
    Same traffic XML as scenario 1, plus full `cases[]` (one row) with your `court_search_id` / `offense_id`.

    File: `samples/with-cases-mapping.json`

    Quickstart: [Optional: map charges with cases\[\]](/quickstart#optional-map-charges-with-cases).
  </Accordion>

  <Accordion title="8. With cases[] — multi-charge (2 courts)">
    Client-style mapping: two cases, five charges; shared `court_search_id` per case; distinct `offense_id` per charge. Synthetic data (no real PII).

    File: `samples/with-cases-multi-charge.json`
  </Accordion>
</AccordionGroup>

***

## Related

* [Quickstart](/quickstart) — auth + first evaluate
* [How It Works](/how-it-works#order--search--evaluate-contract) — one search per call
* [Testing Scenarios](/testing-scenarios) — assertion examples from live-shaped responses
* [Evaluate](/api-reference/endpoints/evaluate) — full field reference