Integration hub

Build sites, dashboards, apps, and AI agents with FXMacroData.

Start with the outcome you want, then choose the right delivery pattern. Use REST for current and historical records, webhooks or changes polling for serverless updates, SSE or WebSocket streams for always-on listeners, and MCP for AI tools that need live macro context.

Choose a pattern AI builder brief API reference Supabase guide

Choose by goal

Start here if you are not sure which docs to open.

Most integrations are one of these patterns. The safest default is server-side REST plus caching. Add webhooks, changes polling, or SSE only when your product needs incremental updates after the first load.

What you are building	Use this pattern	Open these docs
Website or SaaS app Customer-facing pages, paywalled data, custom dashboards.	Backend API route or server function. Keep the API key on the server. Cache current state from `/v1/announcements/{currency}/latest`.	Quickstart and API reference
Dashboard or internal tool Analyst dashboard, market monitor, internal research page.	REST bootstrap, scheduled refresh, and optional changes polling for incremental updates.	Plotly Dash guide
Serverless app Supabase, Vercel, Cloudflare Workers, scheduled jobs.	Short-lived functions for REST, webhooks, and changes polling. Use an always-on worker for persistent streams.	Supabase guide and webhooks
AI agent Chat assistant, research agent, trading prep workflow.	MCP when the agent client supports tools. REST tool calls when you control the agent runtime.	MCP server, prompt library, and OpenAPI reference
Real-time release workflow Alerts, release automation, cache invalidation.	Webhooks for callbacks. SSE or WebSocket for always-on listeners. Changes polling for serverless fallbacks.	Webhooks, SSE, and WebSocket
Spreadsheet or BI report Excel, Google Sheets, Power BI, QlikView.	Direct REST calls from the approved connector, usually with scheduled refresh and narrow endpoint selection.	Excel, Google Sheets, Power BI, QlikView
Trading platform workflow MetaTrader, NinjaTrader, TradingView, alert overlays.	Platform connector or webhook workflow. Keep heavy history and API keys outside chart scripts when possible.	MetaTrader, NinjaTrader, Pine Script
Commercial redistribution Your customers see FXMacroData-powered data in your product.	Backend cache, partner metering, and customer-visible data served from your app rather than direct browser API keys.	Redistribution pixel and startup workflows

Recommended architecture

Use one flow across most products.

1. Discover

Call /v1/data_catalogue/{currency} before hardcoding indicator slugs.

2. Bootstrap

Load current state with /v1/announcements/{currency}/latest.

3. Backfill

Fetch history only for indicators your product uses. Cache those rows.

4. Update

Use webhooks, changes polling, SSE, or WebSocket streams for new releases.

5. Serve

Serve your users from your backend, database, dashboard, or agent tool layer.

Copyable requests

Start with narrow calls, then add live updates.

Bootstrap latest

Load current values for one currency.

Use this for first page load, daily repair jobs, or current-state cache refreshes.

curl "https://api.fxmacrodata.com/v1/announcements/usd/latest"

Protected currency

Use your key for non-USD data.

Keep the key in server secrets, environment variables, or your backend vault.

curl "https://api.fxmacrodata.com/v1/announcements/eur/latest?api_key=YOUR_API_KEY"

Incremental sync

Poll recent changes instead of every slug.

Use this when your runtime cannot keep a persistent SSE or WebSocket connection open.

curl "https://api.fxmacrodata.com/v1/announcements/changes?currencies=g10&payload=full&limit=100&api_key=YOUR_API_KEY"

Webhook subscription

Let FXMacroData call your server.

Best for alerts, downstream jobs, and cache invalidation after a release lands.

curl -X POST "https://api.fxmacrodata.com/v1/webhooks/subscriptions?api_key=YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/fxmacrodata/webhook",
    "events": ["announcement"],
    "currencies": ["usd", "eur"],
    "indicators": ["inflation", "policy_rate"]
  }'

For AI-assisted builders

Give your coding tool a complete brief.

If you are building with Codex, Cursor, Claude, ChatGPT, or another AI coding tool, start with a clear implementation brief. The brief should say where the API key lives, which endpoint family to use, how to cache data, and how live updates should arrive. That produces better code than asking for a generic API integration.

Brief for a website or dashboard

Build a server-side FXMacroData integration for a financial dashboard.
Keep FXMACRODATA_API_KEY on the server only.
On first load, call:
https://api.fxmacrodata.com/v1/announcements/usd/latest
For protected currencies, call:
https://api.fxmacrodata.com/v1/announcements/eur/latest?api_key=YOUR_API_KEY
Cache the latest values in the app database.
Do not call every indicator every minute.
Use /v1/announcements/changes for incremental updates.

Brief for an AI agent

Build an FXMacroData macro research agent.
Use MCP if the client supports MCP tools.
Use REST tool calls if the app owns the agent runtime.
Before requesting indicators, call:
https://api.fxmacrodata.com/v1/data_catalogue/usd
Use announcement endpoints for historical rows.
Use calendar endpoints for upcoming release checks.
Return source, period, value, prior, and announcement_datetime.

MCP setup Prompt library MCP client article Custom GPT guide

Delivery choices

REST, changes, webhooks, streams, and MCP each have a clear job.

REST

Use for deterministic current values, history, calendar rows, predictions, COT, commodities, and FX rates.

Open reference

Changes polling

Use from short-lived workers or scheduled jobs when you need recent release changes without polling every slug.

See Supabase pattern

Webhooks

Use when FXMacroData should call your HTTPS endpoint after matching announcement events.

Open webhook docs

SSE and WebSocket

Use from always-on workers or services that can hold a persistent real-time connection.

Open stream docs

MCP

Use when an AI client can call FXMacroData tools directly for research, charts, calendars, and release context.

Open MCP docs

Widgets and embeds

Use when you want an embeddable calendar or market component without building the full data layer yourself.

Browse widgets

Production checklist

Use this before you ship.

Keep API keys server-side. Do not place production keys in browser JavaScript, mobile apps, or public repositories.
Call the data catalogue first. Use /v1/data_catalogue/{currency} to discover supported indicators.
Bootstrap once per currency. Use /v1/announcements/{currency}/latest instead of one request per slug.
Cache historical rows. Fetch back history only for the indicators your product uses.

Use incremental updates. Prefer webhooks, changes polling, SSE, or WebSocket streams after bootstrap.
Store cursors and timestamps. Persist the last processed change cursor or announcement timestamp.
Handle retries idempotently. A webhook or worker retry should update the same release row, not duplicate it.
Show source-aware fields. Preserve period, value, prior value, revision fields, and announcement timestamps in your UI.

Key Facts

Page

Integrations

Section

Documentation

Canonical URL

https://fxmacrodata.com/pt/documentacao/integrations

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 Integrations 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.