Griffin
UK bank built for embedded banking with accounts, payments and compliance APIs.
- Category
- Payments & Banking
- Type
- Banking as a service
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- API key
- Docs
- Griffin API docs
02Data
What you can sync.
- Bank accounts
- Transactions
- Payments
- Legal persons
Bring Griffin bank accounts into the same model as revenue and costs, so finance and operations read the same numbers.
Need more? Name any other Griffin data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- An API key
Griffin uses an API key. You add the credentials once, when the AI asks for them, and it tells you where to create them in Griffin if you need help.
04How it works
How it works in DataMind.
-
Pick Griffin.
Open Lake, pick Griffin in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Griffin API docs.
-
Answer a few questions.
The AI reads the Griffin documentation, then asks which credentials you will use, which data to sync (for example bank accounts and transactions), 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 Griffin data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
