| 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 (Most Actives)
If your SOAP action is MostActives, you must use the pageid node in your content request. Set the pageid to one of the 6 values found below to retrieve the desired data. All most active categories are updated every 15 minutes throughout the trading day. The return data includes a "recordcount" node that indicates the total number of records returned.

The rsMostactives Node will contain child nodes of:
  • CHANGE - change in price from previous close.
  • CONAME - Company name.
  • EXCHANGE - Exchange for the listed symbol.
  • LAST - last price.
  • LASTUPDATE - When this issue was scanned.
  • SYBMOL - The company ticker symbol.
  • ORDINAL - The order for this issue (per exchange). For example, if you are looking at "gainers" and the ordinal is 1 for a NYSE stock, that would indicate that the stock was the highest gainer by percentage on the NYSE for that scan.
  • PERCCHANGE - Change as a percentage.
  • UPDATETITLE - A string with a date and time for the update - used in a title.
  • VOLUME - Volume for the stock (only applicable to the volume gainers category.
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.
Pageid - An integer from the above table representing one of the 6 available categories.
Request Structure
A SOAP action of Mostactives takes only one required parameter beyond the standard username, password and id. That parameter is pageid. A pageid is an integer that cooresponds to the desired content. Use the table below to determine the appropriate pageid for your request.
Number (int) Description
1    Most Active stocks
2    Volume Gainers
3    Percentage Gainers
4    Percntage Losers
7    52 Week Highs
8    52 Week Lows
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">15</Recordcount>
       <Results xmlns="http://www.finwin.com">
         <rsMostactives> 
           <CHANGE xsi:type="xsd:float">8.0000000000000002E-2</CHANGE>
           <CONAME xsi:type="xsd:string">Cisco Systems Inc</CONAME>
           <EXCHANGE xsi:type="xsd:string">NASDAQ</EXCHANGE>
           <LAST xsi:type="xsd:float">16.100000000000001</LAST>
           <LASTUPDATE xsi:type="xsd:date">2002-03-21 11:21:00</LASTUPDATE>
           <ORDINAL xsi:type="xsd:float">1.0</ORDINAL>
           <PAGEID xsi:type="xsd:int">1</PAGEID>
           <PERCCHANGE xsi:type="xsd:float">0.5</PERCCHANGE>
           <SYMBOL xsi:type="xsd:string">CSCO</SYMBOL>
           <SYM_ID xsi:type="xsd:int">7068398</SYM_ID>
           <UPDATEDATE xsi:type="xsd:date">2002-03-21 00:00:00</UPDATEDATE>
           <UPDATETITLE xsi:type="xsd:string">03/21/02 at 12:15 EST</UPDATETITLE>
           <VOLUME xsi:type="xsd:int">24627400</VOLUME>
         </rsMostactives>
         <rsMostactives> 
           <CHANGE xsi:type="xsd:float">-0.40999999999999998</CHANGE>
           <CONAME xsi:type="xsd:string">Gemstar-Tv Guide Intl Inc</CONAME>
           <EXCHANGE xsi:type="xsd:string">NASDAQ</EXCHANGE>
           <LAST xsi:type="xsd:float">15.0</LAST>
           <LASTUPDATE xsi:type="xsd:date">2002-03-21 11:21:00</LASTUPDATE>
           <ORDINAL xsi:type="xsd:float">2.0</ORDINAL>
           <PAGEID xsi:type="xsd:int">1</PAGEID>
           <PERCCHANGE xsi:type="xsd:float">-2.6600000000000001</PERCCHANGE>
           <SYMBOL xsi:type="xsd:string">GMST</SYMBOL>
           <SYM_ID xsi:type="xsd:int">7068399</SYM_ID>
           <UPDATEDATE xsi:type="xsd:date">2002-03-21 00:00:00</UPDATEDATE>
           <UPDATETITLE xsi:type="xsd:string">03/21/02 at 12:15 EST</UPDATETITLE>
           <VOLUME xsi:type="xsd:int">2166500</VOLUME>
         </rsMostactives>
       </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