The UAE Open Finance APIs
What the APIs cover, how the Hub mediates access, and where to find specifications.
UAE Open Finance uses a central API Hub. A TPP calls the Hub; the Hub calls the financial institution through its Ozone Connect interface and returns the response. The Hub manages consent, issues access tokens and provides the TPP-facing APIs. TPPs do not call the institution's backend directly.
Customer data sharing and payment initiation require customer consent. Services such as Confirmation of Payee, product information and ATM information use client credentials without an end-customer consent journey. FAPI supplies the financial API security profile; DCR registers a client and is a separate step from customer authentication.
The production directory snapshot observed on contains 6 published API family identifiers: Accounts, ATM, Confirmation of Payee, Insurance, Payments, Products. The Observatory shows published resources and versions. Publication does not establish successful integration, availability or live usage.