Location monitoring

Watch a radius around an address

A location monitor stands watch over a place rather than a person. You give it an address (or coordinates) and a radius, and each day it evaluates which matching records fall inside that radius — alerting you as records move in (new), change while inside it (changed), or move out or come off a registry (removed).

{
  "product": "sex-offender",
  "type": "location",
  "location": { "address": "100 Main St, Austin, TX 78701", "radiusMiles": 1 },
  "channels": { "email": "alerts@example.com" }
}

You can specify the centre either as an address string or as explicit lat/lng coordinates. radiusMiles is required.

{
  "product": "sex-offender",
  "type": "location",
  "location": { "lat": 30.2711, "lng": -97.7437, "radiusMiles": 2 },
  "channels": { "email": "alerts@example.com", "webhookUrl": "https://example.com/hooks/os" }
}

Coverage

Criminal location monitoring is coming soon

Criminal-record location monitoring will arrive as location coverage across criminal records expands. It is documented here so you can plan for it, but it is not billable yet. A POST /v1/monitors with product: "criminal" and type: "location" does not error — it returns a not_yet_available acknowledgement, so your integration can handle the transition without special-casing an error path.

// POST /v1/monitors  {"product":"criminal","type":"location", …}
{
  "status": "not_yet_available",
  "product": "criminal",
  "type": "location",
  "message": "criminal location monitoring is coming soon; no monitor was created and nothing was billed"
}

The address you register

The centre of a location monitor is the subscriber’s own input. It is stored encrypted, isolated to your account, and audit-logged, and it is used for one purpose only: to evaluate proximity each day. See Access, keys & data handling.

Not a consumer report

A location monitor’s alerts are not a consumer report and may not be used for any FCRA-covered decision. The legal notice accompanies every alert.