Trading Economics: economic data, release calendars and APIs for brokers

Trading Economics supplies economic time series, release calendars, market information and forecasts through its website and data interfaces. For a brokerage, the practical roles include an economic-calendar component, research inputs, market commentary and licensed data in customer applications. It provides information for those workflows; the reviewed API service describes data delivery rather than order execution or custody. Product coverage, refresh frequency and redistribution rights need to be selected together.[2][26]

The database service brings together series with different geographic coverage, histories and publication cycles. A national inflation series, a regional indicator and a market quote are therefore different data objects. Their units, frequency, reference period and source matter as much as the latest number. A brokerage building a recurring macro report benefits from stable identifiers and explicit series selection rather than treating a broad catalogue description as the purchased dataset.[3]

Trading Economics describes its forecasts as outputs from a global macroeconomic model combined with analyst expectations and relationships between countries. The product page covers the next four quarters or three years, with revisions as information changes. These are model estimates: a forecast horizon is different from a promised delivery schedule, and a projected market value is different from a price available for execution.[7]

The API documentation accepts credentials through supported URL parameters or an authorization header. A firm can use the language packages or build directly against HTTP. In a customer-facing application, a server-side integration keeps a shared subscription credential out of a public browser bundle. This is an implementation implication of authenticated access, rather than a claim that Trading Economics manages the brokerage’s application security.[8]

The MCP catalogue includes country and market searches, economic indicators, calendars, historical observations, forecasts and company financial information. It lets an AI workspace retrieve structured inputs without an analyst constructing each request manually. The published tools reviewed here do not list order placement or settlement. A generated explanation still needs the underlying series identity, observation date and source context; access through an AI client does not change the meaning or licence of the retrieved data.[12]

Calendar streaming uses a persistent WebSocket connection, with an API key and secret and an explicit calendar subscription. That mechanism reduces the need to repeatedly request the same event list. It does not itself establish an end-to-end latency commitment: the provider’s release timing, network delivery and the receiving application’s processing remain separate parts of the workflow.[13]

Trading Economics publishes individual and professional subscription tiers, while larger integrations are quoted. Its API overview says the commercial scope depends on functionality, request volume and distribution. A brokerage displaying data to clients should define that use before selecting a plan; a research seat and a redistributable product have different commercial purposes.[2]

The billing page accepts cards and PayPal, with bank transfers available for quarterly or annual subscriptions. Paid trials are non-refundable and convert to recurring billing unless cancelled before expiry. It describes an API trial allowance of 100,000 data points and 100 requests. Plans can be changed or cancelled, but unused subscription days do not receive a refund or credit. The displayed monthly charges should not be mistaken for a tax-inclusive enterprise quotation.[15]

An enterprise agreement must define the feeds, permitted audience and redistribution rights. Internal analytical access does not itself establish permission to republish data to a broker’s customers or partners.[2]

Implementation starts with the data model: choose series and instruments, establish the required history and frequency, and map the returned identifiers into the brokerage’s systems. For a live calendar, distinguish the event’s scheduled publication time from its economic reference period. For a historical store, preserve provider update timestamps so a revised observation can replace the right record without being mistaken for a new period.[16][27]

The API separates several failure conditions. Its status guide associates 401 with credentials or access, 403 with blocked access or exhausted download allowance, and 409 with request throttling; malformed requests can return 400. That distinction matters operationally: repeatedly retrying an entitlement problem will not restore a missing subscription, while a rate-related response calls for slower scheduling. Applications should keep the original response context for support.[19]

A practical deployment therefore needs a release-timezone rule, a revision policy, a quota monitor and explicit handling for missing or stale observations. These are consequences of the documented fields and limits, not evidence of a managed monitoring service included in every subscription. The data source can supply an updated record while the brokerage remains responsible for refreshing its own cached chart, research page or customer notification.[27][17]

Professional includes prioritised developer and analyst assistance. Enterprise advertises an account manager, 24/7 priority support and tailored onboarding. Those descriptions do not specify a universal response-time guarantee.[14]

The API enquiry form accepts a service question together with contact and country information, with company and telephone fields available. It is an appropriate route for discussing feed coverage, redistribution and a larger commercial requirement. Developer documentation provides the public reference for endpoints and response handling; an enquiry form is not an incident-status dashboard.[21][19]

The general terms grant a personal, revocable and non-transferable licence and provide the service on an as-available basis, without a general accuracy or availability warranty. Their restrictions should be read alongside any negotiated commercial agreement. They also allow Trading Economics to end access with or without cause or notice, while a user may discontinue use and notify the provider. A business that needs contractual continuity, redistribution or a defined service remedy needs those provisions in its agreement.[22]

The United States stock-market page contains a material qualification for index users: displayed index information can be based on OTC instruments, CFDs, perpetual futures or other derivatives. It is supplied for general reference and can differ from official index levels, exchange data or settlement values. That disclosure belongs to the relevant index data; it should neither be omitted from a trading-related display nor incorrectly extended to every official economic statistic in the database.[24]

The privacy policy says the Google Sheets integration uses permissions to read and write spreadsheets and operate its interface. It states that Google user data is not persistently stored on Trading Economics servers or used to train AI models, and that access can be revoked through Google permissions. Those statements address Google-connected data handling; they do not describe every possible AI client a brokerage might connect to the MCP endpoint. Privacy requests go to the published privacy address.[23]

The services reviewed are data and research tools. This profile does not identify a brokerage, deposit-taking or execution permission for the subscription itself. A price dataset also does not establish benchmark-administrator status or a right to use third-party exchange and index intellectual property. The relevant question is the exact dataset and licensed application, with the product’s own origin and use restrictions retained.[22][24]

Trading Economics presents itself as a global economic-information service. Its About page describes official underlying sources for economic indicators, while other product pages describe proprietary forecasts and market datasets. This combination is useful for an analyst seeking several kinds of inputs in one workflow, but the brand’s breadth should not obscure their different origins. Catalogue counts appearing on individual pages are not a reliable substitute for checking the specific series and product entitlement.[1][7]

The official Android app listing identifies IEconomics Inc. as the developer and publishes an address at 1 World Trade Center, floor 85, New York, NY 10007, United States. That establishes an associated company identity in the app channel. The website pages reviewed mainly use the Trading Economics brand, so the app listing alone does not prove which entity will sign every B2B data agreement or establish a universal headquarters for all services.[25]

Its API customer page describes both individual analytical use and business applications built around the data. That supports a broad customer scope including researchers, financial firms and software teams. This profile does not convert a generic use-case description into a claim that a named broker is an active customer, or that a particular customer application is licensed under a standard individual subscription.[26]

Operator

Trading Economics; IEconomics Inc. is identified in its official Android app listing

Service scope

Economic indicators, release calendars, financial-market series, company fundamentals and forecasts for research and licensed applications.

Customer types

Financial institutions; Broker research teams; Asset managers; Economic researchers; Application developers; Data publishers

Delivery

SaaS; API; Hosted

Pricing publication

Public and quoted pricing

Platforms

Trading Economics website; Trading Economics mobile applications

Integrations

REST API; Python; Node.js; Microsoft Excel; Google Sheets; WebSocket calendar stream; Trading Economics MCP server

Pricing scope

Published subscriptions and negotiated enterprise scope; dataset and distribution requirements affect the commercial agreement.

Implementation

Select datasets and rights, authenticate the chosen interface, map timestamps and series identifiers, and manage quotas and revisions in the receiving application.

Support

Public developer documentation and an API enquiry form; enhanced support depends on subscription tier.

Permissions and regulatory scope

Data and research services. Dataset licensing and intellectual-property rights are distinct from a brokerage or execution permission.

Provider metadata checked 20 Oct 2026Source 2Source 26Source 8Source 21Source 25Source 22Source 16Source 27

The point-in-time page’s published request example shows a calendar date-range query; it does not, on that page, document a separate as-of or vintage-selection parameter. The stated offering is relevant to research that must avoid using later revisions, but the example alone is insufficient to establish the vintage behaviour of every field or every economic series. A backtest depending on original consensus and first-release values needs that precise dataset scope established.[29]

Series continuity deserves similar care. A changed base year can alter a level series without representing a new economic event; a replaced or discontinued indicator may require a new identifier. Retaining the provider’s change information alongside the downloaded observations makes those decisions traceable. It also helps an editor explain why a historical chart or comparison differs from an earlier edition of a research article.[28]