Sample Pack

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

Prefer a UI? Load the traffic sample from the quick-start /public-records console (Reset sample), or copy a file from this pack into your client.

Scenario index

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

1. Traffic / not reportable — ScreeningResults

Speeding / traffic-style charge. Typical outcome: Automation / NOT_REPORTABLE.File: samples/traffic-not-reportable.json

curl -s "$PR_API_BASE/evaluate" \
  -H "Authorization: Bearer $PR_TOKEN" \
  -H "Content-Type: application/json" \
  --data @samples/traffic-not-reportable.json

2. Reportable / auditor — ScreeningResults

Recent theft conviction. Typical outcome: REPORTABLE with Auditor when identity matches.File: samples/reportable-auditor.json

3. Insufficient data / validation — ScreeningResults

Charge present but disposition empty — incomplete reportability / possible validation.issues.File: samples/insufficient-data.json

4. JSON resubmit — record_json

Corrected mapped criminal JSON. Requires submission_type: "resubmit" and sibling candidate_info.File: samples/resubmit-record-json.jsonGuide: Resubmission Workflow.

5. BackgroundReportPackage schema

Same evaluate contract; XML root <BackgroundReportPackage>.File: samples/background-report-package.json

6. OrderXML schema

Same evaluate contract; XML root <OrderXML>.File: samples/order-xml.json

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.jsonQuickstart: Optional: map charges with cases[].

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

Quickstart — auth + first evaluate
How It Works — one search per call
Testing Scenarios — assertion examples from live-shaped responses
Evaluate — full field reference

Core Concepts

Guides

Examples

Support

Scenario index

​Scenario index

​Related

Scenario index

Related