Skip to main content

Exploring our Unified Domain Model documentation

· 3 min read
Akkuro Lending Development Team

When you’re building or integrating with Akkuro Lending, one of the biggest challenges is ensuring that everyone and every systems speak the same language. Data flows across services, APIs, and databases can become complex, and that's why Akuro Lending uses a Unified Domain Model (UDM) as a common language that can bring clarity and consistency to the entire Lending ecosystem.

Therefore, we are pleased to introduce our Domain Model documentation. This documentation gives you the business context behind our data, helping you better understand Akkuro Lending and use our API schema with confidence.

What is the Unified Domain Model?​

The Unified Domain Model is a standardized, business-driven representation of real-world concepts and objects related to lending. Akkuro Lending organizes objects by functional domain, such as counterparty and collateral. The UDM forms the foundation that keeps the entire Lending ecosystem working together smoothly and serves as a guideline for data storage.

This improves communication between components, increases data consistency, reduces mapping errors and ambiguity, and simplifies integration across different systems and teams.

To learn more, check out the Domain model overview.

What our Domain Model documentation offers​

If you’re exploring how your system can integrate with us, or you simply want to understand how our lending domain is structured, this documentation is your go-to resource.

To make these concepts easy to grasp, the docs include simplified diagrams inspired by UML class diagrams. These visuals highlight the essential classes, attributes, and relationships you need to understand how data is organized. These visuals help you quickly understand how lending data is structured, plan smoother integrations, and see how different parts of the platform fit together.

Moreover, this documentation shows not just the data structure, but also explains the business meaning behind the data. It gives you the big picture of our domain model, helping you understand what the data means.

Currently, our documentation covers the following functional domains:

How to use our documentation​

The Domain Model documentation and the API Schema are designed to work hand in hand:

  • The Domain Model documentation explains the domain concepts
  • The API schema shows you how to interact with the APIs

By starting with the Domain Model documentation, you’ll understand the core concepts, how objects depend on each other, and which APIs to use at each stage of a business flow. This reduces guesswork, shortens integration time, and leads to cleaner, more reliable implementations.