Avaloq
Avaloq is a leading provider of wealth management technology and digital banking solutions, offering over 7,500 REST API endpoints for financial services integration. The platform connects more than 170 financial institutions with 200+ fintech partners through Community APIs, Standard Adapters, and certified integrations for banking, wealth management, payments, and compliance.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Avaloq the way a machine reads it — 85 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Avaloq scores 51.5/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Avaloq
Each block below is one kind of artifact we hold for Avaloq. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Avaloq Community API
Community APIs for fintech integration providing simplified REST endpoints for connecting third-party applications with the Avaloq banking platform. Pre-vetted by Avaloq for sec...
Avaloq Accounts API
Bank account management
Avaloq Customers API
Customer data management
Avaloq Payment Status API
Payment tracking and status
Avaloq Payments API
Payment instructions and transfers
Avaloq Transactions API
Transaction history and management
Open Collections 2
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Avaloq Banking API
OPEN COLLECTIONAvaloq Payments API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Avaloq Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Avaloq Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Avaloq Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
7500+ REST API Endpoints
Over 7,500 REST API endpoints for comprehensive banking and wealth management operations.
Community APIs
Pre-vetted REST APIs for seamless fintech integration with the Avaloq platform.
Standard and Certified Adapters
Three adapter types (Standard, Certified, Project) enabling ecosystem connectivity.
Cloud Sandbox
Sandbox access to Avaloq products in the cloud for integration testing.
Kafka Integration
Event-driven integration via Apache Kafka for real-time data streaming alongside REST APIs.
SOAP and REST Support
Dual protocol support for SOAP and REST through the AMI Web Services Framework.
BlackRock Aladdin Integration
Built-in integration with BlackRock Aladdin for institutional investment management.
Multi-Jurisdiction Regulatory Support
Support for FINMA, MiFID II, GDPR, and other regulatory frameworks.
Scroll within the panel for all 8 ·
Semantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Avaloq Banking Context
JSON-LDAvaloq Payments Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Avaloq API Rules
SPECTRALAvaloq API Rules
SPECTRALJSON Schema 21
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Account
JSON SCHEMAAccountList
JSON SCHEMACreateCustomerRequest
JSON SCHEMACustomer
JSON SCHEMACustomerList
JSON SCHEMAError
JSON SCHEMAPayment
JSON SCHEMAPaymentList
JSON SCHEMAPaymentRequest
JSON SCHEMATransaction
JSON SCHEMATransactionList
JSON SCHEMAAccountList
JSON SCHEMAAccount
JSON SCHEMACreateCustomerRequest
JSON SCHEMACustomerList
JSON SCHEMACustomer
JSON SCHEMATransactionList
JSON SCHEMATransaction
JSON SCHEMAPaymentList
JSON SCHEMAPaymentRequest
JSON SCHEMAPayment
JSON SCHEMAScroll within the panel for all 21 ·
JSON Structure 11
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Avaloq Structure
JSON STRUCTUREBanking Account List Structure
JSON STRUCTUREBanking Account Structure
JSON STRUCTUREBanking Create Customer Request Structure
JSON STRUCTUREBanking Customer List Structure
JSON STRUCTUREBanking Customer Structure
JSON STRUCTUREBanking Transaction List Structure
JSON STRUCTUREBanking Transaction Structure
JSON STRUCTUREPayments Payment List Structure
JSON STRUCTUREPayments Payment Request Structure
JSON STRUCTUREPayments Payment Structure
JSON STRUCTUREScroll within the panel for all 11 ·
Examples 12
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Avaloq Createpayment Example
EXAMPLEAvaloq Listaccounts Example
EXAMPLEBanking Account Example
EXAMPLEBanking Account List Example
EXAMPLEBanking Customer Example
EXAMPLEBanking Transaction Example
EXAMPLEPayments Payment Example
EXAMPLEScroll within the panel for all 12 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Wealth Management Platform Integration
Connect advisory tools and portfolio management applications with core banking data.
Digital Banking Channels
Build mobile and web banking experiences on top of Avaloq account and transaction APIs.
Fintech Partner Integration
Onboard fintech partners into the banking ecosystem through Community APIs.
Regulatory Reporting Automation
Automate MiFID II, FINMA, and other regulatory report generation and submission.
Payment Processing
Integrate domestic SEPA and international SWIFT payment processing.
KYC and Client Onboarding
Digitize client onboarding with KYC checks, document collection, and compliance screening.
Investment Portfolio Management
Build robo-advisory and portfolio management tools using investment APIs.
Trade Order Management
Execute and manage multi-asset trade orders through the Avaloq OMS.
Scroll within the panel for all 8 ·
Integrations 7
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
BlackRock Aladdin
Native integration with Aladdin by BlackRock for institutional investment management.
Bloomberg
Market data integration with Bloomberg for pricing and analytics.
SWIFT
SWIFT messaging network integration for international payment processing.
SEPA
SEPA credit transfer and direct debit support for European payments.
AWS
Avaloq Model Bank available on AWS for simplified cloud deployment and testing.
Salesforce
CRM integration with Salesforce for client relationship management.
FIX Protocol
FIX protocol support for electronic trading and order routing.
Scroll within the panel for all 7 ·
Resources
Every other property we hold for Avaloq — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/avaloq · machine-readable index on apis.io