Book a demo

Webhooks

Session updates, pushed as they happen.

ChargeIT sends session events to your backend, so your systems never have to poll the API to know what is happening at the charger.

Request API access API overview
A session changesAt the charger, over OCPP
ChargeITSends the session event
Your endpointReceives the update

Pull and push

Where webhooks fit.

The API answers when your backend asks. Webhooks tell your backend without being asked. Most integrations use both.

  • Pull with API keysLocations, charger status, sessions, tariffs and invoices, whenever your backend asks.
  • Push with webhooksSession updates sent to your endpoint as they happen.
  • Or push, sent for youSession updates delivered as push notifications to your app, sent by ChargeIT.

API

Your backend asks.

Webhooks

ChargeIT tells you.

What they are for

Keep your systems in step.

Your own app

Show drivers a session’s progress without polling.

Your backend

Know when sessions start, change and end.

Your reporting

Session data in your own systems as it happens.

Getting started

From request to first event.

  1. Tell us what you are building

    Request API access and describe your integration.

  2. We enable your organisation

    The developers panel and the scopes you need are switched on for you.

  3. Connect your backend

    Event formats and setup details come with your API access.

Questions

Webhooks, answered.

Do webhooks replace the API?

No. Use the API to read data and act; use webhooks to be told when a session changes.

Which events are sent?

Session updates, as sessions start, progress and end.

Where do I find the event formats?

They come with your API access, together with the setup for your organisation.

Stop polling.

Tell us what your systems need to know, and we’ll set up your access.

Request API access