Dispatch webhook

The dispatch instruction Axle sends to your webhook during a grid event

This webhook is in development and not currently exposed by our API. The schema below may change before release.

During a grid event, Axle sends an HTTP POST to the webhook URL you provide. Each request carries a single dispatch instruction: one event, with a target power for every affected asset over a fixed window. You apply that target power to each asset between start_time and end_time.

You register your webhook URL when you set up your integration — get in touch to configure it.

Request body

{
  "event_id": "eab8c867-7c4d-4116-a587-02c9d1f13a16",
  "issued_timestamp": "2026-06-29T17:02:37.448917+00:00",
  "start_time": "2026-06-30T20:30:00+00:00",
  "end_time": "2026-06-30T21:30:00+00:00",
  "assets": [
    { "asset_id": "3c361164-5187-4b4b-8e8a-7b3f67c4d5a8", "power_kw": -6.915 },
    { "asset_id": "1a161164-5187-4b4b-8e8a-7b3f67c4d5a8", "power_kw": -4.915 }
  ]
}

Field	Type	Description
event_id	string (UUID)	Unique identifier for this dispatch event.
issued_timestamp	string (ISO 8601)	When Axle issued the instruction.
start_time	string (ISO 8601)	Start of the dispatch window.
end_time	string (ISO 8601)	End of the dispatch window.
assets	array	One entry per affected asset.
assets[].asset_id	string (UUID)	The Axle asset identifier returned at onboarding.
assets[].power_kw	number	Target power for the asset across the window, applied at the inverter. Positive = charge (import into the battery), negative = discharge (export).

power_kw is the target at the inverter. Axle normally dispatches at the inverter’s maximum power rating, and accounts for household load potentially limiting the power the battery delivers.

Responding

Return a 2xx status to acknowledge receipt.

Acknowledgement and delivery-feedback semantics are still being finalised. Get in touch for the latest detail on how your webhook should respond.