API Integration FAQs

All our APIs can be called security over HTTPS using SSL.
How you implement secure calls depends on which protocol you use when calling our services.

If you use SOAP, you simply need to make sure you use a secure web reference to the WSDL file.
For instance, use this web reference when calling the XigniteGlobalQuotes service securely: https://globalquotes.xignite.com/xglobalquotes.asmx?WSDL 
Or use this reference when calling it in the clear: http://globalquotes.xignite.com/xglobalquotes.asmx?WSDL 
They will work and operate exactly the same way.

If you use REST, just put HTTPS as the prefix to your URL instead of HTTP.
Again, the APIs will work exactly the same way.



Yes, you can integrate the XigniteMetals web service into your eCommerce Shopping Cart.
Many Xignite clients who operate in the precious metal industry use XigniteMetals to price their transactions based on up-to-date accurate metal prices.

The APIs that can be integrated with your shopping cart are:

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.


No, this is not permitted because our Services are hosted on in a virtual environment across many servers.
Due to load balancing or other server shuffling activities, the IP address for an API could change at any time without notice. You cannot rely on any IP address to remain static. The proper way to code to an Xignite API destination is via the API URL.

If you have any issues using an Xignite API, please send an e-mail to support@xignite.com so that we can assist you.

All Xignite APIs support the JSON and JSONP format.

To return data using the JSON format, all you need to do is use ".json" as the extension for the service on the URL call.

For instance the following call will return data in XML format
http://www.xignite.com/xCurrencies.xml/GetRealTimeCrossRate?From=USD&To=EUR

But this similar call will return data in JSON format
http://www.xignite.com/xCurrencies.json/GetRealTimeCrossRate?From=USD&To=EUR
 
'JSONP' or "JSON with padding" is a communication technique used in JavaScript programs which run in Web browsers. It provides a method to request data from a server in a different domain, something prohibited by typical web browsers because of the same origin policy. 

To implement JSONP for any API call, you may add the following value pair to your querystring: &_callback=yourFunction.

For more information on JSONP, check http://www.w3resource.com/JSON/JSONP.php.

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.