402 Bad Request on Case Resolution

mkalgren

Hello all,

I am receiving an error when attempting to run the Resolve Results API call. The response I get from both Postman and my application code states that the request is bad and "Resolution of results request has failed, please check that all required fields are supplied and valid."

Here is a sample of the JSON I am sending:

{
    "reasonId": "0a3687d0-611f-16a6-984b-1dc60000022c",
    "resolutionRemark": "",
    "resultIds": [
        "0a3687d0-693a-1627-9a69-6256013e83e4"
    ],
    "riskId": "0a3687d0-611f-16a6-984b-1dc600000230",
    "statusId": "0a3687d0-611f-16a6-984b-1dc600000231"
}

I noticed this did not exactly match the format provided in the Postman collection, so I attempted to resend the same data with the same JToken order provided in documentation:

{
    "resultIds": [
        "0a3687d0-693a-1627-9a69-6256013e83e4"
    ],
    "statusId": "0a3687d0-611f-16a6-984b-1dc600000231",
    "riskId": "0a3687d0-611f-16a6-984b-1dc600000230",
    "reasonId": "0a3687d0-611f-16a6-984b-1dc60000022c",
    "resolutionRemark": ""
}

There are multiple results per match I am attempting to resolve. Do they all need to be resolved at once? If so, changes might need to be made to our system to resolve the entire case rather than individual matches.

Thank you,

Mark Kalgren

Prabhjyot

@mkalgren

Thank you for your query.

ResultId in 'Resolve Result' API call is an array. That means you can pass multiple results-id for a specific resolution type and will have the same resolution status once the API call is successful.

For the Error 400 Bad request : Once you have selected the resolution status-id from the API call - 'Get the resolution toolkit', you will have to pick the risk-id and the reason-id from the 'resolutionRules' for the specific status-id. If you are selecting the risk-id and reason-id which is not configured in the resolutionRules for the specific status-id you will get Error 400 : Bad request.

Further, the configuration of these fields are done from the Admin settings of the World-Check account via the UI.

Hope this clarifies your concern.