Base URLs
| Environment | URL |
|---|---|
| Production | https://api.venlyfinance.com/v1 |
| Staging | https://api-staging.venlyfinance.com/v1 |
Authentication
All endpoints require a Bearer token in theAuthorization header. Obtain one using OAuth2 client credentials:
Idempotency, pagination, versioning
Both APIs follow shared conventions for idempotent retries, list pagination, and version stability. See the API Conventions page for the full rules.Data model
Every Finance API resource hangs off a party. Parties hold accounts; accounts hold wallets and virtual bank accounts; wallets and IBANs are the entry points for crypto and fiat respectively. New here? Start with Getting started for the party → account → verification → IBAN flow, read the data model in depth, or follow the full Integration Walkthrough.Resources
Parties
Onboard individuals and organisations. The foundation of every account.
Accounts
Create and manage financial accounts with role-based party access.
Virtual Bank Accounts
Assign IBANs for EUR SEPA pay-ins linked to accounts.
Wallets
Generate blockchain wallets on Base or Avalanche for crypto settlement.
Transfers
Execute fiat and crypto transfers between accounts.
Fiat-to-Crypto Payment Sessions
Generate pay-in sessions that convert fiat deposits to crypto.
Payment Requests
Create payment requests for account or card provider integrations.
Permits
Manage EIP-712 permit signatures for token approvals.
Allowances
Query token allowances for wallets.
Next Steps
Getting Started
Create a party, open an account, and get verified — with managed and self-custody examples.
Integration Walkthrough
The full end-to-end flow, from onboarding to settling a transfer.
Account verification
Why accounts start unverified and how a Venly admin approves them.
Authentication
Token exchange, refresh patterns, and environment URLs.

