How many API endpoints does Aura provide?

Aura provides over 2,000 documented API endpoints, all built with clear, adaptable structures for diverse business needs. An API Sandbox is available so you can explore the endpoints hands-on before building against them.

How does Aura structure core data like clients, products, and accounts?

Every Aura Business API centers around a Client, created from either a Person or an Organisation, which becomes a Personal or Corporate Client once a business relationship begins. Products define pricing, lifecycle, and accounting rules, under which individual Accounts are created and processed through to closure.

What should I know about API request structure before integrating?

API request tags are ordered alphabetically rather than grouped logically, so it's worth reviewing the full schema rather than skimming. Some tags are conditionally mandatory, marked Required = false but flagged with a Conditional note in the description, meaning a field can become required depending on other values you send.

What is Aura DataHub?

Aura DataHub aggregates data from multiple systems into a single, unified repository, with real-time ingestion and an automated ETL process to extract, transform, and consolidate incoming data. It also includes built-in data lineage tracking and automated quality checks throughout the data lifecycle.

How is data secured across the platform?

Aura implements end-to-end encryption for data both in transit and at rest, paired with fine-grained, granular access control policies, so security is enforced at the individual data-access level, not just at the perimeter.

Aura for Developers

Built for builders

Harness the power of Aura core APIs, DataHub and Aura Crew agentic platform

6,500+ API endpoints

100% unified data

100% AI ready

100% built for builders

API Sandbox

We provide developers with clear and adaptable APIs that cater to diverse business needs.

Explore Aura API

Get yourself a head-start through this general introduction before getting into the details of Aura APIs.

Client Creation & Data Architecture

All Aura Business APIs center around a Client, created from either a natural person (Person) or an artificial entity (Organisation). When business interactions begin with a financial institution, these records become Personal or Corporate Clients. Products (such as Term Deposits, Mortgages, or Cards) define the pricing, lifecycle, and accounting rules, under which specific customer Accounts are created and processed until closure.

Configurable Parameters & ID Hierarchy

Many API parameters (like Address Type) are maintainable values configured by the Product Owner according to business requirements. Most configurable parameters support both a Business ID and a UUID; if both are sent in an API request, the UUID takes precedence. Pre-defined lists of valid values must be matched exactly as stated in the parameter descriptions.

API Structure & Conditional Fields

API request tags are ordered alphabetically rather than logically grouped, making it important to review the entire structure. Conditionally mandatory tags are marked as Required = false in the schema, but feature a {Conditional} flag in the first line of their description (e.g., providing an AddressType makes Address1 mandatory).

Implementation Essentials

To integrate successfully, secure the necessary environment credentials and header parameters (such as Branch, Currency, and Service Delivery Channel). Work closely with the Product Owner to verify valid maintainable parameters, and carefully read the inline tag descriptions to ensure all conditional requirements are met.