@nabil.hassoumi,

It is the same as UI - status, risk and reason is must for resolving a case via the API. Apart from that, you can resolve multiple result Ids with the same status, risk and reason. example below -

{  "resultIds":[ "{
                {result-id1}}", “{
                {result-id2}}” ],  "statusId": "{
                {status-ID}}",  "riskId": "{
                {risk-ID}}",  "reasonId": "{
                {reason-ID}}",  "resolutionRemark":"Enter remarks here!"}

resolutionRemark is another field which can be used to enter a remark for resolving a particular match. There is no other field used via API while resolving a match as of now.

Can you please explain a bit more on what exaclty do you mean by customizing a field?

@nabil.hassoumi,

Thank you for the query.

For resolving a case via API, the manditory fields are resultId, statusId, riskId and reasonId.

resultId can be retreived from the the API call - 'Get screening results'.

statusId, riskId and reasonId can be retreived from the API call - 'Get the resolution toolkit for a group'

The statusId which you use would have specific riskId and reasonId associate with it and only after you use the associated Ids will the match be resolved using the API, else you would receive Error 400 Bad request.

You can use the statusId value from the 'Get the resolution toolkit for a group' and check the associated risk and reason Ids.

Hope this helps.

Hello, My question was more about the workflow, about the mandatory and customised fields. When you do a remediation through WC1 Web access you must fill these fields (Status, Risk Level, Reason ...). So which ones are mandatory through the API ? also what fields can be customised through the API ?

Best Regards

Nabil