Bulk records execution Problem in WCO API
When we are sending bulk records(Ex:250) using API to WCO, we are able to create 135 records in WCO but after 135 records we are getting 401 - UnAuthorized error. Is there any time limit for the API connection or API Keys.
Best Answer
-
I assume you are sending each request concurrently because we do not have the functionality of sending bulk request.
No we do not have a time limit for the API connection or API key as each request establishes a new connection.
The reason you may be getting a 401 is because the date header value you are sending would be getting outdated after 135 requests. The dateheader value sent in the request should be exact as per the GMT clock, although we allow a leeway of 40 to 50 seconds on the timestamp but anything more than that we consider the date header value to be expired and send a 401 to avoid replay attack.
Kindly send a fresh date header value for each request instead of using the same timestamp for all your concurrent request. This can be done by defining a new date header value for each request instead of using the same dateheader value for every concurrent request.
2
Answers
-
Hello @Irfan,
Thank you so much for your reply. Now i am able to send bulk request at a time with out hitting any unauthorised access after sending the date value header as GMT for each request .
0 -
That's great news and I am glad to hear that the API calls are being sent concurrently.
Kindly accept the answer so that our other users can get benefitted by your question.
0 -
Hi @Irfan.Khan
I would like to know know one more question regarding update request of WCO API.
previously i have observed that when i run postman application using put request with the individual/Organisation data, it would update the data what we sent irrespective of remaining fileds like secondary/custom (the data would remain as usual). but later on i came to notice that when I use the same PUT request i saw only the fields that were send was updated and remaining secondary/custom fields remains Null(empty). this was so surprising for me.kindly help me whether the API calls of WCO has been changed Recently?? so as to change the code accordingly.0 -
@manjusha.batchu
I understand your concern, but can you raise a new post for your question so that I may help you out.
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 中文论坛