JSON API - Report Reference
This page documents the hearing outcome report endpoints. Reports are a separate top-level resource from hearings — a report does not live at a path under /hearings/v1/hearing/{id}, it lives under its own /reports/v1/report resource, addressed by the report's own ID.
It's a companion to JSON API - Hearing Response Reference (which covers hasAppearance and the appearance/attorney objects on the hearing itself) and JSON API - Hearing Attachment Reference (hearing-level attachments — a different thing from report attachments below).
Why you might see an empty list
A report only exists once a covering attorney has actually appeared and submitted their write-up. If you call the list endpoint for a hearing that hasn't happened yet, was canceled, or was covered but the attorney hasn't filed their report, you will correctly get back an empty array — this is not an error and does not mean something is broken on your end or ours. There is currently no field that tells you "no report yet, check back later" versus "this hearing will never have a report" — if that distinction matters for your integration, contact support@docketly.com to discuss your use case.
Endpoints
Method | Endpoint | Scope | What it does |
|---|---|---|---|
|
|
| List available hearing outcome reports |
|
|
| Retrieve a specific report by its own ID |
|
|
| Download a report attachment |
{id} above is the report's own ID (returned in the list response), not the hearing's ID. There is no lookup by hearing ID directly — list reports and match on the hearing reference in each entry, or use the token field from hearing creation to correlate if you set one (see JSON API - Hearing Create Payload Reference).
Authentication
Requires an Authorization header (HTTP Basic, or an OAuth2 Bearer token with reports:read scope) — see the API page for authentication details.
This page is new as of September 2026, written up after a live integration test surfaced that these endpoints existed but were undocumented. Field-level detail on the report object itself (the individual isReport* outcome fields, garnishment/settlement/judgment data, etc.) is not yet fully cataloged here — flag to engineering if you need the complete field list before relying on it.