Reverse-engineering the Enel X Way API

enel-x-way-api.md

Reverse-engineering the Enel X Way API

These API endpoints were extracted from decompiling the Enel X Way Android app.

Authentication

https://emobility.enelx.com/api/authentication/v2/oauth/refreshToken

Status

https://emobility.enelx.com/api/emobility/v2/status

Charging

Home

https://emobility.enelx.com/api/emobility/v2/charging/process/start
https://emobility.enelx.com/api/emobility/v2/charging/process/{sessionId}/stop
https://emobility.enelx.com/api/emobility/v2/charging/process/{sessionId}/status

Public

https://emobility.enelx.com/api/emobility/v2/charging/station/{stationId}
https://emobility.enelx.com/api/emobility/v2/charging/station/carplay

Reservation

https://emobility.enelx.com/api/emobility/v2/reservation
https://emobility.enelx.com/api/emobility/v2/reservation/{reservationId}

User

https://emobility.enelx.com/api/user/v2/profile/

Utility

https://emobility.enelx.com/api/utils/v1/functionality/
https://emobility.enelx.com/api/utils/v1/labels
https://emobility.enelx.com/api/utils/v1/callback/payment-ok
https://emobility-qa.enelx.com/api/utils/v1/callback/payment-ok

following along, I started doing the same

Not sure if the app route is the future, given their recent statement. I have higher hopes in the Juice Rescue initiative. I couldn't get it to work on my purchased-in-Spain European Juicebox, though…