Why this guide – and why Renault is different

Renault requires a manufacturer‑side subscription step before vehicle data becomes available. For most brands, the onboarding flow is a single session: the user signs in, grants consent, and your app immediately starts receiving charging data. Renault is different: once the user selects their vehicle, we must subscribe the vehicle to a service on the Renault backends. Renault will then update the configuration in the EV. This asynchronous process can last anywhere from a few minutes to several days (mean ~1.5 h).

This delay creates two UX gaps you need to bridge:

Inform the user that activation is in progress so they don’t think something is broken.
Bring them back at the moment activation completes so they can finish pairing.

Jedlix exposes the technical hooks for this (two new connectionStatusvalues plus a webhook). To fully support Renault, it is recommended to add a small amount of UI and notification logic so everything feels seamless.

This guide will highlight the changes needed to:

Display a Waiting for activation screen while Renault completes subscription.
Notify the driver when the vehicle is ready (connectionState="readyToContinue").
Resume your existing onboarding flow: start a new connect session for the existing user and vehicle id.

Changes at a glance

Area	New for Renault	developer impact
Waiting for activation screen	Vehicle may take up to 1  week (mean ~1.5 h) to be subscribed. Two new connectionStatus values:• waiting• readyToContinue	Add UI for waiting + resume states.
Notification	Webhook `vehicleConnectionReadyToContinue` to trigger in‑app push/email.	Implement webhook
Resume onboarding	Starting a new onboarding session for `readyToContinue`resumes the flow, rather than starting from the beginning	Start a new onboarding session through `startSelectedVehicleConnectSession`in the SDK

Flow diagram

User onboarding journey

User selects a (supported) Renault in the vehicle onboarding flow
User goes through the onboarding steps, and starts the subscription process. At this point they can exit the onboarding flow and return to the app
Subscription in progress – app shows Waiting screen (connectionState = waiting).
Jedlix receives confirmation from Renault → connectionState flips to readyToContinue.
Your backend receives a webhook (or you poll the endpoint)
You notify the user (push notification, email, ..) → user resumes the onboarding flow
Onboarding complete

Links to relevant API docs

Fetching the vehicle onboarding status (connectionState): https://developer.jedlix.com/reference/getvehiclebyid
Starting a new onboarding session from an existing user + vehicle (startSelectedVehicleConnectSession): https://github.com/jedlix/jedlix-sdk-android/blob/main/sdk/src/main/java/com/jedlix/sdk/connectSession/ConnectSessionManager.kt
Subscribing to webhooks (vehicleConnectionReadyToContinue): https://developer.jedlix.com/reference/createsubscriptionasync