> ## Documentation Index > Fetch the complete documentation index at: https://docs.gominerva.com/llms.txt > Use this file to discover all available pages before exploring further. # Send an API result to a user > Send a completed API result to a named user's investigation bin in the Minerva user interface for manual review. Use this endpoint when your onboarding flow includes a manual review step, or when you want a specific API result inspected more closely. Assign results after the search completes, using the Search and Search Status APIs. The Search Status API response body contains the job and request IDs this endpoint needs. The user's email address in Minerva identifies the recipient. The recipient must be in the same organization as the API key that submitted the search. If the investigation does not exist, Minerva creates it as a bin in that user's account to hold the API result. ## OpenAPI ````yaml /api-reference/core.json post /v1/sendAPIResultToUser openapi: 3.0.0 info: version: 1.6.2 title: MinervaAI Core API description: >- The Minerva core monolith, which provides search, consensus, pruning, and report generation. servers: - url: https://api.gominerva.com description: The production API server for Minerva. security: - ApiKeyAuth: [] tags: - name: Search description: >- Current screening, search, and reporting endpoints for active integrations. - name: Legacy description: >- Legacy endpoints retained for backwards compatibility. Prefer the canonical POST-based search flows for new integrations. - name: API to UI Integration description: Endpoints used to bridge API integrations with Minerva UI workflows. - name: Potential Matches description: Update review workflow state for potential matches returned by searches. paths: /v1/sendAPIResultToUser: post: tags: - API to UI Integration summary: Send an API result to a user description: > Send a completed API result to a named user's investigation bin in the Minerva user interface for manual review. Use this endpoint when your onboarding flow includes a manual review step, or when you want a specific API result inspected more closely. Assign results after the search completes, using the Search and Search Status APIs. The Search Status API response body contains the job and request IDs this endpoint needs. The user's email address in Minerva identifies the recipient. The recipient must be in the same organization as the API key that submitted the search. If the investigation does not exist, Minerva creates it as a bin in that user's account to hold the API result. requestBody: required: true content: application/json: schema: type: object required: - jobId - requestId properties: investigationId: type: string maxLength: 36 description: >- If an earlier call to `/sendAPIResultToUser` created an investigation, provide its `investigationId` to assign the result to it. Provide either `investigationName` or `investigationId`. example: existing-investigation-id investigationName: type: string maxLength: 1024 description: >- The plain text label of the investigation this result belongs under. If the label does not exist in the user's investigation list, Minerva creates it; otherwise the investigation matching the label receives the result. The investigation date matches the date the API result was generated. Use a label that is easy for the receiving investigator to identify, such as a date or specific batch metadata. example: My Investigation Name jobId: type: string maxLength: 36 description: >- The unique ID of the job the result ran under. This is the same ID used to query the API result through the Search Status API, and it also appears in the Search Status API response body. example: job-id-of-api-result requestId: type: string maxLength: 36 description: >- The unique ID of the request the result ran under. Each result in a Search Status API batch carries an `id` that uniquely identifies that result within the job. example: request-id-of-api-result userEmail: type: string maxLength: 256 description: >- The email address of the user who should receive the API result in one of their investigation bins. If omitted, the result is assigned to the requesting user. example: user@myorganization.com example: investigationName: My New Investigation jobId: previous-api-call-job-id requestId: previous-api-call-request-id userEmail: user@myorganization.com responses: '200': description: API result successfully cloned into user investigation. content: application/json: schema: type: object properties: investigationId: type: string description: >- The unique identifier of the investigation that contains the API result. example: unique-id-of-the-investigation status: type: integer example: 200 message: type: string example: API result successfully cloned into user investigation. code: type: string example: success '400': description: > Bad Request: the request format does not match the required schema. Check your JSON body formatting and refer to the schema above for allowed fields. content: application/json: schema: type: object properties: status: type: integer example: 400 message: type: string example: Empty or invalid body '403': description: > Forbidden: authentication failed because: - The API key was invalid - A server-side safety check judged the request data unsafe, usually because it contained script/code tags or injection motifs - Your account would overrun a hard quota if this call is made content: application/json: schema: type: object properties: status: type: integer example: 403 message: type: string example: Missing x-api-key header. '404': description: > Not Found: no user with that email address exists in the same organization as the API user that submitted the request. content: application/json: schema: type: object properties: status: type: integer example: 404 message: type: string example: User not found in the same organization '500': description: > Internal Server Error: something went wrong on the Minerva server while completing this task, so it did not complete. Contact support@gominerva.com with reproduction notes so we can resolve it. content: application/json: schema: type: object properties: status: type: integer example: 500 message: type: string example: >- Internal server error occurred while processing the request security: - ApiKeyAuth: [] components: securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- The Minerva API key used for this integration. Manage API keys in the Minerva dashboard under Administration > Developers. ````