Search history retrieval is read-only. It does not submit a new screening,
change review status, or modify historical records.
Endpoint
Query parameters
List recent search requests
Retrieve a date range
Date range filters are inclusive and apply to the request’screated_at
timestamp.
Example response
Paginate an audit export
For a full audit export, request pages untilpagination.has_next is false.
Keep the same filters on each page so the result set remains consistent.
JavaScript
What changed since the last run
Monitoring screens each monitored profile again on its cadence. To see what the latest screening found, use thesearchId from the profile_status_updated webhook and list that screening’s unresolved matches:
cURL
suppressed instead of unresolved, and a screening where every match is suppressed sends no webhook. So review_status=unresolved on the latest screening returns the matches that suppression did not treat as repeats. These are usually new findings, plus any repeat that didn’t meet the suppression rules. Treat it as a close approximation, not an exact difference. Suppression is on by default with the Balanced preset, and you configure it per workspace in the Minerva dashboard. If it is off in a workspace, every match in each screening is unresolved, including repeats.
You can also query by profile and time window:
Minerva cannot list matches that disappeared since the previous screening. To
find them, compare the matches of two screenings in your own system.
Monitoring run history
To show that a monitored profile was screened, including screenings that found nothing, list its search requests:cURL
requests[] is one screening request for the profile. A request is recorded for every screening, whether or not it found anything.
- Monitoring screenings carry
config.billable_tagset tomonitoring. Other screenings of the profile, such as the onboarding screening, appear in the same list with a different tag or none. created_atis when the screening was requested.entity_resultsis keyed by the index of each submitted entity, starting at"0". An empty object, such as{"0": {}}, means every feed answered. When a feed did not return a complete answer, the entity’s entry carriesfeed_statuses.<Feed>.statusset topartialorunavailable, andpartial: true. That feed was not fully screened in that run.
cURL
pagination.total_count is the number of matches that screening produced. 0 means it found nothing.
A request has no separate completion time. Use
created_at as the time of the
screening.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 returnedid as the request_id on the search matches endpoint.
cURL
Match IDs
Each stored match carries anid. It is the value you send as match_id to update the match’s review status, so you can save it in your system and record a decision later.
A synchronous POST /v2/search returns the same value on each match as screening_match_id, so you can take the ID straight from the response without reading the matches back. If a match in the response has no screening_match_id, read the request’s matches with GET /v2/search/matches?request_id=<request_id> and use their id values.
- Stable. A match keeps its
idfor as long as it exists. Updating its review status doesn’t change it. - New per screening. A new screening, such as a monitoring rescreen, stores its matches with new IDs and its own
request_id. Minerva never reuses the ID of an earlier match, so if a rescreen finds the same person or entity again, that potential match has a newid. On monitored profiles, repeated alert suppression can mark a match that repeats an earlier finding assuppressed. - Retained. Minerva doesn’t expire stored matches automatically, and archiving a profile doesn’t remove them.
- Not the record ID. A match can also carry
record_id, the data source’s own identifier for the matched record. It isn’t a match ID, so don’t send it asmatch_id.
Results of a synchronous search
When a synchronousPOST /v2/search returns an entity in entity_matches, the matches listed for it are already stored. You can read them with GET /v2/search/matches and the request_id from the same response.
In rare cases Minerva completes the search but can’t store an entity’s matches. That entity’s metadata then includes results_stored: false. The field is absent on normal responses and doesn’t change the status code or any other field. When you see it, that entity’s matches may be missing from GET /v2/search/matches. If you need them stored, run the search again.
An asynchronous search returns a job_id and no entity_matches, which means the search is still running. Read its matches with GET /v2/search/matches and the request_id once the job has completed.