Skip to main content
Flatpeak Connect enables your customer-facing app to link their energy account with energy provider — securely and consistently across markets. This guide explains how the Connect process works, the role of your app and backend, and how data flows through the system. When a customer uses Connect, Flatpeak automatically selects the fastest and most accurate method available. If one method fails — for example, if the user skips login — the system instantly falls back to the next best option. No dead ends. No manual steps unless absolutely necessary. Connect prioritises tariff connection methods in this order:
  1. DIRECT – Instant, authenticated connection
  2. LIBRARY – Selection for Flatpeak-maintained library
  3. MARKET – Automatically links market-based tariff by geo-location
  4. MANUAL – Customer input as a last resort
Explore DIRECT provider integrations coverage and MARKET coverage
The diagram below illustrates how sessions progress across these connection types:
  • Simplified flow diagram
  • Detailed flow diagram

​
Connect modules

The Flatpeak Connect is composed of two modules:

​
1. Main module

This module manages the core user interaction flow, including: The UI of this module is customisable. You can either:

​
2. Auth module

When a customer selects a provider with a direct integration to Flatpeak, they are redirected to the Auth module (shown in green in the diagram above). This module handles:
  • Redirecting to the energy provider’s authentication page
  • Secure login at the provider’s page
  • Return to the Main module
This module is not customisable, as it is usually hosted by the energy provider. It must be displayed in a WebView.

Example pages within Connect flow modules

​
URL parameters when creating Connect tokens

When calling the create-connect-token endpoint , you must specify the environment URLs used during the Connect flow.
ParameterDescription
connect_urlURL the customer is redirected to during the Handling Callback step of the Provider Login Redirect. Specify either the URL where your Connect web app is hosted or a deep link into your native app.
callback_urlURL where the customer is redirected after they complete or exit their Connect session.
Example configurations: Option 1. Using Connect web app hosted by Flatpeak 
  "connect_url": "https://anode.connect-web.flatpeak.com"
Option 2. Hosting the Connect web app yourself 
  "connect_url": "https://flatpeak-connect-web.yourapp.com",
  "callback_url": "yourapp://flatpeak/callback"
Option 3. Implementing Connect natively via the API 
  "connect_url": "yourapp://flatpeak/connect",
  "callback_url": "yourapp://flatpeak/callback"