Skip to content
Sandbox

Vehicles · home devices · electricity

One connection.
The customer controls access.

Connect vehicles, home devices and electricity through one integration, with clear permissions and an auditable history.

Discuss a pilotExplore sandbox →

In development. The sandbox uses simulated providers; live availability depends on each provider's API and commercial access.

ConnectionsVehicles, home, electricityHow it worksFour steps, customer decidesFor insurers
Sandbox simulationProvider names are examples in the sandbox. Eivro has no partnership with them, and they are not available as live connections.

Three kinds of connection, one flow

What can be connected depends on each provider's API and on commercial access. We list a provider as live only when the connection works.

Vehicles

Vehicle status the manufacturer's API offers, such as location at a chosen time or warning lights.

Sandbox examples: Tesla, BMW

Alarms and home devices

Alarm state, leak, smoke and door sensors from alarm and smart-home systems.

Sandbox examples: Homely, Homey

Electricity

Consumption and meter data, for example to spot a heating failure in an empty house.

Sandbox examples: Tibber, Elhub

How it works

  1. The business integrates once

    You have one API and one connection flow for vehicles, home devices and electricity.

  2. The customer connects an account

    The customer's account at their provider is linked, after they sign in there.

  3. Eivro finds what is available

    A list of the devices and data the provider's API offers for that account.

  4. The customer chooses

    Access to exactly the devices and information the customer chose, for as long as they choose.

For insurers

Three uses we want to test in a pilot. Each works only where the provider's API offers the data and the customer has chosen to share it.

Spot protection that has gone quiet

See when a shared alarm or leak sensor stops reporting, so the customer can be reminded before something happens.

Tell customers about possible damage

A leak alert, or electricity use that drops in a cold house, can trigger a message to the customer.

Share what matters for one claim

After an incident, the customer can share the relevant history for that claim only, for a limited time.

We make no promises about fewer claims, lower premiums or compatibility with every device. A pilot is how we find out what works.

One Eivro connection inside the insurer’s app

After an approved integration, an insurer can show Eivro’s service catalogue in its app or website. In the planned flow, customers continue to Eivro to choose and approve what may be shared. The sandbox shows only the catalogue and a simulated consent preview.

Services discoverable in the Eivro sandbox

  • TeslaVehiclessimulated in sandbox
  • BMWVehiclessimulated in sandbox
  • HomelyAlarms and home devicessimulated in sandbox
  • HomeyAlarms and home devicessimulated in sandbox
  • TibberElectricitysimulated in sandbox
  • ElhubElectricitysimulated in sandbox

Preview the customer’s choice

Choose sandbox services to see an example of the request the customer would review at Eivro.

Where does the customer come from?
Services requested by Example Insurance

Select only the services the customer should review. No provider account or information is accessed.

Example purpose: Preview how customer approval could be presented

Sandbox example: services, purpose and information field are not live or checked against provider rights. No account, personal data, API call or persistent access is used.

  1. Discover the catalogue

    One integration discovers Eivro’s services and clearly distinguishes sandbox from live availability. The sandbox does not know which customer accounts are connected.

  2. The customer chooses and approves

    In the planned live flow, customers continue to Eivro, choose accounts, and approve specific services, information, purpose and duration.

  3. Share only what was selected

    An approved live integration can receive access only after valid customer authorization. Declining or selecting nothing grants no access.

  4. The customer can revoke

    Once customer permissions are supported in production, they should be revocable through Eivro. Sharing information never grants control of devices.

In development. The sandbox catalogue shows simulated services; no insurer integration or provider connection is available in production yet.

The customer controls sharing. An insurer integration by itself does not authorize decisions about coverage, pricing or claims.

The customer stays in control

Four rules the flow is built on. The sandbox shows them with simulated providers.

  • Information and commands are separateSharing what a device reports never allows controlling it. Commands need their own approval.
  • Explicit choice of devicesOnly the devices the customer ticks are connected. New devices are not added on their own.
  • Withdraw at any timeOne permission or the whole connection, from the customer's own page.
  • A visible historyEvery connection, change and withdrawal is logged, and the customer can see it.
Connection historyHomely · sandbox
23.10. 09:14
Connected · 3 of 4 devices selected
23.10. 09:15
Shared with insurer: alarm state, leak alerts
02.11. 18:40
Claim 4471: leak history shared until 02.12.
14.11. 21:02
Withdrawn by customer: door events
ExampleThe history as the customer sees it. Dates and events are examples.

For developers

Create an authorization session, send the customer to the shared flow at Eivro, and get back only the devices and information the customer approved. The service catalogue is public and holds no customer data; only a registered, authenticated insurer client can create a session. The sandbox simulates the flow; it creates no live provider access.

Explore the sandbox

ChatGPT and Claude: not available yet. ChatGPT guide · Claude guide

GET /.well-known/eivro/services

POST /v1/authorization-sessions
Idempotency-Key: <opaque key>
{
  "services": [
    {
      "serviceId": "home.example-alarm",
      "fieldIds": ["alarm.state", "sensor.alerts"]
    }
  ],
  "purposeId": "registered-purpose-id",
  "channel": "insurer-app",
  "requestedDurationSeconds": 604800,
  "redirectId": "registered-redirect-id",
  "codeChallenge": "<43-character S256 challenge>",
  "state": "<opaque client correlation value>"
}

# 201 Created
{
  "sessionId": "opaque-session-reference",
  "status": "pending_customer_action",
  "expiresAt": "<customer-action deadline>",
  "authorizationUrl": "<first-party Eivro authorization URL>"
}
SketchIllustrative request. Eivro derives the recipient from the registered client, the field and purpose IDs are examples, and each request carries an Idempotency-Key. Paths and fields can change before the API is published.

Help shape connected protection.

We are looking for insurers and device or energy providers for a focused pilot: one product line, a limited group of customers who opt in, and what to measure agreed before we start.

Sandbox
Simulated providers only
Pilot
By agreement, with a limited scope
Live connections
Not available yet

Prefer to look first? Explore the sandbox

We use your details only to reply about the pilot. Privacy