POST cases/screeningRequest returns 400 when secondary field Gender = UNKNOWN

Hey team,


I get a 400 when I send the below request:

{"groupId":"5nzbfkbtnlaw1eddswcrh0dpb","entityType":"INDIVIDUAL","providerTypes":["WATCHLIST"],"nameTransposition":true,"caseId":"PFS25A","name":"Mr Abel Conrad","secondaryFields":[{"typeId":"SFCT_1","value":"UNKNOWN"},{"typeId":"SFCT_2","dateTimeValue":"1962-05-05"},{"typeId":"SFCT_5","value":"KOR"}]}

Changing SFCT_1 (Gender) to MALE (as per below)

{"groupId":"5nzbfkbtnlaw1eddswcrh0dpb","entityType":"INDIVIDUAL","providerTypes":["WATCHLIST"],"nameTransposition":true,"caseId":"PFS25A","name":"Mr Abel Conrad","secondaryFields":[{"typeId":"SFCT_1","value":"MALE"},{"typeId":"SFCT_2","dateTimeValue":"1962-05-05"},{"typeId":"SFCT_5","value":"KOR"}]}

and I get a successful creation.

As far as I can see UNKNOWN is a valid entry for gender as per the spec?


Cheers

Andy

Best Answer

  • Prabhjyot
    Prabhjyot LSEG
    Answer ✓

    @a.gale

    Thank you for your query.

    The values which can be used for SFCT_1 via the API is UNSPECIFIED, MALE and FEMALE.

    Unknown is used via the UI for Gender, where as via the API it has to be UNSPECIFIED.

    We will get the document updated accordingly.

    Hope this helps.

Answers