RKD GET DOCUMENT Postman 403 error

Client tries to use Get Document to get filings for ELD.AX with DCN. It works in the RKD Support Portal. Using the same credential and token, and same endpoint, the client got 403 error. I can replicate client’s issue in Postman. Please see details below and shed some lights. Many thanks
Getting 403 error for the below,
FYI, we are passing active token only. The same token is working for other endpoints.
Best Answer
-
Hello @thomas.j.tan
Based on the RKD Support portal page and RKD Developer Guide (you can open it by clicking on the "Developer Guide" button on that page), the RKD Filing Service supports the authentication setting via HTTP Cookies, not HTTP Headers parameters like other services.
The required HTTP Cookies values are as follows:
- RkdAppId=AppID
- RkdToken=RkdToken
You can find more detail about how to set up HTTP Cookies in Postman via the official Postman https://learning.postman.com/docs/sending-requests/cookies/ document.
Hope this helps.
0
Answers
-
Hello @thomas.j.tan
Based on the official Postman https://learning.postman.com/docs/sending-requests/cookies/ document, you can set the HTTP Cookies automatically when run the Authentication script via the following steps:
Firstly, add the "api.rkd.refinitiv.com" domain to the Postman Cookies menu:
Next, add the "api.rkd.refinitiv.com" domain to the Domain Allowlist as follows:
Then, you can set the Application ID and RKD Token in the Test Script as follows (please update the variable names to match your requirement).
const cookieJar = pm.cookies.jar();
cookieJar.set("api.rkd.refinitiv.com", "RkdAppId",pm.variables.get("appid"),(error, cookie) => {
if (error) {
console.error(`An error occurred: ${error}`);
} else {
console.log(`Cookie saved: ${cookie}`);
}
});
cookieJar.set("api.rkd.refinitiv.com", "RkdToken",pm.variables.get("Token"),(error, cookie) => {
if (error) {
console.error(`An error occurred: ${error}`);
} else {
console.log(`Cookie saved: ${cookie}`);
}
});0 -
Then make sure the Cookie is presented in the HTTP Header and the content type is application/pdf.
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
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛