Your key stays private
The call is made by our server, not the browser. The key is never in the page source and never in the network tab — which is the whole reason not to do this with JavaScript on your own site.
Today's gold price, this morning's exchange rate, your own pricing service. If it answers over HTTP with JSON, a calculator on your website can use it — and your key never leaves our server.
30-day free trial · no credit card requiredA widget like any other. It shows the visitor nothing; it fetches figures for the rest of the calculator to use.
Headers for the key or token, and values to send — fixed, or taken from what the visitor answered.
The real response comes back and you click the figures you want. Nested values are named for you.
They appear in the formula editor alongside your own questions: [rate] * [grams].
The call is made by our server, not the browser. The key is never in the page source and never in the network tab — which is the whole reason not to do this with JavaScript on your own site.
Reuse an answer for a chosen number of seconds, so a hundred visitors in five minutes cost one call rather than a hundred. Most services charge by the call.
A response carrying a list becomes a chart or a data table, so a price history plots itself.
Rates, prices, stock levels, shipping quotes, your own internal pricing service. No integration is written for a specific provider, so anything that answers with JSON works.
No. The request is made server-side and the key travels in a header from our server to theirs. Nothing about it reaches the browser.
Set the cache. At five minutes, every visitor in that window shares one call. At zero, each change a visitor makes is a fresh call — accurate to the second, and more expensive.
Yes. Any value sent with the call can be a fixed value or the answer from one of your fields, so the question you ask the service changes with what they type.
A list becomes a dataset a chart or data table can plot. The connector reads both rows of objects and parallel lists.