Run a check
Run Check
Execute a specific check for KYB or KYC processes
POST
Run a check
This endpoint allows you to run a specific check for either Know Your Business (KYB) or Know Your Customer (KYC) processes.
Conflict (409 Conflict) if
This endpoint runs a specific check with the provided parameters. The response includes a check job ID that can be used to track the progress and retrieve results of the check.
API Endpoint
Request Body
The unique identifier for the agent to be used for the check.
The identifier of the specific check you want to run.
Optional. A unique identifier (UUID) that you can provide for this check job.
If provided, this ID will be used as an idempotency key.
If a job with this ID already exists, the API will return a
409 Conflict error, and you can then use this job_id to retrieve the existing check job’s status and results using an appropriate endpoint (e.g., /getJobById or a check-specific status endpoint if available).
If not provided, a new unique ID will be automatically generated for the check job.The KYB schema containing the information for business verification checks.
The KYC schema containing the information for individual verification checks.
An optional URL to receive webhook notifications about the check status.
Optional arguments specific to the check being run.
Response
The unique identifier for the created check job.
The current status of the check job (e.g., “PENDING”, “RUNNING”, “COMPLETE”).
The timestamp when the check job was created.
The timestamp when the check job was last updated.
The ID of the agent used for this check.
The input payload provided for the check job.
Example Request
Example Response
Successful creation (200 OK):job_id already exists:
Implementation Details
TherunCheck endpoint is implemented in the shared_router.py file. Here’s a brief overview of the implementation:
- The endpoint uses the
get_check_schemadependency to parse and validate the incoming request data. - It then calls the
celery_enqueue_run_checkfunction, which handles the logic for running a single check. - The function checks if the user has access to the requested agent and validates the check configuration.
- If everything is valid, it enqueues the check job using Celery.
- Finally, it returns a JSON response with the check job details.
shared_router.py file in the Parcha backend codebase.
Available Checks
Here are some of the available checks that can be run using this endpoint:kyb.web_presence_check: Verifies the online presence of a business.kyb.business_registration_check: Checks the registration status of a business.kyc.identity_verification: Verifies the identity of an individual.kyc.adverse_media_check: Searches for any negative media coverage related to an individual.
The available checks may vary depending on your subscription level and the specific agent you’re using. Consult the Parcha documentation or contact support for a complete list of checks available to you.
Best Practices
- Choose the right check: Make sure you’re using the appropriate check for your use case (KYB or KYC).
- Provide comprehensive data: The more details you provide in the payload, the more thorough and accurate the check can be.
- Use webhooks: Setting up a
webhook_urlallows you to receive real-time updates about your check progress. - Handle errors gracefully: Be prepared to handle potential errors or edge cases in your application.
- Respect rate limits: Be mindful of any rate limits on the API to ensure smooth operation of your integration.
runCheck endpoint to perform specific checks as part of your KYB or KYC processes.Authorizations
API key obtained from your Parcha account settings. Include as Bearer token in the Authorization header.
Body
application/json
Response
Check started successfully