How do I authenticate for requests PUT in Python?
I have problems getting requests.put working on the api in Python. The same way of authentication that works with GET and POST do not work with PUT. I want to make calls to this:
PUT /cases/{caseSystemId}/ongoingScreening
I have the following things defined in my .env file:
REFINITIV_API_ENDPOINT = https://rms-world-check-one-api-pilot.thomsonreuters.com
REFINITIV_API_KEY = abc111
REFINITIV_API_SECRET = abc222
REFINITIV_PRODUCT_KEY = abc333
REFINITIV_GROUP_ID = abc444
How do I use this to make PUT calls in Python using the requests library? We are using Python 3.8.5. I am running Debian WSL on Windows 10. Everything I tried so far gives me the HTTP401 error. I know the keys work because GET and POST on other endpoints work with them.
Best Answer
-
I see a time difference between request and response headers of more than 30 seconds.
Can you please check the clock and try again?
0
Answers
-
Can you please share the request and the response headers of the failed request? Also, can you please confirm the content of dataToSign which you are passing for the PUT request?
0 -
https://rms-world-check-one-api-pilot.thomsonreuters.com/v2/cases/{case_system_id}/ongoingScreening
PUT headers = {
"Date": "Tue, 16 Feb 2021 13:28:15 GMT",
"Authorization": "Signature keyId=\"CENCORED1\",algorithm=\"hmac-sha256\",headers=\"(request-target) host date\",signature=\"CENCORED2=\""
}
result.status_code = 401
result.headers = {'Strict-Transport-Security': 'max-age=15552000, includeSubdomains', 'Authorization': 'WWW-Authenticate: Signature realm="World-Check One API",algorithm="hmac-sha256",headers="(request-target) host date content-type content-length"', 'Transfer-Encoding': 'chunked', 'Date': 'Tue, 16 Feb 2021 13:31:55 GMT', 'Server': '""'}0 -
What do you mean by dataToSign?
0 -
The case_system_id I use right now is a few minutes old and I got that from making a screening request on a random name we made up.
0 -
Fugerad it out I think. I get 204 status back when I PUT to the endpoint with users caseSystemId. The problem was with signing the header I think.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛