Skip to main content
Use the search history endpoint to retrieve screening/search request metadata that was created in Minerva for your tenant. This endpoint is intended for audit-purpose search history retrieval: it helps compliance teams reconcile which screenings were run, when they were run, who ran them when that user context is available, and which submitted entities and feeds were 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 used by the other Minerva API endpoints:
The API key determines the tenant whose historical requests are returned. API keys are managed from Administration > Developers in the Minerva dashboard.

Query Parameters

Use RFC3339 date-time values with an explicit timezone, such as 2026-05-01T00:00:00Z. When building 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

Paginating 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

Retrieving 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