- Run a PEP and sanctions screening job
Runs a PEP and sanctions screening job.
- Mock serverhttps://docs.bndry.net/_mock/apis/openapi/v1alpha/entities/{entity}/pepSanctionIndividualEntityJobs/{pepSanctionIndividualEntityJob}:run
- BNDRY APIhttps://api.bndry.app/v1alpha/entities/{entity}/pepSanctionIndividualEntityJobs/{pepSanctionIndividualEntityJob}:run
- oauth2_client_credentials
- oauth2_authorization_code
curl -i -X POST \
'https://docs.bndry.net/_mock/apis/openapi/v1alpha/entities/{entity}/pepSanctionIndividualEntityJobs/{pepSanctionIndividualEntityJob}:run' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Success
This resource represents a long-running operation that is the result of a network API call.
The server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the name should be a resource name ending with operations/{unique_id}.
Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
If the value is false, it means the operation is still in progress. If true, the operation is completed, and either error or response is available.
- error
- response
{ "name": "string", "metadata": { "type": "string", "value": "string" }, "done": true, "error": { "code": 0, "message": "string", "details": [ … ] } }