Build once. Connect widely.
Use versioned REST APIs and signed webhooks across participating providers.
Quickstart
Create a purpose-bound permission, send the customer to the returned authorization URL and listen for lifecycle events.
POST /api/v1/permissions{
"purpose": "income_verification",
"scopes": [
"account.identity",
"income.summary"
],
"access_type": "ONE_TIME"
}Provider adapters
Every bank and MNO integrates through the same Financial Provider Adapter contract.
GET /capabilitiesDiscover account types, scopes and channels.POST /authorizationsStart a provider-controlled authorization.GET /accountsReturn canonical financial accounts.GET /transactionsReturn normalized, scoped transactions.Webhooks
Events include a unique event ID, timestamp, signature, delivery ID and correlation ID. Consumers must be idempotent because delivery is at least once.
permission.approvedpermission.revokedconnection.verifiedverification.completed