In order to access the nFusion Solutions APIs, you will be issued one or more API tokens, depending on your use case. These API tokens should be considered a secret, and should not be exposed over the public internet. To that end, API calls should never be made directly in JavaScript such that the code can be inspected in a browser and the API token discovered. Instead of making direct calls to nFusion APIs in client-side code, please use a proxy on your own server. For example, https://yoursite.com/proxy/metals/spot. The nFusion API can then be called from your server-side code and the token will not be exposed. It is also highly recommended that your proxy perform some form of caching so that the ratio of client-side requests for data is not 1:1 with calls to nFusion APIs, as this will boost performance. Moreover, when accessing our data API, some of the following HTTP headers should be added to your API requests, depending on your use cases.AcceptThe recommended value for this header is “application/json”. If you prefer XML results you can specify “application/xml”, but we recommend JSON for most use cases.Accept-EncodingThe recommended value for this header is “deflate,gzip”. This will result in compressed results that generally have better performance.Content-TypeFor POST/PUT operations that require a message body this header should be set to “application/json”.User-AgentWe recommend setting this to your customer id.
