Generate PDF Report
Generate PDF reports as evidence that screening in Minerva was completed. The recommended workflow is to pass a single searchResultId from a previous POST /v1/search-sync response or from a batch result returned by POST /v1/searchStatus or GET /v1/search/{jobid}. For batch results, use the entity-scoped searchId value returned in each result row, such as <requestId>_0. Legacy results and id payloads are still supported for older integrations.
Authorizations
The Minerva API key used for this integration. Manage API keys in the Minerva dashboard under Administration > Developers.
Body
- Option 1
- Option 2
- Option 3
Recommended. Pass the searchId returned by POST /v1/search-sync, or a result-level searchId returned by POST /v1/searchStatus or GET /v1/search/{jobid}. A plain 24-character request id is treated as the first entity in that request; entity-scoped batch ids use the <requestId>_<entityIndex> format.
"69ba0b732908cb3209647d36"
Legacy bulk input. Provide one or more result IDs from POST /v1/searchStatus or GET /v1/search/{jobid} to generate multiple reports in a single request.
Potential match index to include in the PDF. Defaults to 0 when omitted. When using the recommended searchResultId flow, pass a single integer. Legacy bulk requests may also pass an array aligned with results.
0
Legacy job ID fallback from the original POST /v1/search submission. If you omit searchResultId, Minerva can still resolve the matching request from this job ID.
"25e15c07-1322-4364-a26e-2a6ef25c81d4"