← Back to catalog

Other

Enode

auto-generated
swirls add enode …
actionPOSTv1.0.0

Control Charging

Instruct the charger to start or stop charging

Source
actionDELETEv1.0.0

Deauthorize User

Deletes the User's stored vendor authorizations and credentials, invalidates any associated sessions, authorization codes, and access/refresh tokens. All other User data is retained, and if the User is sent through the Link User flow in the future their account will be just as they left it. No webhook events will be generated for a deauthorized user.

Source
actionDELETEv1.0.0

Disconnect Vendor

Disconnect a single Vendor from the User's account. All stored data about their Vendor account will be deleted, and any vehicles that were provided by that Vendor will disappear from the system.

Source
actionGETv1.0.0

Get My User

Returns metadata about the authenticated User, including a list of vendors for which the user has provided credentials.

Source
actionGETv1.0.0

Get User Charging Statistics

Returns a normalized timeseries of statistics about power consumption and price for the User.

Source
actionPOSTv1.0.0

Link User

Creates an Enode Link session attached to the provided User ID. If this User does not exist, it will be created. The returned `linkState` gives the user short-lived access to Enode Link.

Source
actionPOSTv1.0.0

Start / Stop Charging

Instruct the vehicle to start or stop charging. #### Precedence over smart charging If the vehicle is at a charging location where smart charging is activated: - a request to `start` charging will override smart charging and charging will stay on until fully charged. - a request to `stop` charging will override smart charging and charging will be kept off for the duration of the current smart charging cycle. The smart charging settings are not altered by these actions.

Source
actionPOSTv1.0.0

Start Watching Vehicle

Temporarily triggers high-rate updates of the vehicle's properties, and this state expires automatically. This gives you a way to tell us that user may be interacting with your application and are expecting as-fast-as-possible updates on the status of their vehicle in your UI. Any data changes resulting from this high-rate updating are reflected everywhere, whether you pull data from the `Vehicles` endpoint, or recieve it via the [Firehose Webhook](#tag/Webhooks) The specifics of the expiration times, watch behaviors, and change thresholds are tuned by us to make sure that they work as expected, without causing undue interruption to the vehicle. For many vendors, it is not appropriate to let the high-rate monitoring last indefinitely, as it will keep systems within the car awake that should be allowed to fall into low-power/standby modes.

Source
actionDELETEv1.0.0

Unlink User

Deletes a User and all of their data permanently, and invalidates any associated sessions, authorization codes, and access/refresh tokens

Source
actionPUTv1.0.0

Update Charging Location

Updates a charging location with new configuration

Source
Beyond the catalog

Any provider, on request.

01

Request it

Tell us which provider you need, and we will ship it in the registry.

02

Generate it

Point swirls add at an OpenAPI or GraphQL spec. Typed actions for any API you hold credentials for, today.

Request a providerRead the actions docs
acme · integrations
terminal
~/acme $swirls add linear
✓ 12 typed actions · scopes and schemas included
 
~/acme $swirls add https://api.acme.dev/openapi.json
◆ Fetched spec · 38 operations
✓ 6 typed actions · generated from spec