Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Screening /
  • World-Check One /

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

Overview |  Quickstart |  Documentation |  Downloads

avatar image
Question by cliff.ching · Mar 01, 2018 at 09:00 PM · world-checkworld-check-oneerror-400

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

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

1 Reply

  • Sort: 
avatar image
REFINITIV
Answer by Irfan.Khan · Mar 02, 2018 at 12:57 AM

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.


Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

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

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
9 People are following this question.

Related Questions

Error code 400 in ParallelDots API

Backend error 400

"cases/{ {case-system-id}}/screeningRequest" is not updating case results when called again after case update request

SEQ-screen-sync-simple getting error 400 most of the time

Bad Request error on Cases webservice call

  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Electronic Trading
    • Generic FIX
    • Local Bank Node API
    • Trading API
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • FX Venues
    • FX Trading – RFQ Maker
  • Intelligent Tagging
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open Calais
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • RDMS
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • Workspace SDK
    • Element Framework
    • Grid
  • World-Check Data File
  • Yield Book Analytics
  • 中文论坛
  • Explore
  • Tags
  • Questions
  • Badges