Push API and Webhooks

This is a reminder about our Push API and Webhook capabilities, which provide a more efficient and real-time way to integrate with eMabler. These features have been available for some time, and many customers are already benefiting from the improved reliability and responsiveness they offer.
This is also a reminder that we have a new generic way of enabling and controlling the Push messages on our new Connect platform. For customers receiving push messages already a migration to the new way might be needed.

Push API and Webhooks

With the Push API, your systems can receive events as they happen—either through Webhooks, Kafka, AWS SNS or Azure Service Bus. Webhooks allow direct delivery to your backend using a simple URL and authorization header.

A wide set of message types is supported, such as ChargerState, ChargerBoot, Measurements, Charging Transactions, and more.

Documentation: Push API | Webhook | Message Types

Why you may want to adopt it

Using the Push API helps reduce the need for polling, lowers resource usage, supports more scalable architectures, and enables faster response times in your applications.

About the migration from the old method

The existing integration method remains fully supported. We are not deprecating it or announcing an end-of-life date at this time, as some use cases are still better served by the legacy approach.

However, over the long term, we would like all customers to transition to our new Push API implementation as it becomes the more capable and scalable model.

Getting started

You can enable Push API in Connect UI under:

More → Settings → Developers → Push API

If you need assistance or want to run a pilot, our team is here to help.

Kind regards,

The eMabler Team