Finage
DATA · DATA & ANALYTICS
Quotes, trades, fundamentals and market calendars across stocks, forex and crypto.
Connect Finage with Fabriq Developer
Your user pastes their Finage credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Finage in practice
Finage needs two different credentials: an `apikey` query parameter for the REST endpoints and a separate socket key that goes inside the WebSocket URL, and its own error list includes "401 - use your socket key to connect" for people who mix them up. The plans advertise unlimited API calls and the documentation publishes no rate limit, connection cap or subscription cap anywhere.
Scopes that draw scrutiny
apikey (REST) and socket key (WebSocket)Two unscoped credentials from the dashboard. The REST key travels in the query string — https://api.finage.co.uk/last/stock/{symbol}?apikey=… — so it is captured by any proxy or access log in the path.
Rate limits
- The plan pages advertise "Unlimited API Calls" and publish no per-second or per-minute figure.
- The WebSocket documentation documents no connection count or symbol-subscription cap either, so both have to be established with support.
Worth knowing
- Because the REST credential is a query parameter rather than a header, it ends up in logs, referrers and cached URLs, and cannot be redacted by header-level scrubbing.
- Entitlement, not the endpoint, decides what you get: the plans separate US market data from global, and real-time global from delayed global, so the same call returns different freshness on different subscriptions.
- WebSocket auth failures surface as 401s inside the socket handshake ("invalid socket key", "use your socket key to connect") rather than as an HTTP response you can inspect normally.
Checked against Finage documentation (2026-09-29), Finage WebSocket (2026-09-29), Finage pricing (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Finage behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.