FXMacroData for iPhone, iPad, Mac, Calendar, and Shortcuts
This page shows the Apple-friendly ways to use FXMacroData: calendar subscriptions, Safari Home Screen installs, Universal Links, Smart App Banners, notifications, widgets, and Shortcuts workflows.
Calendar first
Apple Calendar can subscribe to live FXMacroData release feeds now. USD is public; non-USD and all-currency feeds use an API key in the URL.
Apple link behavior
Supported FXMacroData links keep users on public URLs and route to the best available Apple experience.
Alert ready
Release alerts can reach users through browser or native notifications after they grant permission and enable the alerts they want.
Apple Calendar subscriptions
Use the production calendar feed for iOS, iPadOS, macOS, Outlook, and other iCalendar clients. Add alarm_minutes to include a display reminder inside each event.
Public USD feed
webcal://fxmacrodata.com/release-calendar.ics?currency=USD&alarm_minutes=15
Use webcal:// when opening from Apple Calendar. Use https:// for download or server-side checks.
Paid currency feed
https://fxmacrodata.com/release-calendar.ics?currency=EUR&api_key=YOUR_API_KEY&alarm_minutes=30
Public examples use query-parameter authentication because calendar clients do not reliably send custom API-key headers.
Safari and Home Screen web app
FXMacroData ships a web manifest, Apple touch icon, installable standalone display mode, and a service worker. Safari users can add the dashboard to the Home Screen for quick access from iPhone, iPad, or Mac.
Install target
Start from Market Summary or Release Calendar for repeat-use workflows.
Notifications
Use release-calendar alerts for upcoming macro events. Browser or native notifications should respect the user's alert preferences and device permission state.
Smart App Banner
Safari app banners can help users move from the web page into a compatible app when one is available.
Universal Link behavior
The public association endpoints at /.well-known/apple-app-site-association and /apple-app-site-association advertise supported Apple link behavior. They help Apple clients route supported FXMacroData links to the best available experience without changing the public URL.
Public association endpoints
/.well-known/apple-app-site-association /apple-app-site-association
These URLs should remain JSON responses without redirects and without cookies so Apple can verify the domain.
Native associated domains
applinks:fxmacrodata.com webcredentials:fxmacrodata.com
Associated domains should cover only public user-facing paths. Checkout, API, auth, and account-management paths stay web-only.
| App route | Recommended native destination |
|---|---|
/dashboard/release-calendar |
Calendar tab with current filter state. |
/dashboard/{BASE_QUOTE} |
Pair detail screen with macro indicators and latest release state. |
/api-data-docs/{currency}/{indicator} |
Endpoint reference or in-app data preview for the same series. |
/articles/{slug} |
Article reader with a fallback to Safari if native article rendering is not ready. |
Shortcuts, App Intents, widgets, and Siri
The native app should expose the highest-value read-only workflows as App Intents so users can automate market prep from Shortcuts and Siri without building a full scripting surface on day one.
First App Intents
- Get upcoming releases for a currency.
- Get the latest indicator reading for a currency and indicator.
- Open an FX pair dashboard.
- Subscribe to a calendar feed for a currency.
API calls for Shortcuts
GET https://fxmacrodata.com/api/announcements/usd/inflation GET https://fxmacrodata.com/api/calendar/usd
Protected Shortcuts should read the API key from the app's secure storage and append it as api_key only at request time.
Privacy, account, and access notes
Use Apple sign-in where users expect it
If Apple-platform login is offered, Sign in with Apple gives users a familiar account path.
Keep account and billing flows clear
Users should know when they are opening account, subscription, or billing pages in the web experience.
Protect paid data access
Non-USD data, alerts, and calendar scopes should require a signed-in account or user-provided API key; examples should use placeholders only.