Skip to main content
GET
Get a specific check result from 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)
For the overall job status and all check results, use getJobById with include_check_results=true instead.

Parameters

string
required
The unique identifier of the job. You receive this when you start a job or from a webhook notification.
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
This is the stable check identifier, not command_instance_id which changes with each job run.
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.
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.
string
required
The type of the case. Use "kyb" for business checks or "kyc" for individual checks.
boolean
default:"true"
Whether to include status messages showing the check’s progress history in the response.

Response

array
An array of source identifiers used in the check.
object
The full check result object. Structure may vary based on the type of check.

Error Responses

string
A description of the error that occurred.

Example Request

Example Response

Authorizations

Authorization
string
header
required

API key obtained from your Parcha account settings. Include as Bearer token in the Authorization header.

Query Parameters

job_id
string
required

The unique identifier of the job

agent_instance_id
string
required

The unique identifier of the agent instance

check_id
string
required

The unique identifier of the check

case_type
enum<string>
required

The type of the case

Available options:
kyb,
kyc,
entity
include_status_messages
boolean
default:true

Whether to include status messages in the response

Response

Check result retrieved successfully