| gif | history | intraday | java | news | objects | options | quote | soap | spots | tickers | weather | end of day | wddx |

Actions:
 Quote
 Symbol Lookup
 Headlines
 Symbol News
 Story
 Most Actives
 
Soap (Headlines)
If your SOAP action is headlines, you don't need any additional information. FSS will automatically return 15 current headlines to you. However, if you wish to increase or decrease the number of headlines, you may pass in a node titled "rowcount" and set to any number between 1 and 25 (the maximum).

The rsHeadlines node will contain a child node for headline, publish_date and distributor. The distributor can be any of FinWin's default news services, or a premium news service (requiring an additional fee).
Available News Sources
AG News
AP News
AP Entertainment
AP Financial News
AP Sports
BTU Energy News
Business Wire
DTN Market Access News
Finwin Commodity Wire
Internet Wire
PR NewsWire
Prime Zone
Real Time Traders

Parameters
Username - The developers username you chose when you enrolled as a FinWin developer.
Password - The developers password you chose when you enrolled as a finwin developer.
ID - The site ID issued by FinWin when you enrolled this Site to receive FinWin content. Note: If you are developing your site and do not yet havea paid FinWin ID you may use the Complimentary developers site ID of 1183.
Rowcount (opt) - A number between 1 and 25.
Request Structure
A SOAP action of HEADLINES takes only one optional parameter beyond the standard username, password and id. That parameter is rowcount. As an authorized news subscriber you are allowed up to 25 current business headlines from subscribed news sources. Passing in a "rowcount" node and setting it to any number between 1 and 25 allows you to retrive that number of headlines. As in all FSS requests, after the standard SOAP envelope and header, a SOAP request packet must have a node titled <ContentRequest xmlns='www.finwin.com'></ContentRequest>. This node contains child nodes that allow FSS to authorize and process your reqest - as in the example:
<?xml version='1.0'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" 
   xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" 
   xmlns:xsd="http://www.w3.org/1999/XMLSchema">
    <SOAP-ENV:Body>
       <ContentRequest xmlns='www.finwin.com'>
         <REQUEST xsi:type="xsd:string">Quote</REQUEST>
         <USERNAME xsi:type="xsd:string">Sillyname</USERNAME>
         <PASSWORD xsi:type="xsd:string">sillypassword</PASSWORD>
         <ID xsi:type="xsd:string">1183</ID>				
         <SYMBOLS xsi:type="xsd:string">msft</SYMBOLS>					
         <SEARCHSTRING xsi:type="xsd:string"></SEARCHSTRING>
         <STORYNUMBER xsi:type="xsd:string"></STORYNUMBER>		
         <PAGEID xsi:type="xsd:int"></PAGEID>	
         <ROWCOUNT xsi:type="xsd:int"></ROWCOUNT>	
       </ContentRequest>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Return Data
					
<?xml version='1.0'?>
<SOAP-ENV:Envelope 
   xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" 
   xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" 
   xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" 
   xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
   <Recordcount xsi:type="xsd:int">25</Recordcount>
     <Results xmlns="http://www.finwin.com">
       <rsHeadlines> <DISTRIBUTOR xsi:type="xsd:string">BW</DISTRIBUTOR>
         <HEADLINE xsi:type="xsd:string">First True Object-Oriented Web Service Platform Announced by Wizen Software</HEADLINE>
         <PUBLISH_DATE xsi:type="xsd:date">2002-03-20 17:48:00</PUBLISH_DATE>
         <STORY_ID xsi:type="xsd:int">630519</STORY_ID>
       </rsHeadlines>
       <rsHeadlines> <DISTRIBUTOR xsi:type="xsd:string">BW</DISTRIBUTOR>
         <HEADLINE xsi:type="xsd:string">UICI Added To S&amp;amp;P SmallCap 600 Index</HEADLINE>
         <PUBLISH_DATE xsi:type="xsd:date">2002-03-20 17:48:00</PUBLISH_DATE>
         <STORY_ID xsi:type="xsd:int">630520</STORY_ID>
       </rsHeadlines>
     </Results>
</SOAP-ENV:Body></SOAP-ENV:Envelope>


			
Fault Packets
FSS returns error descriptions as a soap packet with a "<Soapfault></Soapfault>" node in the results. An FSS SOAP fault packet looks like this:
					
<?xml version='1.0'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" 
   xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" 
   xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" 
   xmlns:xsd="http://www.w3.org/1999/XMLSchema">
   <SOAP-ENV:Body>
     <Results xmlns="http://www.finwin.com">
        <SoapFault>
          <EXCEPTION xsi:type="xsd:string">Username or password incorrect</EXCEPTION>
        </SoapFault>
     </Results>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

				
FSS Returns the following messages as SOAPFaults:
  • Method not allowed - Returned when you use an HTTP GET rather than a POST request. This return message also generates a 405 HTTP status code in the response header.
  • Missing SOAPAction Header - returned when no header titled SOAPAction was found.
  • Invalid SOAPAction Value - n is not a valid action - returned when the SOAPAction header contains an invalid or unrecognized SOAPAction
  • Missing Content-Type Header - A header named "content-type" was not found in your HTTP request
  • Invalid Content Type - your content-type header specifies something other than text/xml
  • Username Required - You did not provide a username in the request packet.
  • password Required - You did not provide a password in the request packet.
  • id Required - You did not provide a site id in the request packet.
  • Invalid Site ID - Your site ID is either unauthorized or not found.
  • Username or password incorrect - Your username and password are unauthorized or not found.

DTN Market Access
9110 West Dodge Road, Suite 200   Omaha, Nebraska 68114
Copyright 2010, All rights reserved