Getting Started FAQs

Yes, all Xignite APIs deliver CSV output that is RFC 4180 compliant.
The goal of RFC 4180 is to encourage a "standardization" of CSV formatting, and states that CSV may contain values separated by comma and embedded in double quotes.

You may view the RFC 4180 specifications here



The API of choice for pulling real-time spot prices for multiple precious metals simultaneously is GetRealTimeMetalQuotes.
The following URL can be used to call up the latest prices for Gold, Silver, Palladium and Platinum in USD (other currencies are supported as well).
Please ensure you are properly logged into the Xignite Web and your Account is entitled to XigniteGlobalMetals:

http://globalmetals.xignite.com/xGlobalMetals.xml/GetRealTimeMetalQuotes?Symbols=XAU,%20XAG,%20XPD,%20XPT&Currency=USD

The number of hits required to display "metals market activity" depends on the timeliness of updates required on the client end. Some customers may choose to update prices every 5 minutes, while others may wish to update twice per minute. As the granularity increases, so does the number of hits. Our teams can assist in determining rough figures for total hits/month required for a particular "price refresh" schedule.

If you have other questions on how to query for daily Metals prices, please Open a Case or send an e-mail to support@xignite.com.



  1. Right-click on the project and click "Add Service Reference":


     
  2. From the window that pops up, click on the “Advanced” button:


     
  3. Click “Add Web Reference” from the next window:


     
  4. Put in the URL and service name and click on “Add Reference”. You can rename the web reference for convenient use in your code.


     
  5. At this point, the project update should be complete and the Web Reference will be added correctly.

If you have any other question, please send an e-mail to support@xignite.com.


IP authentication is discouraged because your application will break if your IP addresses change. We highly recommend using API token authentication to avoid this problem. If you still wish to use IP authentication, there are a few simple steps to follow in order to add or remove IP addresses on your User Account. When using IP authentication, it is critical the IP is added before any queries are executed or the queries will error.

First, you must log in to the Xignite Web Site - once logged in, follow the steps here:
  1. Go to the Manage My API Tokens page within the My Profile area
     
  2. On that page, click the  button
     
  3. In the Add Token box, change the first dropdown to “IP”
     
  4. In the 2nd blank box that appears, enter the full IP address
     
  5. Once you confirm it is entered correctly, press 
     
  6. Note: To lock in this change, press  or you will not actually Save this new IP to the account.

No, you may not use any APIs listed in the WSDL if they are not also cataloged on the API List page for that Service as such API are not supported.

APIs that are available in the WSDL but not documented could potentially be:
  • Non-functional or buggy
  • Targeted for deprecation at any time
If you use such an API you therefore assume the risk that your application could not work with no ability to obtain support for it.

If you have any other questions about this, you may send them to support@xignite.com.

An API Token is an alphanumeric code, unique to your Xignite Account, which can be used from any system to validate your API calls. API tokens are passed in the Username field of any SOAP code.  It is also our preferred method of authentication over using IP or E-mail Addresses.  For example, an API Token can be used in a multi-server configuration without following up to add each IP address to your account. If load balancing switches the call to originate/execute from another server, this is seamless when using an API Token. This allows for a more dynamic and error-free configuration. 

To add an API Token to your account, follow these steps:

 

  1. Go to My Account > Manage My API Tokens: https://www.xignite.com/MyAccount/Tokens.aspx
     
  2. Click the blue  button, and select the option “API” from the dropdown
     
  3. The window will say “A random token will be generated.”, then click the blue  button
     
  4. Once you go back to the Token list/table, make sure to click  or it will not actually equip your account with the new Token.
     
  5. Once it saves, you will see the alphanumeric string in the table as a new row.