We build custom integration for high volume partners only. And we require the following:
A session to access the charge point should be either:
1) A server token which gives access to the charge point(s)
2) User token
User logins via credentials, Monta stores token and refresh token. Which should give us access to the charge point(s) for min 90 days. Even if the user logins another place, the refresh token needs to continue working
|
API |
Request |
Response |
Required |
|
Get status |
SERIAL |
STATUS |
✅ |
|
Get transactions |
SERIAL |
ID, START, STOP, KWH |
✅ |
|
Get transaction |
SERIAL, TRANSACTION_ID |
ID, START, STOP, KWH |
✅ |
|
Get global meter value |
SERIAL |
KWH |
✅ |
|
Start |
SERIAL,TAG_ID |
TRANSACTION_ID |
✅ |
|
Stop |
SERIAL |
TRANSACTION_ID |
✅ |
|
Reboot |
SERIAL |
|
❌ |
|
Unlock |
SERIAL |
|
❌ |
|
Set events |
SERIAL |
|
❌ |
We prefer to have a full event driven integration, not relying on polling. But the web hooks urls should be setup via an API or be a global setup you handle
Here is the list of events:
|
Events |
Fields |
Required |
|
Status update |
SERIAL, STATUS |
❌ |
|
Transaction started |
SERIAL, TRANSACTION_ID |
❌ |
|
Transaction stopped |
SERIAL, TRANSACTION_ID |
❌ |
|
Meter updated |
SERIAL, KWH |
❌ |