Consent UI enable your users to securely provide consent to their EV data to you. You can use the following information to build a customized url and redirect your customer to it
This is the entry point to consent UI from your app.
App-id for your app
User-id of user in your database
inverter. Defaults to
Brand of the device, if known beforehand. This will skip the brand selection screen
This param is deprecated and will be dropped soon. Please use the
callbackEnv param instead.
If multiple callback urls are registered with Telematica, this param will dictate where the webhook event for
user.devices-connected will be sent.
If your app has only 1 endpoint registered, you can ignore this param.
If your app has multiple endpoints registered, leaving this empty will send events to all endpoints.
If your app has multiple endpoints registered, and the value of this param is valid, the event will be sent to endpoint corresponding to your chosen environment.
Note: Callback URLs must be registered with Telematica beforehand. For more details contact us
url where we will redirect the end user using webview browser redirect. This will typically be an app URL (
yourApp://somepage). The redirect URL schema must be registered with Telematica beforehand.
IN. This will show only the supported device models on brand-selection page.
SiteId of the device in your database. This will be forwarded to you in the callback. A
site is an abstraction at Telematica level to represent group of devices (EV, charger, HVAC and solar inverter) in single location that should be controlled together.
Site name of the device in your database. This will be forwarded to you in the callback.
All query params with key starting with prefix of
metadata_ are pass through params. These will be passed as-is to the callback you receive on device connection success.