Cowally API
Everything in Cowally, inside the product you already have.
Every Cowally service has an API, from onboarding and the decision engine to the core, products, documents, collections and analytics. Your developers plug in exactly what you need: the scoring engine inside your onboarding flow, documents inside your app, loans at your checkout, or your own app on top of the Cowally core.
Every service, ready to connect
Start applications, move them through steps, run checks and receive finished applications.
Send an application, get back the decision, the score and the reasons.
Customers, accounts, loans, balances and movements.
Loan products, payment schedules, payouts and repayments.
Accounts, goals, interest and balances.
Transfers, bills, QR and payments with a reference.
Uploads, checklists, correction requests, versions and signatures.
Send the loan book in, get strategies, contacts and results back.
The metrics and views behind every dashboard.
Issue, sign, endorse and keep promissory notes and CDTs.
Use one, or combine several; they share the same data.
What you can build
A scoring engine in your onboarding
Your form sends the applicant's data; the decision engine returns the decision, the score and the reasons; your app shows the result.
Documents in your app
Your app sends the documents customers upload; Cowally handles the checklist, corrections, versions and signatures, and returns each file's status.
Loans at your checkout
Your checkout asks for a loan offer, the customer accepts, and Cowally creates the loan and its payment schedule.
Your own app on the Cowally core
Your developers build the customer app you want; balances, loans, transfers and payments come from the Cowally core.
Collections on your loan book
Your current core sends the loan book; Cowally runs the strategies and returns contacts, promises and payments received.
Four ways teams use the API
Add a piece to your product
Plug one service into an app or website you already have.
Connect your current core
Run new products or tools on Cowally while your core keeps what it holds today.
Build your own channel
Design your own app or website on top of Cowally's services.
Feed your data platform
Bring Cowally's data into your own reports, data warehouse and BI tools.
How an integration goes
A first integration can take about a week.
Book a technical sessionHow we support your team
A technical session to start. Our architects map what you want to build and which services you need.
Full documentation and a test environment. Your developers get the documentation in the session and can build safely before going live.
Our engineers alongside yours. Questions answered while you build, and support once you're live.
For your developers
Documented APIs for every service.
Stable, versioned contracts that don't break when one side changes.
Access by role: each integration only reaches the data and actions it's allowed to.
Every call logged, with monitoring and alerts.
Private connectivity, with fixed IP addresses for your access lists.
Your data, your country, when your regulation requires it.
A test environment to build against before going live.
Questions about the API
All of them: onboarding, the decision engine, core banking, loans, savings, payments, documents, collections, analytics, and digital notes and custody.
Yes, the API is for your development team or your technology provider. If you'd rather not build anything, use the service inside Cowally, or give your people access through MCP.
We share the full documentation with your team in the technical session.
A first integration can take about a week.
Yes, so your team can build and test before going live.
Yes. They share the same data from the moment you combine them.
Per service, depending on your volumes.
Bring your developers
In a technical session, our architects will show the services running and walk your team through the integration.