Skip to content

// multido api

Every record.
One API.

Arrest, booking, court and custody data from official sources, as JSON over HTTPS. Every record names its source.

api.multido.co
auth
Bearer key, scoped to your organization
provenance
Source and agency on every record
pagination
Cursor-based, stable ordering
push
Signed webhooks, or poll /changes

// quickstart

Three calls to your first record.

  1. 01

    Get a key

    Organization admins create keys in the Tempo console. They start with rg_live_ and are shown once. A key reads only what your organization sees.

  2. 02

    Check coverage

    GET /sources lists what your key covers, how often each source is collected and whether it is on time.

  3. 03

    Read records, follow the cursor

    Every record names its source. List endpoints return next_cursor until the last page.

Base URL api.multido.co/api/v1
Authorization: Bearer $MULTIDO_KEY
X-Api-Key is accepted too

shell
export MULTIDO_KEY=rg_live_...
B=https://api.multido.co/api/v1
# 1. What does this key cover, and is each source on time?
curl $B/sources \
-H "Authorization: Bearer $MULTIDO_KEY"
# 2. Read arrests, newest first
curl -G $B/arrests \
-H "Authorization: Bearer $MULTIDO_KEY" \
-d limit=25 -d since=2026-11-01T00:00:00Z
# 3. Follow the cursor until next_cursor is null
curl -G $B/arrests \
-H "Authorization: Bearer $MULTIDO_KEY" \
-d limit=25 -d since=2026-11-01T00:00:00Z \
-d cursor=$NEXT_CURSOR

Example data. The person, case numbers and ids are fictional.

// reference

Endpoints.

Base URL api.multido.co/api/v1. Results are paginated by cursor. A key can read only the sources your organization sees. Datasets can be scoped per key.

01 /

Records

GET

/arrests

Arrests, newest first. Filter by since, until, source and q.

GET

/court-records

Court cases and hearings as the court publishes them.

GET

/correctional-records

Jail intakes and rosters, with custody status.

02 /

Bookings

GET

/bookings/{id}

The arrest and jail intake merged: custody, charges, bond, court dates.

GET

/bookings/lookup

By arrest_number or jail_intake_id. Exact match.

03 /

Radio, incidents and files

GET

/calls

Radio transmissions with transcript and audio link.

GET

/systems

The radio systems your key can read.

GET

/incidents

Incidents, newest first.

GET

/files

Files in your organization, with /files/{id}/download.

04 /

Sources and sync

GET

/sources

Every source your key covers: agency, cadence, health.

GET

/changes

Every field-level change, as a cursor feed. after=latest starts at now.

GET

/withdrawals

Expunged or sealed records to delete downstream.

// on every response

The source is part of the record, not a footnote.

Pick a field to see where it sits in the record.

GET /api/v1/arrests/12:2204871
{
"data": {
"id": "12:2204871",
"dataset": "arrests",
"source": {
"key": "meck_sheriff_arrests",
"name": "Mecklenburg Sheriff arrest records",
"agency": "Mecklenburg County Sheriff's Office"
},
"booking_id": "arrest:2204871",
"booking_number": "2204871",
"arrested_at": "2026-11-07T00:00:00.000Z",
"full_name": "MARSH, ELENA RUTH",
"sex": "F",
"sex_label": "Female",
"sex_raw": "FEMALE",
"race": "W",
"race_label": "White",
"race_raw": "WHITE",
"date_of_birth": "1988-06-02",
"charges": [
{
"description": "LARCENY - MISDEMEANOR",
"case_number": "26CR331204",
"bond_type": "SECURED",
"bond_type_label": "Secured",
"bond_type_raw": "SEC",
"bond_amount": 1500
}
],
"charge_count": 1,
"bond_total": 1500,
"first_seen_at": "2026-11-07T14:11:09.402Z",
"last_changed_at": "2026-11-07T14:11:09.402Z"
}
}

// pagination

Cursors, in a stable order.

List endpoints return next_cursor. Pass it back as cursor to get the next page. When it is null, you have everything. Cursors are opaque: store them, do not build them.

Filter any list with since, until, source and q (name, arrest number or agency person id). limit is 1 to 500; there is no offset and no total count.

page 1
GET /api/v1/arrests?limit=2
{
"data": [
{ "id": "12:2204871", "full_name": "MARSH, ELENA RUTH", ... },
{ "id": "12:2204866", "full_name": "...", ... }
],
"next_cursor": "eyJ2IjoxLCJrIjpb...",
"has_more": true
}
page 2, last page
GET /api/v1/arrests?limit=2&cursor=eyJ2IjoxLCJrIjpb...
{
"data": [
{ "id": "12:2204859", ... }
],
"next_cursor": null,
"has_more": false
}
filter by name
curl -G https://api.multido.co/api/v1/arrests \
-H "Authorization: Bearer $MULTIDO_KEY" \
--data-urlencode "q=MARSH" -d limit=25

// webhooks

Push, in place of polling.

Add an endpoint in the Tempo console and receive an HTTPS POST when records are created, changed or withdrawn. GET /changes carries the same changes as a feed if you would rather pull.

01 /

Add an endpoint

In the Tempo console, choose the event types and datasets. Each endpoint gets its own whsec_ signing secret.

02 /

Record changes

A collection run creates, updates or withdraws a record. The event is sent within about 2 minutes.

03 /

POST to your URL

Signed with Tempo-Signature. Reply 2xx within 10 seconds. Failures retry at 1 min, 5 min, 30 min, 2 h and 6 h.

Event types

record.created
A new record was collected.
record.updated
Fields changed in one collection run. Carries changes[] with old and new values and codes.
record.withdrawn
A record was removed, usually by an expungement or sealing order. Delete your copy.
webhook.test
You pressed Send test event.

Events carry ids and the changed fields, not the full record. Fetch it from the dataset endpoint. Delivery is at least once: dedupe on id.

what your endpoint receives
POST /multido/webhooks HTTP/1.1
Content-Type: application/json
User-Agent: Tempo-Webhooks/1
Tempo-Event-Id: evt_2c1d9a4f0b7e4a8c9d1e
Tempo-Event-Type: record.updated
Tempo-Signature: t=1792300800,v1=5f1c0e1b9d3a7c2e...
{
"id": "evt_2c1d9a4f0b7e4a8c9d1e",
"type": "record.updated",
"created_at": "2026-11-09T21:15:40.000Z",
"data": {
"dataset": "correctional",
"record_id": "70:26-118684",
"source": "meck_sheriff_inmates",
"changes": [
{
"field": "custodyStatus",
"old_value": "In custody", "new_value": "Released",
"old_code": "IN", "old_label": "In custody",
"new_code": "RELEASED", "new_label": "Released"
}
]
}
}
verify the signature
// Tempo-Signature: t=<unix seconds>,v1=<hex>
// v1 = HMAC-SHA256 of "{t}.{raw body}", keyed with the endpoint secret (whsec_...)
import crypto from "node:crypto";
function verify(rawBody: string, header: string, secret: string) {
const p = Object.fromEntries(header.split(",").map((s) => s.split("=")));
if (Math.abs(Date.now() / 1000 - Number(p.t)) > 300) return false; // older than 5 min
const want = crypto.createHmac("sha256", secret).update(p.t + "." + rawBody).digest("hex");
return crypto.timingSafeEqual(Buffer.from(want), Buffer.from(p.v1));
}

After 50 failed deliveries in a row an endpoint is disabled until you re-enable it. Rotating a secret keeps the old one valid for 24 hours.

// errors and limits

Plain status codes.

400

invalid_request

A parameter is malformed or out of range.

400

invalid_cursor

Cursor reused with different filters, or malformed.

401

invalid_api_key

Missing, mistyped or revoked key.

403

scope_missing

The key is not scoped for this dataset.

404

not_found

No such record, or not visible to your key.

409

ambiguous

A booking lookup matched more than one agency.

429

rate_limited

Per-key limit. Wait Retry-After seconds.

429

api_quota_exceeded

Monthly organization quota used up.

500

internal_error

Retry with backoff.

Rate-limit headers

  • RateLimit-Limit
  • RateLimit-Remaining
  • RateLimit-Reset
  • Retry-After
  • X-RateLimit-Limit (monthly)
  • X-RateLimit-Remaining (monthly)

1,000 requests per minute per key by default, up to 3,000. The monthly organization quota depends on your plan.

400, bad cursor
HTTP/1.1 400 Bad Request
{
"error": "invalid_cursor",
"message": "The cursor is malformed or was issued for a different query.",
"status": 400
}
429, per-key limit
HTTP/1.1 429 Too Many Requests
Retry-After: 41
RateLimit-Limit: 1000
RateLimit-Remaining: 0
RateLimit-Reset: 41
{
"error": "rate_limited",
"message": "Rate limit of 1000 requests per minute per key exceeded.",
"status": 429
}

Every error has the same shape. Branch on error, not message.

Request API access.

Tell us the regions and record types you need. We will confirm coverage and set up your organization.

Multido data is not a consumer report and may not be used to make employment, tenancy, credit or insurance decisions, or for any purpose governed by the Fair Credit Reporting Act. API terms apply.