Skip to main content

Push API

Connect now allows you to setup Push API in completely self-service manner! If you need to have access to real time data from your chargers, consider taking Push API into use. You can enable Push API in Connect from More > Settings > Developers > Push API

Note

Push API will incur an extra fee on some subscription packages.

Supported methods​

Currently we support following methods for Push API:

  • Webhook
  • Kafka
  • Azure Service Bus

Why Push API?​

Wondering why take Push API into use? Here are a couple of good reasons:

  • Lower latency and real-time delivery

    • Push APIs deliver data as soon as an event occurs, enabling real-time or near-real-time workflows. In contrast, REST APIs typically require polling at intervals, which introduces delay and may result in stale data.

  • Reduced resource consumption

    • With Push API, clients don't need to continuously poll for changes. This significantly lowers unnecessary network traffic and CPU usage, especially when changes are infrequent.

  • Improved scalability

    • Systems built on event-driven architectures (e.g. Kafka or Azure Service Bus) can scale more effectively under high load. Events are queued, distributed, and processed asynchronously without overwhelming services.

  • Loosely coupled architecture

    • Push APIs support decoupled system design. Producers emit events without needing to know which consumers exist or how they process the data, enabling more modular and flexible integration patterns.

  • Reliable delivery and retry handling

    • Message brokers like Kafka or Azure Service Bus offer built-in mechanisms for guaranteed delivery, retries, dead-letter queues, and message persistence — features not natively available with traditional REST endpoints.

  • Better user experience

    • In client-facing applications (e.g., end user UIs or mobile apps), receiving updates via Push API improves responsiveness and makes for a more seamless experience compared to periodic polling.