Skip to main content
The search history endpoint returns the screening requests your tenant has run. Use it for audit retrieval: a compliance team can reconcile which screenings ran, when they ran, who ran them where Minerva recorded a user, and which submitted entities and feeds each request included.
Search history retrieval is read-only. It does not submit a new screening, change review status, or modify historical records.

Endpoint

Authenticate with the same API key header the other Minerva API endpoints use:
The API key determines the tenant whose historical requests are returned. Create and manage keys from Administration > Developers in the Minerva dashboard, or see API Keys.

Query parameters

Use RFC3339 date-time values with an explicit timezone, such as 2026-05-01T00:00:00Z. When you build URLs, use your HTTP client’s query parameter encoder, URLSearchParams, or --data-urlencode, so reserved characters such as : and + are encoded safely.

List recent search requests

Retrieve a date range

Date range filters are inclusive and apply to the request’s created_at timestamp.

Example response

Paginate an audit export

For a full audit export, request pages until pagination.has_next is false. Keep the same filters on each page so the result set remains consistent.
JavaScript

Retrieve associated results

The search history response gives you the request metadata and the request identifier. When you need the stored match-level results for a historical request, use the returned id as the request_id on the search matches endpoint.
cURL
The response returns the stored potential match objects. They use the same field layout as a direct search response, so the field descriptions and the recommended analyst review order in the Screening Integration Guide apply to them as well.