Website
fxmacrodata.com pages, dashboards and documentation.
Operational transparency
System status
Each component below is checked directly against production from the FXMacroData service itself, at most once a minute, when this page is opened. What you see is the result of that check, not a declared state.
Checking
Running live checks against production.
Components
Response code and round-trip time from the most recent check. A component reads operational only when its production endpoint has just answered.
REST API
api.fxmacrodata.com, health endpoint.
Announcements data
A stored USD release row read through the API.
Live release events
The changes feed behind SSE, WebSocket and webhook delivery.
GraphQL
api.fxmacrodata.com/v1/graphql.
MCP server
mcp.fxmacrodata.com, tools/list over Streamable HTTP.
OpenAPI schema
api.fxmacrodata.com/openapi.json.
Operational answered 2xx or 3xx within the timeout
Degraded answered, but with a client error or slower than five seconds
Outage server error, timeout or refused connection
Incident history and delivery speed
Two records sit alongside the live checks.
Incidents and maintenance
Incident timelines, post-incident notes and scheduled maintenance are posted on the FXMacroData status feed, where you can also subscribe to updates.
Release speed
How quickly each official release was available through the API after the publisher released it, measured release by release in milliseconds.
Data corrections
Dated record of data and service issues and what was done about them.
Seeing something different?
If a component shows operational here but your integration is failing, email info@fxmacrodata.com with the request path, the response code, the time in UTC and the first eight characters of your API key. Support terms are on the support page.