screeningRequest succeed on v1 but failed on v2

corey

---
http_interactions:
- request:
    method: post
    uri: https://api-worldcheck.refinitiv.com/v1/cases/5jb7ysi13r5a1guvhfwxqtbh2/screeningRequest
    body:
      encoding: UTF-8
      string: ''
    headers:
      Date:
      - Mon, 25 Jul 2022 06:52:56 GMT
      Authorization:
      - Signature keyId="14fc9662-2f3f-4461-86b7-c615bb8b43a8",algorithm="hmac-sha256",headers="(request-target)
        host date",signature="Mjvleye4WeMnB1LW4GEXU1rMB0xw7ihfDzvv82wIP7U="
      Accept-Encoding:
      - gzip;q=1.0,deflate;q=0.6,identity;q=0.3
      Accept:
      - "*/*"
      User-Agent:
      - Ruby
  response:
    status:
      code: 201
      message: ''

^ 201 using v1

---
http_interactions:
- request:
    method: post
    uri: https://api-worldcheck.refinitiv.com/v2/cases/5jb7ysi13r5a1guvhfwxqtbh2/screeningRequest
    body:
      encoding: UTF-8
      string: ''
    headers:
      Date:
      - Mon, 25 Jul 2022 07:00:22 GMT
      Authorization:
      - Signature keyId="14fc9662-2f3f-4461-86b7-c615bb8b43a8",algorithm="hmac-sha256",headers="(request-target)
        host date",signature="JZMorI1Ss3STJIWIsbAJfXcDNSsoNF9vvXJe9Z/ba/Y="
      Accept-Encoding:
      - gzip;q=1.0,deflate;q=0.6,identity;q=0.3
      Accept:
      - "*/*"
      User-Agent:
      - Ruby
  response:
    status:
      code: 404
      message: ''

but 404 when using v2

the rest setting are identical

case_system_id: 5jb7ysi13r5a1guvhfwxqtbh2
api_key_id: 14fc9662-2f3f-4461-86b7-c615bb8b43a8

Please provide help, thanks in advance

corey

that is on pilot

production also encounter same issue
api key: 6c7cdfdb-7f4c-4853-9b95-5ef4a2b94246

Vivek Kumar Singh

Hi @corey

Thanks for your query!

Please allow us to verify the details on our side, will get back to you shortly.

Thanks

Vivek Kumar Singh

corey

Hi @Vivek Kumar Singh

Is there any update about this issue?
because i found that the enable ongoing screening kind of have same 404 problem

Vivek Kumar Singh

Hi @corey

Apologies for the delay in response!

Can you please let us know the best available time so that we can schedule a session to discuss this issue in details.

I'm available 09:00 AM - 18:00 PM IST

Thanks
Vivek Kumar Singh

corey

hi @Vivek Kumar Singh

Sure, is the time 8 Aug (Monday) - 11:00:00 IST (13:30:00 SGT) good for you?
Please let us know how you would like to schedule a session for it, thanks!

corey

hi
@Vivek Kumar Singh

Didn't get your response, maybe delay 1 week so 15 Aug fine for you?

Vivek Kumar Singh

Hi @corey
Apologies for the delay in response!

I would like you to kindly send me a meeting invite based on your convenience to "Vivek.Singh@lseg.com".
I will be happy to jump on call to discuss this in detail.

Thanks