Ozone Connect v2.1

These specifications describe the APIs LFIs must implement for the API Hub to call. They show the request and response contracts an LFI's Ozone Connect backend must expose so the API Hub can proxy TPP requests — covering consent events, bank data sharing, service initiation, confirmation of payee, products & leads, and ATMs.

Audience: LFI engineering teams implementing the backend the API Hub calls into.

What you'll find here: the endpoints the API Hub calls on the LFI, and the responses the LFI must return.