Required information, setup and verification for Fluvius API.
Collect authorised Fluvius metering data using the configured customer-reference flow. Eniris manages the API environment; the customer supplies consent and connection-point scope.
A reliable API connection combines the correct authorization method, an explicitly limited installation scope and a verified first retrieval.
Connection type: API and platform connection.
Provide your company and contact person, the intended Insights account, the source identifiers and explicit permission for the requested scope. Include a recent source example for verification.
| Information / setting | What is needed | Supplied or configured by |
|---|---|---|
| Authorisation reference (REFERENCE_NUMBER) | Reference identifying the customer consent/access flow. | Customer / installer |
| Exclusions (DISALLOW_LIST) | IDs that must not be processed; Eniris checks the identifier type used by this connector. | Customer / installer |
Check that the first collection completed, then open the intended Insights account and verify the relevant measurements or metadata. Compare source IDs, timestamps and units with the original source. Check the next scheduled execution as well. An active schedule or a healthy job alone does not prove that every requested measurement was received.
For ordinary onboarding meters, creation requests an immediate first run and keeps recurring collection active. Source publication times, upload intervals and provider limits still apply; immediate collection cannot manufacture missing source data.
Provide Eniris with the connection name, account/site scope, time of the attempt and the exact error. Check source availability and access permissions before retrying. Share a source screenshot or sample without passwords or tokens.
Costs are not established for this connector. Confirm provider access, export licences and any project charges with Eniris before activation.