For a deeper look into our World Check One API, look into:

Overview |  Quickstart |  Documentation |  Downloads

question

Upvotes
cliff.ching avatar image
5 ●6 ●3 ●8

Error 400 when creating case with secondary field

Hi team,

I created a case with the following and received an error.

(request-target): post /v1/cases
host: rms-world-check-one-api-pilot.thomsonreuters.com
date: Fri, 02 Mar 2018 01:45:49 GMT
content-type: application/json
content-length: 336
{"secondaryFields":[{"typeId":"SFCT_1","value":"MALE"},{"typeId":"SFCT_2","value":"1967-09-25"},{"typeId":"SFCT_3","value":"USA"},{"typeId":"SFCT_4","value":"USA"},{"typeId":"SFCT_5","value":"USA"}],"entityType":"INDIVIDUAL","customFields":,"groupId":"0a3687d0-611f-16a6-9870-ce4700001793","providerTypes":["WATCHLIST"],"name":"Donald"}

The following is the error message:

The remote server returned an error: (400) Bad Request.

[{"error":"INVALID_MESSAGE_FORMAT","cause":"Message body is not well-formed."}]

I am able to create case without the secondary field so I believe there is some problem within my encrypted data to send.

Thanks

world-checkworld-check-oneerror-400
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

Upvotes
Irfan.Khan avatar image
4.2k ●8 ●5 ●6

Hello @cliff.ching

I have checked the JSON body you have provided in this query and see two errors in it.

{"secondaryFields":[{"typeId":"SFCT_1","value":"MALE"},{"typeId":"SFCT_2","value":"1967-09-25"},{"typeId":"SFCT_3","value":"USA"},{"typeId":"SFCT_4","value":"USA"},{"typeId":"SFCT_5","value":"USA"}],"entityType":"INDIVIDUAL","customFields":,"groupId":"0a3687d0-611f-16a6-9870-ce4700001793","providerTypes":["WATCHLIST"],"name":"Donald"}

1. customFields does not have square brackets after colon. Please include square brackets after custom fields, even if you are not including any custom fields in your request. Ex: customFields:[],

2. The "Date" value of the secondary field has the "name" mentioned as "value". Kindly change it to "dateTimeValue". For example:

{"typeId":"SFCT_2","dateTimeValue":"1967-09-25"}

The correct JSON body is shown below:

{"secondaryFields":[{"typeId":"SFCT_1","value":"MALE"},{"typeId":"SFCT_2","dateTimeValue":"1967-09-25"},{"typeId":"SFCT_3","value":"USA"},{"typeId":"SFCT_4","value":"USA"},{"typeId":"SFCT_5","value":"USA"}],"entityType":"INDIVIDUAL", "customFields":[] ,"groupId":"0a3687d0-611f-16a6-9870-ce4700001793","providerTypes":["WATCHLIST"],"name":"Donald"}

Make sure the EOL conversion is Linux linefeed (LF) before pasting the Json body to the Postman, if you are using the tool to test WC1 API.

It is always recommended to use the "SEQ-1c: Get the case template for a group" and compare the JSON body (to be used for saving the case) to the case template obtained from SEQ-1c to be sure that all the value and their keys are correct.

You can use any JSON validator available online to be check the JSON being sent to WC1 API is valid.

Thanks,

Irfan Khan.


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.