UI Integration

HORISEN apps can show data from external APIs (Client API). All integration points must be pre-configured in the local integration storage and considered static meta/configuration data. Each time a front-end app makes a request to see the data, the Integration proxy makes a call to Client API to provide the data.

The Integration Proxy API (IPA) sits between HORISEN front-end applications and your Client API, and supports two UI component types: Grid components, which render your data as a paginated, sortable, and filterable table, and KPI components, which display a single aggregated value with a title, footer text, and an optional link. Your Client API only needs to expose one endpoint per component and return raw JSON in the structure IPA expects.

Authentication between IPA and the Client API uses a lifetime access token, sent either as a token query parameter or in a configurable request header — or the Client API can be left public if no authentication is required. The UI Integration API section documents a reference (IPA Mock API) implementation showing the exact request parameters and response shape for both component types.