Skip to main content
GET
Batch Search Results API

Authorizations

x-api-key
string
header
required

The Minerva API key used for this integration. Manage API keys in the Minerva dashboard under Administration > Developers.

Path Parameters

jobid
string<uuid>
required

The job ID of a former search submission to the search POST endpoint.

Response

The job id was valid, and either the status or the full search results are returned.

Automatic Disposition (New): when the workspace that submitted the batch has Automatic Disposition enabled with the Direct API channel turned on, Minerva analyzes every screened potential match in a row's results[] - one carrying at least one risk flag (Sanctions, PEP, News, Criminal, Legal, and so on) in checklist.screen - before that row completes, which can add a few seconds per screened entity to row completion. The same rows are returned by POST /v1/searchStatus.

  • review_status changes only in Full Auto Mode: a prediction that meets the configured confidence threshold sets true_positive or false_positive, and the applied prediction is returned in automatic_disposition.
  • In Hint Mode the prediction is returned in disposition_hint and review_status stays unresolved - the annotation is advisory, for your integration to interpret in real time.
  • An analysis that completes without meeting a threshold returns disposition_hint with prediction: "undetermined" and the match stays unresolved.

Clean matches and workspaces without the feature enabled never carry these fields. The default response example shows annotated matches. Opt the whole job out at submission by sending the X-Minerva-Automatic-Disposition: skip header on POST /v1/search (inert unless the feature is enabled for the workspace), and see the Automatic Disposition Guide for consuming these fields in an integration.

status
integer
Example:

200

response
enum<string>

The current status of the batch search job

Available options:
complete,
pending,
error
Example:

"complete"

submitted
integer

Total number of search requests submitted in the batch

Example:

42

completed
integer

Number of search requests completed so far

Example:

42

results
object[]

Array of search results (only present when response is "complete")