Skip to main content
GET
Get job by ID
This endpoint retrieves detailed information about a job by its ID, including its status, progress, and associated check results.

API Endpoint

Query Parameters

job_id
string
required
The unique identifier of the job to retrieve.
include_check_result_ids
boolean
default:"false"
If true, includes only the IDs of check results. Cannot be used with include_check_results.
include_check_results
boolean
default:"false"
If true, includes full check result objects. Cannot be used with include_check_result_ids.
include_status_messages
boolean
default:"false"
If true, includes status messages associated with the job.
jsonpath_query
string
Optional JSONPath query to filter and extract specific fields from the response. Useful for reducing payload size when include_check_results=true returns large amounts of data. See Filtering Check Results below for examples.

Filtering Check Results

When using include_check_results=true, the response can contain large amounts of data. Use the jsonpath_query parameter to filter and extract only the data you need.

JSONPath Syntax

The API uses JSONPath syntax for filtering. Here are common patterns:
  • Filter by field value: $.check_results[?(@.field=='value')]
  • Get all items: $.check_results[*]
  • Extract specific field: $.check_results[*].field_name
  • Nested field access: $.check_results[*].payload.nested_field

Common Use Cases

Get only the results for a specific check type:
Returns: Array containing only the web presence check result
Filter to see only checks that didn’t pass:
Returns: Array of failed check results
Get just the payload type from all check results:
Returns: Array of payload type strings (e.g., ["WebPresenceCheckResult", "PolicyCheckResult"])
Extract specific nested fields from check result payloads:
Returns: Array of hit names from the verified_hits array (e.g., ["LinkedIn", "Crunchbase"])
Get all completed checks:
Returns: Array of completed check results

Adverse Media Filtering Examples

For detailed adverse media structure, see the Adverse Media Screening Check documentation.
Retrieve all verified adverse media hits for a job:
Returns: Array of all adverse media profiles found
Filter for articles where the business is identified as the perpetrator:
Returns: Array of weblinks where is_perpetrator is true
Filter for articles from Google Search only:
Returns: Array of weblinks from Google SearchOther sources: refinitiv_world_check, comply_advantage, serp_google_news, serp_brave_search
Filter for articles about regulatory violations:
Returns: Array of weblinks with “Regulatory Violations” in topicsCommon topics: “Legal Disputes”, “Compliance Issues”, “Safety Issues”, “Financial Misconduct”, “Criminal Activity”
Extract just the article titles and URLs:
Returns: Array of objects with only title and url fields
Filter for articles published in 2024 or later:
Returns: Array of weblinks published in 2024 or later
Get summaries for articles from a specific country:
Returns: Array of event summaries for articles from the United States
Extract all direct quotes about the business:
Returns: Array of direct quotes from adverse media articles

Python Example

Error Handling

400 Bad Request
object
Returned when the JSONPath query has invalid syntax.
404 Not Found
object
Returned when the JSONPath query returns no results.
JSONPath Resources:

Response

id
string
The unique identifier for the job.
agent_id
string
The ID of the agent that executed the job.
owner_id
string
The email address of the job owner.
status
string
The current status of the job (e.g., PENDING, RUNNING, COMPLETED, FAILED, RETRIED). If the status is RETRIED, it means this job instance was superseded by a new job. You should use the new_job_id to fetch the latest job information.
started_at
string
The timestamp when the job started.
completed_at
string
The timestamp when the job completed.
recommendation
string
The recommendation based on the job results.
input_payload
object
The input data provided for the job.
status_messages
array
An array of status messages associated with the job.
new_job_id
string
The unique identifier of the new job that was created as a retry of this job. This field is present only if the status is RETRIED.
original_job_id
string
The unique identifier of the original job that this job is a retry of. This field is present if this job was created as a retry of a previous job.
check_results
array
An array of check results from the job execution.

Usage Examples

Example Response

Notes

The include_check_result_ids and include_check_results parameters are mutually exclusive. Using both will result in a 400 Bad Request error.
Access to job details is restricted. The API will return a 401 Unauthorized error if the user doesn’t have access to the specified agent.
If the job is not found, a 404 Not Found error will be returned.
This endpoint provides a comprehensive view of a job’s status and results, allowing for detailed tracking and analysis of the KYB/KYC process.

Error Responses

400 Bad Request
object
error
string
“Cannot include both check result ids and check results in the response”
401 Unauthorized
object
error
string
“Unauthorized”
404 Not Found
object
error
string
“Job not found”

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
include_check_result_ids
boolean
include_check_results
boolean
include_status_messages
boolean

Response

Job retrieved successfully