Reference & Lookup Data · Integration
OANDA
Add OANDA to your product for your customers, and give your AI agents governed access to it.
Embed an OANDA integration so your product can price, convert and report in the currencies your customers actually trade in, using rate data they trust. OANDA publishes current and historical foreign exchange rates across a wide set of currency pairs, including period averages and end of day rates for a chosen date, which is what makes it usable for revaluation and reporting rather than only a live display. Each customer connects their own OANDA subscription, so requests run under their entitlement and their usage is attributable to them instead of pooled through a shared key. fastn owns the credential storage, retries, throttling and API upkeep, and the same governed connection is what your AI agents read.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Convert amounts in your product using current rates from each customer's own OANDA subscription, with no per-customer code.
Read the historical rate for a specific date so a restatement or a revaluation uses the rate that actually applied.
Show multi-currency totals in a customer's reporting currency without you maintaining a rate table.
Keep rate requests attributable per tenant so entitlement and volume follow the customer that used them.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent converts figures across currencies while answering a finance question, with each rate lookup logged.
An agent explains how a currency moved between two dates using historical rates rather than a guess.
An agent reads the rates it needs for a report within scoped permissions, using only that tenant's subscription.
Example prompt
Convert these invoice totals to our reporting currency using the OANDA rate on each invoice date.
Set up OANDA in 4 steps
- 01Enable the OANDA connector in your fastn dashboard.
- 02Have each customer supply credentials for their own OANDA subscription so requests run under their entitlement.
- 03Map the currency pairs and rate types your product uses, per customer, as configuration.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the OANDA integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an OANDA integration without building it. Your customers connect their own OANDA account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an OANDA update is not your on-call problem.
- One integration serves your product and your agents. The same governed OANDA connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Works well with
QuickBooks
NetSuite
SnowflakeOften used alongside
Tools the same teams tend to run next to OANDA, across other categories.
Salesforce
HubSpot
Notion
BoxOANDA integration FAQ
How do I add an OANDA integration to my product?
Enable the OANDA connector in your fastn dashboard, then let each customer authenticate their own OANDA account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no OANDA client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own OANDA account?
Yes. Every connection is scoped to the individual customer, so each authorises their own OANDA account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this OANDA integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent converts figures across currencies while answering a finance question, with each rate lookup logged.
Who maintains the OANDA integration?
fastn does. When OANDA changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does an OANDA lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should OANDA results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. OANDA is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the OANDA integration?
A common starting point: convert amounts in your product using current rates from each customer's own OANDA subscription, with no per-customer code. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the OANDA integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding OANDA does not change your per-connector cost. You can start free with 3 connected accounts.
Add OANDA to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.