Ebury
Cross-border payments and FX platform for SMEs and mid-market companies.
- Category
- Payments & Banking
- Type
- Cross-Border payments
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- OAuth 2.0
- Docs
- Ebury API docs
02Data
What you can sync.
- Trades
- Payments
- Beneficiaries
- Balances
- Quotes
Bring Ebury trades into the same model as revenue and costs, so finance and operations read the same numbers.
Need more? Name any other Ebury data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- OAuth 2.0 (client ID, client secret, refresh token)
Ebury uses OAuth 2.0 (client ID, client secret, refresh token). You add the credentials once, when the AI asks for them, and it tells you where to create them in Ebury if you need help.
04How it works
How it works in DataMind.
-
Pick Ebury.
Open Lake, pick Ebury in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Ebury API docs.
-
Answer a few questions.
The AI reads the Ebury documentation, then asks which credentials you will use, which data to sync (for example trades and payments), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Ebury data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
