Help with authorization for WC1 API

Hi I am quite new to WC1. I have the API key and the API secret. I am trying to use python to connect to WC1 API and automate a few things. I need some help with the authorization value in the header.
I am trying to execute the below snipprt.
import requests
url = "https://api-worldcheck.refinitiv.com/v2/reference/countries"
headers = {
"Authorization": "SOME_STRING_VALUE",
"Date": "SOME_STRING_VALUE"
}
response = requests.request("GET", url, headers=headers)
print(response.text
I have come to learn the authorization value should be something like the below.
Signature keyId="xxxxxxxxxxxxx",algorithm="hmac-sha256", headers="(request-target) host date content-type content-length", signature="xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
Can anyone please guide me in the correct way on how to generate the signature?
I am aware that the signature should be generated using HMAC but the official documentation is not entirely clear on what data to use as input.
Host: api-worldcheck.refinitiv.com Date: Tue, 07 Jun 2016 20:51:35 GMT Content-Type: application/json Content-Length: 88 Authorization: Signature keyId="4321",algorithm="hmac-sha256", headers="(request-target) host date content-type content-length", signature="Iktz/AdXHmDouNm6uBB8ZW0xcfNGuWGDxmX9TFMwuF0=" { "caseId": "my customer ID", "name": "John Doe", "providerTypes": ["WATCHLIST"] }
For instance, is it essential to have the caseID, name and providerTypes when generating the signature? If yes, what are these values pointing to? I am just looking to connect to WC1 and have some articles resolved using python.
Thanks in advance.
Best Answer
-
janaka.medawala, thank you for reaching out to us!
It is not essential to have caseId, name, or providerTypes when generating the signature.
I'm not able to share some code samples with you here because the files are too big, so I've just emailed you.
If you have any further questions, please let me know!Best,
Judith
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛