Fuse is a unified data aggregation API that provides fully structured, calculated, and cross-referenced person data through a single integration point. Built for banks, lenders, and regulated environments, Fuse delivers actionable insights that power better decision-making across your organization.

Instead of connecting to 10+ separate APIs to gather customer information, Fuse consolidates all your data needs into one streamlined integration—significantly reducing development time and ongoing maintenance overhead.

Unified Customer Profile — Fuse incorporates advanced logic for inferring, calculating, and matching data from diverse sources to construct a comprehensive customer profile. Data is automatically cross-referenced and validated to ensure accuracy and completeness.

Single Integration Point — Access personal data from multiple registries through one API. This reduces the complexity of managing multiple vendor relationships, credentials, and integration contracts.

Cost Efficiency — Repeated and duplicate customer applications often lead to higher API expenses with minimal benefit. Fuse enables you to efficiently search and reuse data from previous inquiries at no additional cost, optimizing your data spend.

Fuse is built around two primary resources: Inquiries and Persons.

Inquiry — An Inquiry represents a data collection process for a specific person. When you need to gather information about a customer, you create an Inquiry. The Inquiry tracks what data has been requested, what consent has been obtained, and serves as the container for all fetched person data.

Person — A Person represents the individual whose data is being collected. Person data is always accessed within the context of an Inquiry, ensuring proper consent and audit trails.

Some data sources require explicit consent from the end user before their data can be accessed. When fetching consent-protected information, the following flow applies:

1. Create an Inquiry — Initialize an Inquiry for the person using their national identity number.

2. Redirect for Consent — If the requested data requires consent, direct the end user to complete the consent process. The Inquiry status will indicate when consent is pending.

3. User Completes Consent — The end user authenticates and grants permission for their data to be accessed.

4. Fetch Person Data — Once the Inquiry is completed, you can fetch the person data. Fuse aggregates information from all connected registries and returns a unified response.

Previously fetched data remains available within an Inquiry, allowing you to query additional information without re-fetching from source systems. You can also search for existing Inquiries to reuse data from previous requests, reducing costs and improving response times.

In order to consume this API, you must register Neobits as a provider in Altinn. Access must be provided for the Norwegian Population Registry and Samtykkebasert Lånesøknad.

Once your Altinn access is configured, you can authenticate using your API credentials and begin making requests to the Fuse endpoints documented below.