question

Upvotes
Accepted
35 10 16 20

Screening Online API request fails with Insufficient identifier... What is a correct "identifier" for the Screening Online API?

When I call the screen method, I get this error:

Unmarshalling Error: java.lang.IllegalArgumentException: Insufficient identifier components provided.

I have my group and user identifiers, but what is a sufficient identifier?

Here's my screening code that fails...

<soapenv:Body>

<scr:screen>

<screenRequest>

<assigneeIdentifier>203</assigneeIdentifier>

<customId1>?</customId1>

<customId2>?</customId2>

<groupIdentifier>4</groupIdentifier>

<name>Michael Bloomberg</name>

<nameType>INDIVIDUAL</nameType>

</screenRequest>

</scr:screen>

</soapenv:Body>

world-checkapiscreeningscreening-api
icon clock
10 |1500

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

1 Answer

Upvotes
Accepted
3.1k 16 7 7

Hi @John Williams, the Screening Online API has several identifiers it uses. In your code example the assignee and group identifiers are not formatted properly. I updated my answer for correctness and further clarity.

The most common identifiers and their formats are:

groupIdentifier: cng_so_xxx - where xxx is your group ID

userIdentifier: cnu_so_xxx - where xxx is your user ID

ownerIdentifier: cnu_so_xxx - where xxx is a user ID

assigneeIdentifier: cnu_so_xxx - where xxx is a user ID

nameIdentifier: so_n_xxxxxxxxxxxxxxxxxx (created by Screening Online)

matchIdentifier: so_m_xxxxxxxxxxxxxxxxxx (created by Screening Online)

batchIdentifier: so_b_xxxxxxxxxxxxxxxxxx (created by Screening Online)

Notice the prefixes to the identifiers these are required. Replace your assignee and group Identifiers with the proper prefixes and your code should work properly.

Let me know if you have any more questions about your API requests.

icon clock
10 |1500

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

Click below to post an Idea Post Idea