types of network protocols #30

Activity

1. clientsuccessnasdaq commented on Oct 22, 2022

   

   clientsuccessnasdaq

   on Oct 22, 2022 via email

   More actions

   -- Please reply above this line -- Thank you for contacting the Client Success Team at Nasdaq Data Link. Your email is very important to us and we will respond to you within 1 to 2 business days.
2. clientsuccessnasdaq commented on Oct 25, 2022

   

   clientsuccessnasdaq

   on Oct 25, 2022 via email

   More actions

   -- Please reply above this line -- Hi there, Thank you for your inquiry. Can you clarify which product you are attempting to access via NDL Python API? Best regards, Hao TRUNG-HAO NGUYEN Client Success  Nasdaq Data Link How would you rate my reply? Great [1]    Okay [2]    Not Good [3] Links: ------ [1] https://secure.helpscout.net/satisfaction/569083952/record/6088247170/1/ [2] https://secure.helpscout.net/satisfaction/569083952/record/6088247170/2/ [3] https://secure.helpscout.net/satisfaction/569083952/record/6088247170/3/ On Sat, Oct 22, 2022 at 1:34 PM EDT, Nasdaq/data-Link-Python ***@***.***> wrote:

   …

   WARNING - EXTERNAL EMAIL; EXERCISE CAUTION. Hi there, just a simple question. Which kind of network protocol are compatible with Nasdaq for messages and order management? I've found out FIX protocol (used for messages between brokers, investment banks financial advisors etc.) but i would like to know there are alternatives (maybe own by Nasdaq) Thanks - Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> ******************************************* CONFIDENTIALITY AND PRIVACY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient and may constitute non-public information. Personal data in this email is governed by our Privacy Policy at https://www.nasdaq.com/privacy-statement [3] unless explicitly excluded from it; please see the section in the policy entitled "Situations Where This Privacy Policy Does Not Apply" for circumstances where different privacy terms govern emailed personal data. If you received this e-mail in error, disclosing, copying, distributing or taking any action in reliance of this e-mail is strictly prohibited and may be unlawful. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive any work product or other applicable legal privilege(s) by the transmission of this message. ******************************************* Links: ------ [1] #30 [2] https://github.com/notifications/unsubscribe-auth/AWYQ64ZX447MV443Y4FXSRTWEQQNJANCNFSM6AAAAAARL5VWDQ [3] https://www.nasdaq.com/privacy-statement
3. abstractumx commented on Oct 25, 2022

   

   abstractumx

   on Oct 25, 2022 via email

   Author

   More actions

   Hello Hao, Thanks for your reply. Well, there isn’t a specific product because I am doing some tests and designing it from scratch. I am trying to do a feasibility study to understand the best solution to connect with NASDAQ API data. (Previously Quandl) Thanks Il giorno mar 25 ott 2022 alle 17:07 clientsuccessnasdaq < ***@***.***> ha scritto:

   …

   -- Please reply above this line -- Hi there, Thank you for your inquiry. Can you clarify which product you are attempting to access via NDL Python API? Best regards, Hao TRUNG-HAO NGUYEN Client Success Nasdaq Data Link How would you rate my reply? Great [1] Okay [2] Not Good [3] Links: ------ [1] https://secure.helpscout.net/satisfaction/569083952/record/6088247170/1/ [2] https://secure.helpscout.net/satisfaction/569083952/record/6088247170/2/ [3] https://secure.helpscout.net/satisfaction/569083952/record/6088247170/3/ > On Sat, Oct 22, 2022 at 1:34 PM EDT, Nasdaq/data-Link-Python ***@***.***&gt; wrote: > > WARNING - EXTERNAL EMAIL; EXERCISE CAUTION. > > Hi there, > > just a simple question. > > Which kind of network protocol are compatible with Nasdaq for > messages and order management? > I've found out FIX protocol (used for messages between brokers, > investment banks financial advisors etc.) but i would like to know > there are alternatives (maybe own by Nasdaq) > > Thanks > > - > Reply to this email directly, view it on GitHub [1], or unsubscribe > [2]. > You are receiving this because you are subscribed to this > thread.Message ID: > ***@***.***> > ******************************************* > CONFIDENTIALITY AND PRIVACY NOTICE: This e-mail and any attachments > are for the exclusive and confidential use of the intended recipient > and may constitute non-public information. Personal data in this email > is governed by our Privacy Policy at > https://www.nasdaq.com/privacy-statement [3] unless explicitly > excluded from it; please see the section in the policy entitled > "Situations Where This Privacy Policy Does Not Apply" for > circumstances where different privacy terms govern emailed personal > data. If you received this e-mail in error, disclosing, copying, > distributing or taking any action in reliance of this e-mail is > strictly prohibited and may be unlawful. Instead, please notify us > immediately by return e-mail and promptly delete this message and its > attachments from your computer system. We do not waive any work > product or other applicable legal privilege(s) by the transmission of > this message. > ******************************************* > > Links: > ------ > [1] #30 > [2] > https://github.com/notifications/unsubscribe-auth/AWYQ64ZX447MV443Y4FXSRTWEQQNJANCNFSM6AAAAAARL5VWDQ > [3] https://www.nasdaq.com/privacy-statement > > > > — Reply to this email directly, view it on GitHub <#30 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXRV74MMX4G3F6VZEVZDWV3WE7ZTFANCNFSM6AAAAAARL5VWDQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>
4. clientsuccessnasdaq commented on Oct 25, 2022

   

   clientsuccessnasdaq

   on Oct 25, 2022 via email

   More actions

   -- Please reply above this line -- Hi there, Nasdaq Data Link's API uses HTTP network protocol to carry out API calls. You can find more about our API on our tools page [1] here [2]. Please let me know if you have any additional questions. Best regards, Hao Links: ------ [1] https://data.nasdaq.com/tools/full-list [2] https://data.nasdaq.com/tools/api TRUNG-HAO NGUYEN Client Success  Nasdaq Data Link How would you rate my reply? Great [1]    Okay [2]    Not Good [3] Links: ------ [1] https://secure.helpscout.net/satisfaction/569971392/record/6088525750/1/ [2] https://secure.helpscout.net/satisfaction/569971392/record/6088525750/2/ [3] https://secure.helpscout.net/satisfaction/569971392/record/6088525750/3/ On Tue, Oct 25, 2022 at 11:48 AM EDT, Nasdaq/data-Link-Python ***@***.***&gt; wrote:

   …

   WARNING - EXTERNAL EMAIL; EXERCISE CAUTION. Hello Hao, Thanks for your reply. Well, there isn't a specific product because I am doing some tests and designing it from scratch. I am trying to do a feasibility study to understand the best solution to connect with NASDAQ API data. (Previously Quandl) Thanks Il giorno mar 25 ott 2022 alle 17:07 clientsuccessnasdaq < ***@***.***> ha scritto: > -- Please reply above this line -- > > > Hi there, > > Thank you for your inquiry. > > Can you clarify which product you are attempting to access via NDL > Python API? > > Best regards, > Hao > TRUNG-HAO NGUYEN > Client Success > Nasdaq Data Link > > How would you rate my reply? > Great [1] Okay [2] Not Good [3] > > > Links: > ------ > [1] > https://secure.helpscout.net/satisfaction/569083952/record/6088247170/1/ [1] > [2] > https://secure.helpscout.net/satisfaction/569083952/record/6088247170/2/ [2] > [3] > https://secure.helpscout.net/satisfaction/569083952/record/6088247170/3/ [3] > > > > On Sat, Oct 22, 2022 at 1:34 PM EDT, Nasdaq/data-Link-Python > ***@***.***> wrote: > > > > WARNING - EXTERNAL EMAIL; EXERCISE CAUTION. > > > > Hi there, > > > > just a simple question. > > > > Which kind of network protocol are compatible with Nasdaq for > > messages and order management? > > I've found out FIX protocol (used for messages between brokers, > > investment banks financial advisors etc.) but i would like to know > > there are alternatives (maybe own by Nasdaq) > > > > Thanks > > > > - > > Reply to this email directly, view it on GitHub [1], or unsubscribe > > [2]. > > You are receiving this because you are subscribed to this > > thread.Message ID: > > ***@***.***> > > ******************************************* > > CONFIDENTIALITY AND PRIVACY NOTICE: This e-mail and any attachments > > are for the exclusive and confidential use of the intended recipient > > and may constitute non-public information. Personal data in this email > > is governed by our Privacy Policy at > > https://www.nasdaq.com/privacy-statement [4] [3] unless explicitly > > excluded from it; please see the section in the policy entitled > > "Situations Where This Privacy Policy Does Not Apply" for > > circumstances where different privacy terms govern emailed personal > > data. If you received this e-mail in error, disclosing, copying, > > distributing or taking any action in reliance of this e-mail is > > strictly prohibited and may be unlawful. Instead, please notify us > > immediately by return e-mail and promptly delete this message and its > > attachments from your computer system. We do not waive any work > > product or other applicable legal privilege(s) by the transmission of > > this message. > > ******************************************* > > > > Links: > > ------ > > [1] #30 [5] > > [2] > > > https://github.com/notifications/unsubscribe-auth/AWYQ64ZX447MV443Y4FXSRTWEQQNJANCNFSM6AAAAAARL5VWDQ [6] > > [3] https://www.nasdaq.com/privacy-statement [7] > > > > > > > > > > - > Reply to this email directly, view it on GitHub > <#30 (comment), > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AXRV74MMX4G3F6VZEVZDWV3WE7ZTFANCNFSM6AAAAAARL5VWDQ > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > - Reply to this email directly, view it on GitHub [8], or unsubscribe [9]. You are receiving this because you commented.Message ID: ***@***.***> ******************************************* CONFIDENTIALITY AND PRIVACY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient and may constitute non-public information. Personal data in this email is governed by our Privacy Policy at https://www.nasdaq.com/privacy-statement [10] unless explicitly excluded from it; please see the section in the policy entitled "Situations Where This Privacy Policy Does Not Apply" for circumstances where different privacy terms govern emailed personal data. If you received this e-mail in error, disclosing, copying, distributing or taking any action in reliance of this e-mail is strictly prohibited and may be unlawful. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive any work product or other applicable legal privilege(s) by the transmission of this message. ******************************************* Links: ------ [1] https://secure.helpscout.net/satisfaction/569083952/record/6088247170/1/ [2] https://secure.helpscout.net/satisfaction/569083952/record/6088247170/2/ [3] https://secure.helpscout.net/satisfaction/569083952/record/6088247170/3/ [4] https://www.nasdaq.com/privacy-statement [5] #30 [6] https://github.com/notifications/unsubscribe-auth/AWYQ64ZX447MV443Y4FXSRTWEQQNJANCNFSM6AAAAAARL5VWDQ [7] https://www.nasdaq.com/privacy-statement [8] #30 (comment) [9] https://github.com/notifications/unsubscribe-auth/AWYQ642H6BOQBKLCOK376XDWE76MVANCNFSM6AAAAAARL5VWDQ [10] https://www.nasdaq.com/privacy-statement