Example 2 · API Framework Orchestration

Digital Channel — Audax as the front-end API layer

The bank's own Mobile App and Internet Banking both call the same Audax-native digital API. One contract, one canonical engine, multiple channels — only the X-Channel-Id header tells them apart.

Only step 1 varies (the X-Channel-Id header). Steps 2–5 are identical for both channels — the digital API is one contract, not two.

  1. Mobile App client requests the customer's balance via the Audax-native digital API. Both Mobile App and Internet Banking hit exactly the same endpoint with the same contract — only the X-Channel-Id header differs.

    GET /digital/v1/accounts/70000600503/balance HTTP/1.1
Host: api.bank.example
Authorization: Bearer <session-token>
X-Channel-Id: MOBILE_APP
X-Device-Id: 5c1a9e7d-2f44-4b1e-9a0a-3a8c0b9d1e22
  3. identifier lookup

The pattern: the same canonical service (step 4) serves regulated TPPs (Example 1) and the bank's own digital channels (Example 2) identically. Only the edges — steps 1, 2, and 5 — differ by consumer. Examples 3–5 continue this pattern for new endpoints, new middleware, and new connectors.