Can I display market data in my app?

Usually not by default. Much market data is sold for the buyer's own use, and showing prices to people outside your company, in an app, a site or a client report, is a separate permission that the provider's terms give or withhold. This page explains the notions those terms use, the questions to ask before you build, and the warning signs in a contract. It is general information, not legal advice.

The short answer

Not unless the terms of your data source say you may. Paying for access to prices usually does not by itself allow you to show them to your users: providers usually tell your own use apart from display to others, and price the two apart. The way to know is to read the terms of use of your source, or to ask the provider in writing, for the exact use you have in mind: who sees the prices, how fresh they are, and whether they can be copied out of your product.

Your own use, or display to your users

Internal use means people inside your company read the prices: your analysts, your traders, your back office. Display means anyone else sees them: the customers of your app, the visitors of your site, the recipients of a report. Many offers allow the first and not the second, or allow display only to a number of users, each one counted. A public page anyone can open without an account is display to anyone.

Delayed or live data

Live data is the price as it changes. Delayed data is the same price shown after a set delay, often fifteen minutes or more on stock exchange data. Many sources treat delayed display more loosely than live display, and some allow it free of charge with the source credited. The delay and its conditions are set by each source: check them rather than assume a usual figure.

Derived data

Derived data is what you compute from the prices: an average, an indicator, a signal, a converted amount. Terms differ on it. Some treat a value from which the original prices cannot be recovered as yours to show; others cover anything computed from their data. Many terms treat a chart of candles or a converted price as display, since it still shows the source's prices. Ask how your source defines derived data before you rely on it.

Central bank reference rates

The European Central Bank and the Swiss National Bank publish exchange rates anyone can read on their sites. The ECB publishes one reference rate per currency each working day, and says its rates are published for information purposes only and that using them for transactions is strongly discouraged. Such a rate is one figure a day: no bid and ask, nothing between two publications, nothing at the weekend. It suits a reference, an invoice conversion or a daily report, not a screen of live prices. What each bank allows when its rates are shown in a product is in its own terms of use, on its site: read them, and credit the source as they ask.

Free sources and broker feeds

Spot forex is traded over the counter, without a central exchange, so the prices you see come from a bank, a broker or a data provider, each with its own terms. Free price sites and the prices of a trading account are usually for the account holder's personal use: their terms often forbid copying the prices into another product, and reading a site with a program can break them too. A price that is free to look at is not, for that reason, free to show to others.

Questions to ask your provider

Ask in writing, and keep the answer with the contract:

• May the data be shown to people outside our company, and to how many?
• Is there a fee per user who sees a price, and must we report our users?
• Does showing live prices cost more than showing delayed ones?
• May we pass the data on to our clients' systems, or only show it on a screen?
• May we store what we receive and show it again later, and what happens to it when the contract ends?
• What counts as derived data, and may we show it?
• Which symbols and markets does the permission cover?

Warning signs in the terms

None of these forbids your project by itself, but each is a reason to ask before you build:

• Personal use only, non-commercial use only, or internal use only.
• Display to third parties only on an enterprise plan, or by separate agreement.
• A fee per user or per device, with a duty to report them.
• An audit of how many people saw the data, at the provider's request.
• No caching or storage of the data, or storage for a short time only.
• Terms that may change at any time, without notice, for the use your product depends on.

Where this API stands

Every paid plan here allows display in your product, relay to your clients and keeping what you receive, for the 46 currency pairs and 5 metals it carries, with no fee per user and no report of who saw a price. A symbol your connections follow live for more than 80% of its open hours in a month adds CHF 150 to the next invoice. It covers those symbols only, with no bulk export, and the free trial is for testing an integration, not for showing the data to your users. The details are on the market data redistribution page.

Not legal advice

This page describes how market data terms are commonly written, to help you ask the right questions. It is not legal advice and interprets no particular contract. For a decision your business depends on, read the terms of your source and ask a lawyer who knows your market.

Facts as of 10.10.2026.

# 1. your server exchanges the key for a short-lived token
export ADONA_API_KEY="${ADONA_API_KEY:-adk_live_...}"
RESP=$(curl -s https://api.adona-robot.com/v1/tokens \
  -H 'Content-Type: application/json' \
  -H "Authorization: Bearer $ADONA_API_KEY" \
  -d '{"end_user_id":"u-42"}')
TOKEN=$(echo "$RESP" | grep -o '"access_token":"[^"]*' | cut -d'"' -f4)
[ -n "$TOKEN" ] || echo "refused: $RESP"

# 2. the token reads candles
curl -s 'https://api.adona-robot.com/v1/candles?symbol=EURUSD&timeframe=S1&limit=1000' \
  -H "Authorization: Bearer $TOKEN"