How to set customFields for my request?

@Alexandra

Hi,

World-Check One provides the
functionality of passing custom fields as part of your request payload for our
customers to track additional details at their end, the custom fields are
solely for use at your end, the fields that you set will not contribute in
screening against World-Check one data,

Below is an example payload with
a custom filed for your reference,

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

{ "groupId":
"{{group-id}}", "entityType": "INDIVIDUAL",
"providerTypes": [ "WATCHLIST" ], "name":
"Donald Trump", "customFields": [{ "typeId":
"CUSTO_9" }, { "value": "Bc1234" } ],
"secondaryFields": [{ "typeId": "SFCT_1",
"value": "MALE" }, { "typeId":
"SFCT_2", "dateTimeValue": "1961-12" }, {
"typeId": "SFCT_3", "value": "USA" }, {
"typeId": "SFCT_4", "value": "USA" }, {
"typeId": "SFCT_5", "value": "ABW" } ]
}

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

For a custom filed you will have
to define you own typeID and its curresponding value compared to the secondary
fields that World-Check One provides in your case template.

If you wish to not include custom
fields in your request payload you can just delete them from your request
payload and pass the request.

Let me know if this resolves your
issue and feel free to reach out if you need further assistance on this.