Documentation

API Changelog

Material endpoint contract changes for the FXMacroData API: response schemas, endpoint lifecycle changes, authentication behavior, rate limits, and streaming payload changes.

OpenAPI schema API reference Issue log

2026-07-18 Predictions response groups forecasts by announcement

Changed The GET /v1/predictions/{currency}/{indicator} response now returns one data[] group per announcement_id. Forecast values live under data[].predictions[], so clients that previously read data[0].predicted_value should now read data[0].predictions[0].predicted_value or choose a specific entry by prediction_source.
Added Each prediction item can include prediction_type, prediction_source, prediction_source_label, generated_at, confidence, and prediction_reason. This supports multiple forecast sources for the same scheduled announcement.
Changed Prediction groups use the same announcement_id join key as announcement history, making it easier to connect forecast records with realised observations after release.

2026-07-14 Calendar, announcements, and predictions contract clarified

Changed The public endpoint contract is now documented as three distinct surfaces: GET /v1/calendar/{currency} for upcoming release schedules, GET /v1/announcements/{currency}/{indicator} for realised values and prior observations, and GET /v1/predictions/{currency}/{indicator} for forecast groups keyed by announcement_id.
Changed Calendar rows should be treated as schedule rows. Forecast and consensus values belong on the predictions endpoint, not on calendar responses.

2026-05-18 Rate-limit tiers published · per-key concurrency cap

Added Rate-limit budgets are now documented and enforced on API keys. Trial and Individual keys use 300/minute, 5,000/hour, and 100,000/day; Enterprise limits are governed by the customer agreement. See the full table in the rate-limit guide.
Added A per-key in-flight concurrency cap limits accidental single-key request fanouts that could otherwise degrade latency for other users. Trial and Individual keys default to 20 concurrent requests; Enterprise limits are contract-specific.
Added 429 responses now include an X-RateLimit-Window header identifying which budget tripped (minute, hour, day, endpoint, or concurrency) so clients can self-throttle the right dimension.
Changed Concurrency caps are designed for accidental fanout protection, not normal production request patterns. ETag / If-None-Match responses continue to avoid quota counting.

2026-03-30 Press-release and risk-sentiment endpoints added

Added Endpoint added: GET /v1/press-releases/{currency}. Responses return a paginated press-release feed with currency, count, and data[] records containing release titles, URLs, dates, summaries, and policy-context fields where available.
Added Endpoint added: GET /v1/risk_sentiment. Responses return a daily risk-on/risk-off score with score, regime, component metadata, data-quality metadata, and pagination fields.

2026-03-29 GDP response fields added

Added GDP announcement responses now include pct_change_qoq and pct_change_yoy fields alongside the absolute output level. No client-side calculation needed.

2026-03-27 Per-key rate limits and enterprise access tier

Added Per-key rate limiting is enforced on all endpoints. Rate limits vary by subscription tier and are documented in the rate limits guide.
Added Enterprise tier introduced for high-volume and commercial use cases. Contact us for custom limits and SLA terms.

2026-03-25 Live event streaming endpoint added

Added Endpoint added: GET /v1/stream/events for Server-Sent Events delivery of announcement events.
Added SSE clients can filter events with currencies and indicators, and can reconnect with Last-Event-ID to replay buffered events.
Added Stream events include stable identifiers and routing fields such as event_id, currency, indicator, records_written, and timestamp.

2026-03-25 COT, commodities, and calendar contracts changed

Changed GET /v1/cot/{currency} access now follows the same mixed-access pattern as announcements: USD requests are publicly accessible, while other currencies require a valid API key.
Changed GET /v1/commodities/{indicator} now requires a valid API key for every request.
Added Release-calendar rows can include additive routing metadata such as domain, endpoint_family, and endpoint_path, while keeping announcement_datetime and release stable.

2026-03-24 MCP transport endpoint added

Added MCP transport added at https://mcp.fxmacrodata.com for compatible clients. Authentication uses OAuth 2.0 + PKCE.
Added The MCP tool catalogue exposes announcement, release-calendar, data-catalogue, COT, commodities, and market-session query surfaces.

2026-03-23 GraphQL query interface

Added GraphQL endpoint added at POST /v1/graphql. Query indicator announcements, release calendars, and data catalogue entries using standard GraphQL syntax. Authenticate with a valid API key.

2025-11-13 Breaking change: policy_rate replaces interest_rates slug

Changed The indicator slug interest_rates is replaced by policy_rate across all currencies. Update your API calls — the old slug no longer works.

2025-11-06 Public API launch

Added FXMacroData public REST API launched with stable endpoint families for announcements, release calendars, data catalogue discovery, COT positioning, and commodities.
Added Release calendar endpoint launched: GET /v1/calendar/{currency} — lists upcoming economic data releases with scheduled announcement times.
Added COT positioning endpoint launched: GET /v1/cot/{currency} — weekly CFTC Commitment of Traders data for G8 futures contracts.
Added Commodities endpoint launched: GET /v1/commodities/{indicator} — daily energy prices (WTI, Brent, Natural Gas) and precious metals.
Added Data catalogue endpoint launched: GET /v1/data_catalogue/{currency} — discover which indicators are available for each currency, with metadata.

Key Facts

Page

Changelog

Section

Documentation

Canonical URL

https://fxmacrodata.com/ko/documentation/changelog

Source

FXMacroData editorial and official publisher references

Last Updated

See page metadata

Provenance And Trust

Cite the canonical URL and source field above. Where available, this page maps to official publisher releases and timestamped updates.

Quick Q&A

What is this page about? This page explains Changelog with directly usable context for trading, research, and API workflows.

What source should be cited? Use the canonical URL and the listed source field; cite official publisher references when available.

How fresh is this content? The last updated value above reflects the page metadata or latest available data timestamp.

Can this be used in AI assistants? Yes. This section is intentionally structured for retrieval and citation in chat assistants.

Prompt Packs

Use these in ChatGPT, Claude, Gemini, Mistral, Perplexity, or Grok for consistent source-aware outputs.