For a deeper look into our World Check One API, look into:
Ongoing Screening Scenario using both WC1 Saas and API ?
Hello,
I would like to check if the following scenario mixing both WC1 SaaS and API can be used :
- Batch Upload is done via World-Check One SaaS; OGS is enabled for a subgroup also from World-Check One SaaS (Web access).
- Request the OGS Updates for the subgroup, if any, via the World-Check One API (using SEQ 9) ?
Best Regards
Nabil
- Batch Upload is done via World-Check One SaaS; OGS is enabled for a subgroup also from World-Check One SaaS (Web access).
- - OGS can be enabled for a particular batch associated to a group/subgroup, so you first create a batch for a group/subgroup followed by which you will proceed to screening page select screening type as Batch and then enable the “Screen and OGS” option. OGS cannot be enabled for a subgroup but for the batch file itself.testbatchpng.png
- Request the OGS Updates for the subgroup, if any, via the World-Check One API (using SEQ 9) ?
- -Whenever there are any OGS updates they can be requested via World-Check One API using seq9 but the parameter that the request depends on is the date range and not groups and they will come in with respect to a particular user and not group/subgroup and there are cases created for even a single batch in the case manager.
Request-Seq9- { {protocol}}{ {gateway-host}}{ {gateway-url}}cases/ongoingScreeningUpdates
Body- { "query": "updateDate>='{ {weekAgo}}'" }
Kindly refer the below page for any further guidelines related to batch screening.
https://world-check-one-pilot.accelus.com/1.365.1//js/fsp/view/resources/assets/batch-file-screening-guidelines.pdf