Could not get any response. API. Postman

Hello,

today we try to test the World-Check One API v1.5 (methods: SEQ-pre-groups. SEQ-screen-sync-simple, but as response receive the following:

In the Postman logs we found following:

Error: SSL Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE

- Proxy:
  - host:"127.0.0.1"
  - port:8888
  - match:"http+https://*/*"

Request Headers:
- Date:"Thu, 31 Jan 2019 10:04:24 GMT"
- Authorization:"Signature keyId="ffd37d13-36f9-4efc-ab5e-d9ec9dbee778",algorithm="hmac-sha256",headers="(request-target) host date",signature="6i+TUnWEpqWrvlPrlh4R0xDpXRfhWXp1XIM1evrQFRs=""
- cache-control:"no-cache"

Could you assist with the issue?

Thanks in advance!

Find more posts tagged with

api

ssl

world-check-one

postman

world-check

rest-api

Accepted answers

Prabhjyot

@otkachova,

Thank you for providing the steps. Can you please remove the proxy settings and then try again? Steps below -

Go to File > settings > Proxy > Switch off the 'Global proxy configuration.

Once you have disabled the proxy settings, please try again and it should work.

Let us know if this helps.

All comments

Prabhjyot

@otkachova,

Can you please provide us the steps to reproduce the issue?

otkachova

We have done the following steps:

1. Launch Thomson Reuters World-Check One API v1.5

2. Launch and edit WC1 Pilot Environment (set up private API-key, API-secret)

3. Initiate API call (method: SEQ-pre-groups: Get my top-level groups)

The log of the request:

GET /v1/groups
Date: Fri, 01 Feb 2019 07:52:14 GMT
Authorization: Signature keyId="ffd37d13-36f9-4efc-ab5e-d9ec9dbee778",algorithm="hmac-sha256",headers="(request-target) host date",signature="NmPSgSJLkKjFSoxh7pOwrg/k6EHdmYDl2ANYaqaoV+4="
cache-control: no-cache
Postman-Token: dc239e21-e3de-48b4-a43c-8dc1374a3d2d

4. And receive the following response

Prabhjyot

@otkachova,

Thank you for providing the steps. Can you please remove the proxy settings and then try again? Steps below -

Go to File > settings > Proxy > Switch off the 'Global proxy configuration.

Once you have disabled the proxy settings, please try again and it should work.

Let us know if this helps.

EXPLORE OUR SITES