How do I check several caseId at the same time for updates?

We are using Python requests on this API https://docs-developers.refinitiv.com/1600949101673/50009/documentation/schema-reference/wc1-api-schema-reference-documentation.html

Screening new users work fine with POST on /cases/screeningRequest we get results and save the caseId in our own database for future references.

What I can't figure out is how do I should use the caseId to recheck if users have any new results since signing up. The plans is to do this with a scheduled cronjob and we want to send in a long list of several caseId in one POST so we get a list of several users new result for more effectively updating our database.


Best Answer

Answers

  • johan
    johan Newcomer

    I think I got things working on my end now but I can only get this

    {
        "query": "updateDate>='2021-02-15T00:00:00Z'",
        "sort": [
            {
                "columnName": "updateDate",
                "order": "DESCENDING"
            }
        ],
        "totalResultCount": 0,
        "pagination": {
            "currentPage": 1,
            "itemsPerPage": 50,
            "totalItems": 0
        },
        "results": []
    }

    Is there any fake names that get constantly updated so we can test our ongoing monitoring system?

  • @johan,

    There are no fake names for the ongoing screening. You can create few dummy cases with common name, and set it to OGS. You should get the OGS update as and when available.

  • johan
    johan Newcomer

    Is the caseSystemId I get from ongoing screening always the same I get from when I first do cases/screeningRequest ? I am using a development database that gets purged on a regular basis and I have lost all old caseSystemId that I get results for when I call cases/ongoingScreeningUpdates.

    It seems like I get a new caseSystemId when I create a new user with the same name that gives results and screen for the first time.

  • johan
    johan Newcomer

    I think I figured out how to put things together but I have not been able to confirm that I am right because systemCaseId I get when screening for the first time differ from systemCaseId I get when I get updates from screening.

  • johan
    johan Newcomer

    Is there a way to do a hard reset on my refinitiv test environment?

  • johan
    johan Newcomer

    I try deleting the old caseSystemId with

    DELETE /cases/{caseSystemId}/ongoingScreening

    But I still get results on it when I do

    POST /cases/ongoingScreeningUpdates
  • @johan,

    Can you please elaborate? What exactly do you mean by hard reset in the environment?

  • @johan,

    Can you please confirm when was the case disabled for OGS? and the query which you are using for Monitor Ongoing screening updates?

  • @johan,

    Each case will have a unique caseSystemId linked to it. You can create multiple cases with the same name. The caseId and the caseSystemId will be different for each screened entity.