Sex Offender History API Documentation

Endpoint

The History API supports GET / POST. Live API keys require separate Sex Offender History access. Requests must provide exactly one exact Offenders.io identifier and do not support broad name, address, GIS, or date-range search.

Request

Send exactly one of uuid or personUuid, plus an optional positive page. The page defaults to 1.

GET

POST

• uuid pins down one atomic record and expands to connected records when that record has a personUuid.
• personUuid retrieves known atomic records connected to that person identifier.
• page must be a positive integer. Callers cannot set a page size.

Response

History uses the standard { offenders, page, totalPages } response envelope and returns 50 records per page. Records are ordered by createdAt ascending, then uuid ascending.

Each item uses the same public offender field schema documented in the Search API response fields, including its atomic uuid, connecting personUuid, and create-only createdAt. History additionally returns locationHistory. The response is private and is not cached.

locationHistory

locationHistory contains known same-record location episodes when source data supports them. A different ZIP normally appears as a separate atomic record with its own UUID; available same-ZIP changes may appear as ordered episodes inside that record.

Testing API Keys

Testing API keys can call the History endpoint with an exact synthetic UUID or personUuid. They return deterministic synthetic records and never query live registry data. Normal validation and pagination rules still apply.

Access and Limitations

Sex Offender History is controlled access and is enabled per account after an organization and use-case review. It does not grant Search, Extensive, GIS, Facial Recognition, Bulk, or other product entitlements. Review the product overview or request access.