IP Subnet range and the port range of World Check One API

Hi Team,
I have a query to know the IP Subnet range and the port range that were used to host the World check API key.
Below the issues we are facing while executing the code.
The remote server returned an error: (407) Proxy Authentication Required.
The remote server returned an error: (504) Gateway Timeout.
Best Answer
-
We do not provide the IP subnet range to our clients and recommend our users to connect to the host directly. The reason for this that the IP ranges for WC1 API are dynamic and changes over time.
Regarding the port number, you can connect to the https port, i.e, 443.
Regarding the error, kindly note that 407 is client facing error code.
Request you to let us know if you are sending your requests using a proxy. Also, kindly let us know how are you sending your requests- Postman or your own code/application or CRM/CMS.
If you are using a proxy to send your requests, kindly include the below header to see if it works.
"Proxy-Authenticate": "Basic"
If this does not work, it may be the proxy setting that is causing the issue.
0
Answers
-
0
-
Hi @Irfan.Khan,
we checked with each and every application that you mentioned like postman,console aplication and in CRM also. the post data we send was executed correctly for postman and console application(own code)
but we are facing the proxy authentication issue while we host our Own code(window service) in our CRM server.
FYI, i am not using any type of proxy settings in my application.but still i am facing that 407 issue. kindly help me out.
many thanks in advance.0 -
Can you please confirm that you are passing the header
"Proxy-Authenticate": "Basic" in your request header along with the authorization headers and date header.
If the above fix does not solve the issue, can you please let us know the programming language you are using? Is it C# and where the code is hosted?
0 -
Following up to see if the issue still persists.
If the issue has been resolved, kindly help us with how were you able to resolve the error. This would surely help our other clients facing the same issue.
Thanks.
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
- 695 Datastream
- 1.5K DSS
- 631 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 562 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
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 736 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
- 96 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛