Use FXMacroData in QlikView
Load official-source macro indicators, release calendars, FX spot rates, commodities, and COT positioning into QlikView through the Qlik REST Connector and reusable FXMacroData load scripts.
Native REST path
QlikView uses the Qlik REST Connector, so no custom binary connector is needed for the first integration.
Reusable scripts
The package under extensions/qlikview/ includes subroutines for the main endpoint families.
Query-key auth
Protected routes use api_key=YOUR_API_KEY and keep the real key in a local include file.
QlikView setup
- Install the Qlik REST Connector for QlikView if it is not already available.
- Open Edit Script in your QlikView document.
- Create a REST connection named FXMacroData REST.
- Use
https://fxmacrodata.com/api/announcements/usd/inflation?limit=1as the seed URL. - Set the method to GET, authentication to Anonymous, and response type to auto-detected JSON.
- Enable Allow "WITH CONNECTION" so scripts can override the endpoint URL per table.
- Include the FXMacroData
.qvsscript, then call the loader subroutines you need.
The seed URL is only used when creating the REST connection. Runtime loads are directed by the QlikView script package.
Starter load script
Copy the include script into your QlikView app folder or shared reload include folder. Keep the API key in a separate local file.
$(Must_Include=fxmacrodata.qvs);
// $(Include=fxmacrodata-secrets.qvs);
CALL FXMD_LoadAnnouncements(
'FXMD_USD_Inflation',
'usd',
'inflation',
'2025-01-01',
'',
500
);
CALL FXMD_LoadReleaseCalendar(
'FXMD_USD_ReleaseCalendar',
'usd',
''
);
CALL FXMD_LoadForex(
'FXMD_EURUSD',
'eur',
'usd',
'2025-01-01',
'',
1000
);
For protected tables, set SET vFXMD_API_KEY = YOUR_API_KEY; in your local secret include.
Supported loader tables
| Loader | Endpoint | Primary fields | Auth |
|---|---|---|---|
FXMD_LoadAnnouncements |
https://fxmacrodata.com/api/announcements/{currency}/{indicator} |
currency, indicator, date, value, announcement_datetime |
USD public window; key for non-USD or full history |
FXMD_LoadReleaseCalendar |
https://fxmacrodata.com/api/calendar/{currency} |
currency, indicator, indicator_name, source, announcement_datetime |
Public for supported currencies |
FXMD_LoadForex |
https://fxmacrodata.com/api/forex/{base}/{quote} |
base, quote, date, rate |
Key for protected pairs |
FXMD_LoadCommodities |
https://fxmacrodata.com/api/commodities/{indicator} |
indicator, date, price, pct_change |
API key required |
FXMD_LoadCOT |
https://fxmacrodata.com/api/cot/{currency} |
currency, date, open_interest, noncommercial_net |
API key required |
Refresh guidance
- Use
start_date,end_date, andmax_rowsto keep reloads scoped. - Most macro datasets should reload around economic-release cadence, not every few minutes.
- Keep API keys out of shared QVW files, screenshots, and reload logs.
- For corporate proxies, configure proxy settings in the Qlik REST Connector connection.
Direct request examples
These are the same production URLs the QlikView scripts call through the REST Connector.
https://fxmacrodata.com/api/announcements/usd/inflation https://fxmacrodata.com/api/forex/eur/usd?api_key=YOUR_API_KEY https://fxmacrodata.com/api/commodities/gold?api_key=YOUR_API_KEY https://fxmacrodata.com/api/cot/usd?api_key=YOUR_API_KEY