> ## Documentation Index
> Fetch the complete documentation index at: https://docs.parcha.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Specific Check Result

> Retrieve the result of a specific check from a job

This endpoint retrieves the full result of a specific check from a completed job, including all evidence and detailed findings.

## Endpoint

`GET /getCheckResultFromJob`

## When to Use This Endpoint

Use this endpoint when you need to:

* Fetch the complete result for a specific check (e.g., sanctions screening, PEP check)
* Get evidence and detailed findings that may not be included in the standard job response
* Retrieve results for a specific entity in a multi-entity job (like KYB jobs with associated individuals)

<Tip>
  For the overall job status and all check results, use [`getJobById`](/api-reference/getJobById) with `include_check_results=true` instead.
</Tip>

## Parameters

<ParamField query="job_id" type="string" required>
  The unique identifier of the job. You receive this when you start a job or from a webhook notification.
</ParamField>

<ParamField query="check_id" type="string" required>
  The check type identifier (also called `command_id`). This identifies **which type of check** to retrieve.

  Examples:

  * `kyb.sanctions_screening_check_v2`
  * `kyb.adverse_media_screening_check_v2`
  * `kyc.pep_screening_check_v2`
  * `kyb.incorporation_document_verification`

  <Note>
    This is the stable check identifier, not `command_instance_id` which changes with each job run.
  </Note>
</ParamField>

<ParamField query="agent_instance_id" type="string" required>
  Identifies **which entity** the check was run against. This is especially important for jobs that process multiple entities (e.g., a business with associated individuals).

  You can find this value in the check results from `getJobById` response as `agent_instance_id`.

  <Note>
    For single-entity jobs, all checks will have the same `agent_instance_id`. For multi-entity jobs (like KYB with associated individuals), each entity will have its own `agent_instance_id`.
  </Note>
</ParamField>

<ParamField query="case_type" type="string" required>
  The type of the case. Use `"kyb"` for business checks or `"kyc"` for individual checks.
</ParamField>

<ParamField query="include_status_messages" type="boolean" default="true">
  Whether to include status messages showing the check's progress history in the response.
</ParamField>

## Response

<ResponseField name="sources" type="array">
  An array of source identifiers used in the check.
</ResponseField>

<ResponseField name="..." type="object">
  The full check result object. Structure may vary based on the type of check.
</ResponseField>

## Error Responses

<ResponseField name="error" type="string">
  A description of the error that occurred.
</ResponseField>

| Status Code | Description                   |
| ----------- | ----------------------------- |
| 404         | Job or check result not found |
| 403         | Unauthorized access to agent  |
| 500         | Internal server error         |

## Example Request

```bash theme={null}
curl -X GET 'https://api.parcha.ai/api/v1/getCheckResultFromJob?job_id=e85e0cc4-b1e8-40b0-9a3d-83c328eee0f4&check_id=kyb.sanctions_screening_check_v2&agent_instance_id=09e3133959c447b493313b1b3360cc05&case_type=kyb' \
-H 'Authorization: Bearer YOUR_API_KEY'
```

## Example Response

```json theme={null}
{
  "command_id": "kyb.sanctions_screening_check_v2",
  "command_name": "KYB Sanctions Screening Check",
  "command_desc": "Tool used to screen a business against sanctions watchlists",
  "command_instance_id": "a5494583409b41d587cd753b686bcf43",
  "agent_instance_id": "09e3133959c447b493313b1b3360cc05",
  "status": "complete",
  "output": {
    "explanation": "The business was screened against multiple sanctions databases and no matches were found.",
    "payload": {
      "type": "SanctionsWatchlistScreeningCheckResult",
      "verified_sanctions_hits": [],
      "passed": true
    },
    "passed": true,
    "answer": "No sanctions matches found for this business.",
    "recommendation": null,
    "alerts": {}
  },
  "evidence": [
    {
      "source": "OFAC SDN List",
      "searched_name": "Parcha Labs Inc",
      "match_count": 0
    }
  ],
  "sources": ["OFAC SDN", "UN Sanctions", "EU Consolidated List"],
  "created_at": "2023-06-15T10:30:00Z",
  "updated_at": "2023-06-15T10:35:00Z"
}
```


## OpenAPI

````yaml GET /getCheckResultFromJob
openapi: 3.0.0
info:
  title: Parcha API
  version: 1.0.0
  description: API for managing Parcha jobs and checks
servers:
  - url: https://api.parcha.ai/api/v1
    description: Agent Hub API server
  - url: https://demo.parcha.ai/api/v1
    description: Sandbox API server
  - url: https://us1.parcha.ai/api/v1
    description: Legacy API server
  - url: http://{your-company-domain}.parcha.ai/api/v1
    description: Custom Enterpris server (your company's API server)
security:
  - bearerAuth: []
paths:
  /getCheckResultFromJob:
    get:
      summary: Get a specific check result from job
      description: Retrieve the result of a specific check from a job
      parameters:
        - name: job_id
          in: query
          required: true
          schema:
            type: string
          description: The unique identifier of the job
        - name: agent_instance_id
          in: query
          required: true
          schema:
            type: string
          description: The unique identifier of the agent instance
        - name: check_id
          in: query
          required: true
          schema:
            type: string
          description: The unique identifier of the check
        - name: case_type
          in: query
          required: true
          schema:
            type: string
            enum:
              - kyb
              - kyc
              - entity
          description: The type of the case
        - name: include_status_messages
          in: query
          schema:
            type: boolean
            default: true
          description: Whether to include status messages in the response
      responses:
        '200':
          description: Check result retrieved successfully
        '403':
          description: Unauthorized access to agent
        '404':
          description: Job or check result not found
        '500':
          description: Internal server error
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        API key obtained from your Parcha account settings. Include as Bearer
        token in the Authorization header.

````