AI GUIDEPartner content

Free Stock APIs: Where to Get Quotes and Historical Data in Russia

We review free stock APIs: Moscow Exchange quotes, historical candles, instrument directories, request limits, and rules for using data in Russia.

Affiliate link: your price stays the same and the project earns a commission.

Free stock APIs provide instrument directories, historical quotes, candles, some trading data, and select current prices. For the Russian market, the first source usually checked is MOEX ISS from the Moscow Exchange, while broker APIs and international providers are chosen based on the portfolio, bot, screener, or application.

If your task requires a paid model—for example, GPT-5.6 Terra—it is cheaper to arrange access through the Clodex partner service rather than directly from the vendor. The price difference is shown below.

Цены для gpt-5.6-terra (OpenAI)
Price typeOfficial vendor priceThrough Clodex
Input tokens2 $ / 1 million tokens0,07 $ / 1 million tokens
Output tokens12 $ / 1 million tokens0,56 $ / 1 million tokens
DifferenceInput tokens — в 28,6 times cheaper; Output tokens — в 21,4 times cheaper

Partner price source: Clodex. Price check date: 2026-08-18.

SEO Mind42 does not sell API access or provide tokens: we recommend a third-party service Clodex. This is an affiliate link.

The essentials

  • A free stock API does not mean unlimited access to data or unrestricted distribution of it.
  • Historical data, delayed quotes, and real-time data serve different purposes.
  • For Russian stocks, you need to check not only the ticker but also the market, trading mode, currency, and instrument code.
  • MOEX ISS is suitable for working with some Moscow Exchange information, including trading history and the securities directory.
  • A broker API is needed when a service must access its own portfolio, order statuses, or submit orders.
  • Before integration, review the JSON format, request limits, historical data availability, and terms of use for exchange data.
Separate three concepts. Free access to a REST API, free market data, and free commercial use of the information obtained may be governed by different terms from the same source.

What Is a Stock API and What Data Can You Get Through It

A stock API is a programming interface through which an application sends a request to a financial data source and receives a structured response. Most often, the service returns JSON, and less often CSV or another export format. Developers use these responses in Python, JavaScript, Google Sheets, Telegram bots, analytics dashboards, or internal monitoring systems.

A stock market API may provide a list of securities, stock prices, trading volume, price changes, trades, historical quotes, and historical candles. Some sources provide information about dividends, corporate actions, index constituents, exchange rates, bonds, futures, and, depending on the provider, data on crypto instruments.

The fields included depend on the specific endpoint and the provider's rules. One API response may contain the date, opening price, high, low, closing price, and volume. Another method may return a securities directory with the ISIN, SECID, trading venue, board, settlement currency, and an indicator showing whether the instrument is available in the selected trading mode.

The order book and anonymized trades require separate verification. Some APIs publish only aggregated trading data, others provide limited order-book depth, and some sources do not offer such information for free. The presence of historical candles does not automatically mean that a complete trade tape is available.

What Free Stock APIs Are Available

Market data sources differ not by the service name but by the origin of the information and the purpose of the interface. An exchange publishes its own data, a broker connects an API to its client infrastructure, and an external provider collects financial data from several markets and creates a unified request format.

Exchange APIs and Open Interfaces

For Russian stocks, the primary point of reference is MOEX ISS, the Moscow Exchange's programming interface. It helps you find instruments and obtain reference information, historical data, candles, trading statistics, and other sets of exchange information available through specific interface methods.

MOEX ISS is convenient because it works with primary-source data for Moscow Exchange instruments. The response to a single request may include several tables with headers and rows, so developers must explicitly map each field to its index and meaning. An error when parsing the JSON structure can result in incorrect prices, dates, or volumes even when the request is technically successful.

The workflow looks like this: the application finds the required SECID in the directory, verifies the market and board, and then requests historical candles or trading data for the selected instrument. Before implementation, check the method names, response fields, and data status against the current Moscow Exchange API documentation.

The technical availability of information does not override the rules for using it. If the data will appear in a public service, a client report, or a commercial product, check the terms governing the display, distribution, and reuse of exchange information before launching the project.

Broker APIs

A broker API is intended not only for obtaining stock quotes. Through it, an application can work with the client's account, positions, portfolio, orders, execution statuses, and transactions, if these functions are provided by the specific service and permitted by the account settings.

Access to such an API is often tied to the broker's client infrastructure, an access token, and a registered application. The available markets, instruments, and trading data depend on the broker. One service may provide portfolio and order data but not replace a separate historical-data provider for large-scale analytics.

This option is chosen when a trading robot needs to receive the status of its own account or submit orders. Quote APIs and order-placement APIs sometimes exist as separate products. Mixing them in an architecture without checking the documentation is risky: the application may be able to see a price but not have permission to submit a trading order.

International Financial Data Providers

International market-data services are convenient for stocks listed on foreign exchanges, currencies, indices, and cryptocurrencies. They often offer a unified stock API with similar methods for price data, historical data, and instrument directories, which simplifies the development of a multi-currency dashboard.

A provider's free plan may limit the number of requests, the range of supported markets, the depth of history, or the status of quotes. An API key is usually issued after registration, but the specific process depends on the service. Russian instruments should not be assumed to be available by default: coverage of the Moscow Exchange and individual issuers should be checked in the provider's current directory.

A foreign source may return a familiar ticker, but that does not yet confirm that the security is correct. The same code may appear on different exchanges, refer to different asset classes, or describe a depositary instrument instead of a stock traded on the Russian market.

How to Choose an API for Your Task

Choose a source based on the task, the data set, and the rules governing its use. The word “free” does not answer whether an API is suitable for daily exports, a public dashboard, or algorithmic trading.

Task What to Look For Suitable Source Type
Personal portfolio spreadsheet Historical prices, simple exports, stable format Exchange API or market-data provider
Russian stock screener Instrument directory, candles, volumes, filtering Exchange interface
Telegram bot with quotes Request limits, update frequency, rules for publishing data API with clear terms of use
Trading robot Streaming data, order status, account access, failure handling Broker API
Analytics service Data licensing, history, scalability, commercial use Data provider with suitable terms

For Google Sheets, historical prices and daily updates are often enough. A screener needs candles, volumes, and a securities directory. A public application requires a separate review of the rights to display quotes. For approaches to monitoring metrics and automating data collection, see our review of a service for SEO analytics and rank monitoring: the principle of checking the source, data structure, and update frequency is equally important in any analytics system.

How to Get an API Key and Get Started

Connecting an API starts not with writing code but with checking the rules of the selected source. A public method may work without authorization, but an API key or access token is often required for personalized access, quota tracking, and features related to a brokerage account.

  1. Check whether an access key is required. Open the method documentation and find out whether an API key is required for the selected endpoint, historical data, current quotes, or account operations.
  2. Create an account or application. The provider may ask you to register, confirm your contact details, or specify the purpose of the application. The process varies between services.
  3. Keep the secret out of the source code. Environment variables and secure secret storage reduce the risk of an access token leaking from a repository, chat, or client-side JavaScript.
  4. Send a test request. Check the JSON, field names, instrument code, available historical period, authorization errors, and indicator of quote freshness.
  5. Set up error handling. The application should respond correctly to an empty response, request limits, changes to the API schema, and temporary unavailability of a method.
Warning. Do not publish an API key in a public repository, Telegram bot messages, or code that runs in a browser. A compromised key allows third parties to consume your request quota and access the functions available to the token.

What if a test request returns a price but does not specify the data status? You cannot assume it is a real-time price. Check the field description, update time, delay, and trading mode, then record these conditions in the application's logic and user interface.

If you are building automation with neural networks, API keys require the same discipline. In the article about working with APIs and AI tools for SEO tasks we explain the general principle: secrets must not enter publicly accessible code, and the response from an external service must be checked before being used in a production workflow.

If you decide to choose a paid plan while reading, compare the official price with the partner price before subscribing directly: the difference is usually severalfold, and the calculation is provided at the beginning and end of the article.

How to Get Data on Gazprom, Sber, Lukoil, Yandex, and Ozon Stocks

Begin your search for a security in the directory of instruments for the selected API. Do not insert an assumed ticker into a request simply because it is familiar from a trading terminal or the news. The API may use a different code, a separate SECID or ISIN, or a combination of the security code and trading mode.

For Gazprom, Sber, and Lukoil stocks, when working with the Moscow Exchange, verify the actual identifier in the API directory, as well as the market, board, and settlement currency. A single ticker does not always uniquely identify an instrument. The security type, venue, trading mode, and date on which the directory is current all matter.

Yandex and Ozon stocks require an even more careful check of availability in a particular source. The instrument structure, trading venue, and identifiers may differ from the name expected by the user. A foreign provider may not cover the Russian market, while an exchange interface may display the instrument only in a specific data set.

A securities directory solves this problem better than a manually maintained ticker list. The application first searches for an instrument by name or code, then saves the confirmed identifiers and regularly updates the directory. This approach reduces the risk that a screener will start requesting the wrong stock after the data structure changes.

Why Free Quotes May Not Be Suitable for a Trading Robot

Historical candles are suitable for researching a strategy, building charts, and calculating indicators. A trading robot operates in a different environment: it needs price freshness, latency, feed completeness, connection stability, duplicate handling, and an understanding of the status of its own order.

Even a source available for free cannot automatically be considered sufficient for strategy execution. Delayed quotes may distort entry conditions, an incomplete order book will not show actual liquidity, and a missed message will change the signal calculation. If the API does not guarantee a streaming real-time data feed, the algorithm must account for this status rather than disguise it as a market price.

Also check separately how the service reports failures. The robot must distinguish between no trading, an empty response, a technical error, a request limit, and an outdated price. Without this logic, the application risks making the wrong decision based on data that appears correct on the surface.

Algorithmic trading requires testing not only the strategy but also the data channel. It is useful to simulate missing candles, duplicate messages, a change of trading session, and temporary API unavailability in advance. Materials from our AI in SEO category can help establish an approach to checking automated processes: a model or script should not make a critical decision without input data validation.

A practical example of choosing a source

An analyst is compiling a table of Russian stocks and wants to update prices and historical candles daily. First, they check the exchange interface, the availability of the instrument directory, and the structure of the historical data. The broker's API is connected only when the table needs to receive information about the analyst's own investment portfolio or submit trading orders.

This sequence saves integration time. For analytics, there is no need to connect the application to a brokerage account immediately, while account operations require more than a single source of historical data.

Common mistakes when working with stock market APIs

  • Using a ticker without checking the market, trading mode, and instrument identifier.
  • Treating delayed quotes as real-time data.
  • Ignoring the request limit and failing to provide retries after an error.
  • Storing the API key in open-source code, a client application, or a shared document.
  • Publishing quotes in a commercial service without checking the terms for data distribution.
  • Failing to process empty responses, changes to the JSON schema, and temporary endpoint unavailability.

What to check before connecting an API

Checking these points before development reduces the risk of rewriting the integration after launch. This is especially noticeable in projects where one source is needed for historical data, another for the portfolio, and a third for displaying quotes to users.

  • Whether the API supports the required stocks, exchanges, and markets.
  • Whether historical data is available for the required period and at the required candle frequency.
  • Whether the quotes are current or delayed.
  • How the API identifies an instrument: ticker, SECID, ISIN, board, or trading mode.
  • What response format the service uses and how it describes the fields.
  • What restrictions apply to requests and how the service reports errors.
  • Whether the provider permits the display, storage, and distribution of the received exchange data.
  • How the provider reports changes to the documentation and API schema.

For an investor's table or an educational project, a source with clear documentation and accessible historical data is usually sufficient. A public product, trading robot, or service with user data requires a separate assessment of the provider's terms, quote status, and the API's technical stability.

Frequently asked questions

Which stock APIs can be used for free?

Free options can be found among public exchange interfaces, broker APIs, and international financial data providers. The available markets, historical depth, request limits, and rules for using the information differ between them.

Where can I get an API key for stock quotes?

The key is usually created in the provider's account dashboard after registering an account or application. Some public API methods do not require an API key, but this does not eliminate request limits or data usage terms.

Can I obtain quotes for Russian stocks through an API?

Yes, if the selected source supports the Russian market and the required instrument. For an exact request, check the securities directory, instrument code, trading mode, market, and currency.

Is a free API suitable for a trading robot?

It may be suitable for a prototype, strategy research, or testing the processing of historical data. Before live trading, separately assess latency, connection stability, data completeness, account integration, and the order-submission mechanism.

Is a broker API needed for a table containing an investment portfolio?

Not always. If the table shows only public historical quotes and stock prices, an exchange API or data provider is sufficient. A broker API is needed when you need to automatically obtain positions, balances, and transactions for a specific account.

Can Moscow Exchange data be used in a public service?

Technical availability through MOEX ISS does not mean that the data can be freely distributed in any product. Before publishing quotes, charts, or exports, check the terms for using exchange information in your specific scenario.

  • Choose an API based on the task, not on the word “free.”
  • Check the quote status before building signals and reports.
  • Find Russian stocks through an up-to-date instrument directory.
  • Keep the access token outside the code and handle API errors.

SEO Mind42 publishes free practical materials on automation, APIs, and neural networks in promotion. Study the selected source's documentation before connecting: it determines the available data, restrictions, and rules for using it.

If free limits are insufficient, access to models via API can be arranged directly with the vendor or through the Clodex partner service — below is a comparison of official prices and the price through the partner. For example, GPT-5.6 Terra through the partner is 28,6 times cheaper than the official price — the full list of models is in the table.

Model price comparison table
ModelOfficial: input / outputThrough Clodex: input / output
qwen3.6-flashInput: 0,25 $ / 1 million tokens
Output: 1,5 $ / 1 million tokens
Input: 0,019 $ / 1 million tokens
Output: 0,019 $ / 1 million tokens
qwen3.6-plusInput: 0,5 $ / 1 million tokens
Output: 3 $ / 1 million tokens
Input: 0,032 $ / 1 million tokens
Output: 0,032 $ / 1 million tokens
qwen3.7-plusInput: 0,4 $ / 1 million tokens
Output: 1,6 $ / 1 million tokens
Input: 0,045 $ / 1 million tokens
Output: 0,045 $ / 1 million tokens
codex-auto-review—Input: 0,0525 $ / 1 million tokens
Output: 0,0525 $ / 1 million tokens
gemini-3.7-flashInput: 0,75 $ / 1 million tokens
Output: 3,75 $ / 1 million tokens
Input: 0,06 $ / 1 million tokens
Output: 0,24 $ / 1 million tokens
gemini-3.7-flash-highInput: 0,75 $ / 1 million tokens
Output: 3,75 $ / 1 million tokens
Input: 0,06 $ / 1 million tokens
Output: 0,24 $ / 1 million tokens
gemini-3.7-flash-lowInput: 0,75 $ / 1 million tokens
Output: 3,75 $ / 1 million tokens
Input: 0,06 $ / 1 million tokens
Output: 0,24 $ / 1 million tokens
gemini-3.7-flash-mediumInput: 0,75 $ / 1 million tokens
Output: 3,75 $ / 1 million tokens
Input: 0,06 $ / 1 million tokens
Output: 0,24 $ / 1 million tokens
qwen-image-2.0—0,06 $ / шт.
gpt-5.6-lunaInput: 0,2 $ / 1 million tokens
Output: 1,2 $ / 1 million tokens
Input: 0,063 $ / 1 million tokens
Output: 0,504 $ / 1 million tokens
grok-composer-2.5-fast—Input: 0,068 $ / 1 million tokens
Output: 0,068 $ / 1 million tokens
clodex-cursor—Input: 0,07 $ / 1 million tokens
Output: 0,07 $ / 1 million tokens
gpt-5.6-terraInput: 2 $ / 1 million tokens
Output: 12 $ / 1 million tokens
Input: 0,07 $ / 1 million tokens
Output: 0,56 $ / 1 million tokens
deepseek-v4-proInput: 1,32 $ / 1 million tokens
Output: 3,96 $ / 1 million tokens
Input: 0,08 $ / 1 million tokens
Output: 0,08 $ / 1 million tokens
grok-4.5Input: 2 $ / 1 million tokens
Output: 6 $ / 1 million tokens
Input: 0,08 $ / 1 million tokens
Output: 0,08 $ / 1 million tokens
grok-4.6Input: 2 $ / 1 million tokens
Output: 6 $ / 1 million tokens
Input: 0,08 $ / 1 million tokens
Output: 0,08 $ / 1 million tokens
clodex-cursor-pro—Input: 0,084 $ / 1 million tokens
Output: 0,084 $ / 1 million tokens
gemini-3.6-flashInput: 0,75 $ / 1 million tokens
Output: 3,75 $ / 1 million tokens
Input: 0,09 $ / 1 million tokens
Output: 0,36 $ / 1 million tokens
kimi-k3—Input: 0,09 $ / 1 million tokens
Output: 0,09 $ / 1 million tokens
glm-5.2—Input: 0,1 $ / 1 million tokens
Output: 0,1 $ / 1 million tokens
gpt-image-2—0,1 $ / шт.
nano-banana-2—0,1 $ / шт.
deepseek-v4-flashInput: 0,44 $ / 1 million tokens
Output: 1,32 $ / 1 million tokens
Input: 0,12 $ / 1 million tokens
Output: 0,12 $ / 1 million tokens
qwen-image-2.0-pro0,075 $ / шт.0,12 $ / шт.
qwen-image-3.0-pro—0,12 $ / шт.
qwen3.7-maxInput: 2,5 $ / 1 million tokens
Output: 7,5 $ / 1 million tokens
Input: 0,13 $ / 1 million tokens
Output: 0,13 $ / 1 million tokens
glm-5.3—Input: 0,15 $ / 1 million tokens
Output: 0,15 $ / 1 million tokens
MiMo-V2-Flash—Input: 0,162116 $ / 1 million tokens
Output: 0,162116 $ / 1 million tokens
qwen3.8-max—Input: 0,17 $ / 1 million tokens
Output: 0,17 $ / 1 million tokens
grok-imagine-video-1.5—0,18 $ / шт.
MiniMax-M2.1—Input: 0,2 $ / 1 million tokens
Output: 0,2 $ / 1 million tokens
MiniMax-M2.5—Input: 0,22233 $ / 1 million tokens
Output: 0,22233 $ / 1 million tokens
MiniMax-M2.7—Input: 0,22233 $ / 1 million tokens
Output: 0,22233 $ / 1 million tokens
MiniMax-M3—Input: 0,22233 $ / 1 million tokens
Output: 0,22233 $ / 1 million tokens
gpt-5.5Input: 5 $ / 1 million tokens
Output: 30 $ / 1 million tokens
Input: 0,25 $ / 1 million tokens
Output: 1,5 $ / 1 million tokens
gpt-5.6-solInput: 5 $ / 1 million tokens
Output: 30 $ / 1 million tokens
Input: 0,25 $ / 1 million tokens
Output: 2 $ / 1 million tokens
claude-haiku-4-5Input: 1 $ / 1 million tokens
Output: 5 $ / 1 million tokens
Input: 0,2805 $ / 1 million tokens
Output: 1,4025 $ / 1 million tokens
claude-haiku-4-5-20251001Input: 1 $ / 1 million tokens
Output: 5 $ / 1 million tokens
Input: 0,2805 $ / 1 million tokens
Output: 1,4025 $ / 1 million tokens
claude-opus-4-7Input: 5 $ / 1 million tokens
Output: 25 $ / 1 million tokens
Input: 0,3 $ / 1 million tokens
Output: 1,5 $ / 1 million tokens
claude-sonnet-4-6Input: 3 $ / 1 million tokens
Output: 15 $ / 1 million tokens
Input: 0,34125 $ / 1 million tokens
Output: 1,70625 $ / 1 million tokens
claude-sonnet-5Input: 2 $ / 1 million tokens
Output: 10 $ / 1 million tokens
Input: 0,35 $ / 1 million tokens
Output: 1,75 $ / 1 million tokens
Kimi-K2—Input: 0,423486 $ / 1 million tokens
Output: 0,423486 $ / 1 million tokens
Kimi-K2-Thinking—Input: 0,423486 $ / 1 million tokens
Output: 0,423486 $ / 1 million tokens
MiniMax-M2.7-highspeed—Input: 0,44466 $ / 1 million tokens
Output: 0,44466 $ / 1 million tokens
claude-opus-4-8Input: 5 $ / 1 million tokens
Output: 25 $ / 1 million tokens
Input: 0,45 $ / 1 million tokens
Output: 2,25 $ / 1 million tokens
kimi-k2.5—Input: 0,489655 $ / 1 million tokens
Output: 0,489655 $ / 1 million tokens
kimi-k2.6—Input: 0,701398 $ / 1 million tokens
Output: 0,701398 $ / 1 million tokens
kimi-k2.7-code—Input: 0,701398 $ / 1 million tokens
Output: 0,701398 $ / 1 million tokens
claude-opus-5Input: 5 $ / 1 million tokens
Output: 25 $ / 1 million tokens
Input: 0,85 $ / 1 million tokens
Output: 0,85 $ / 1 million tokens
kimi-k2.7-code-highspeed—Input: 1,402797 $ / 1 million tokens
Output: 1,402797 $ / 1 million tokens
claude-fable-5Input: 10 $ / 1 million tokens
Output: 50 $ / 1 million tokens
Input: 2,5 $ / 1 million tokens
Output: 2,5 $ / 1 million tokens

Partner price source: Clodex. Price check date: 2026-08-18.

SEO Mind42 does not sell API access or provide tokens: we recommend a third-party service Clodex. This is an affiliate link.

Compare models before you start

The service sets its plans, limits and model catalog. If they differ from this article, contact us so we can update it and record a new review date.

Browse models

Affiliate link: your price stays the same and the project earns a commission.

free stock api

SEO Mind42 editorial team

We explore SEO and neural networks in practice: test services on our own projects, verify prices and limits against primary sources, and share things you can put to use the same day.

📚 Reference guide to SEO and AI 🔄 Materials are updated 🕐 Updated: 4 October 2026

Related reading

All in this section →