Get an Organisation's Devices
Get the list of all devices for the specified organization ID. By default returns ALL devices with ALL fields.
Optional parameters:
- device_type: Filter by specific device type (hp_atw, hp_wtw, inv, ev, wb)
- device_steering: Only devices that are steered (
on) or not (off) - manufacturer: Only devices whose model carries this manufacturer
- status: Only devices in one of these health tones (good, warning, critical, not_steered;
repeatable). Graded off the connection/monitoring/steering trio, the same tones
…/devices/summarycounts — a device with a pending partner action is filtered under its trio’s tone while its owntonefield readsaction_required. - fields: Comma-separated list of specific fields (e.g., “id,owner.email,device_model.manufacturer”)
- page: Enable pagination by providing page number (1-based)
- page_size: Items per page when pagination is enabled (default: 100)
- sort: Order the whole fleet by
status(worst first),last_data(oldest first) orowner;orderflips it. Unsorted, devices come back device type by device type.sort=statusranks on thetonefield as rendered,action_requiredfirst — unlike thestatusfilter above, which grades the trio alone.
Field examples:
- fields=id,owner.email,device_model.manufacturer
- fields=id,connection_status,monitoring_status,battery_level
Restricted to staff and admins, plus Console Support agents reading across organisations.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Path Parameters
The organization ID of the user's organization
Query Parameters
Filter by device type (hp_atw, hp_wtw, inv, ev, wb)
Comma-separated list of specific fields to include
Page number (1-based) - enables pagination
x >= 1Number of devices per page when pagination is enabled
1 <= x <= 1000Search by device model, external id, owner name/email, or device id prefix
Filter by whether the device is steered (on) or not (off)
on, off Filter by the device model's manufacturer
Only devices whose health tone is one of these (repeatable)
good, warning, critical, not_steered Sort key; direction via order. Ties break on device id
status, last_data, owner Sort direction
asc, desc monitoring, steering, intraday, hems 128128If true, includes soft-deleted
Response
One object per device, each matching its device type's schema (anyOf of the four). When the fields query parameter is set, every object is a partial projection carrying only the requested (dot-nested) fields.
- ElectricVehicleOutput
- HeatPumpOutput
- InverterOutput
- WallboxOutput
ok, warning, error, unknown ok, warning, error, unknown ok, warning, error, unknown The device's console health tone, and the only verdict a client should render: action_required when a partner-resolvable action is pending, else the worst of connection and monitoring, with not_steered for a healthy device nobody optimizes. Do not re-derive it from connection_status/monitoring_status/steering_status — those three are cue-blind and would report a device asking for reauthentication as healthy. The status filter on GET /org/{org_id}/devices and the tone counts on …/devices/summary grade the three statuses only, so a device with a pending action reads action_required here while being counted and filtered under its status tone.
good, warning, critical, not_steered Whether the platform is doing what it should for this vehicle, component by component, and where the problem starts when it is not. Every cell is a reading of state the evaluators already recorded, so a cell nothing has observed reads not_measured rather than a guess.
Deprecated — use GET /org/{org_id}/notifications/status for per-device-type counts, or GET /org/{org_id}/notifications/actions?device_id=… for the specifics. True when at least one action is pending against this device and the partner must take that action before the device can resume normal operation.
AT, AT_HOURLY, BE, CH, EE, DE_LU, HR, HU, IE_SEM, IT_CNOR, IT_CSUD, IT_NORD, IT_PUN, IT_SARD, IT_SICI, IT_SUD, PT, RO, SE_1, SE_2, SE_3, SE_4, UK 20When set, the device is considered deleted.
255300Detected OEM-app charge cap (percent). NULL = unknown / no cap detected.
Event time of the last accepted canonical plug-state write, from any source (Smartcar telemetry, OCPP wire). The arbitration watermark: a claim whose evidence time is not newer than this is stale and does not write. NULL = no claim yet, so anything wins.
Timestamp the API signalled a boost cancel (owned by the API, not the workflow). Drives BoostState.STOPPING until the workflow ends the boost and clears boost_active_at. Cleared by the API on an un-cancel (re-tap).
Battery level at latest plug-in event
Last steering-block recovery probe attempt. NULL = never probed.
1616200URL to embeddable onboarding form
Base URL for authorizing with the Podero server
Pure boost lifecycle, shared by EVs and wallboxes (SC-154). Describes only the boost, not whether the device is charging — normal optimizer-driven charging is AVAILABLE (boostable), not ONGOING.
available, requested, unavailable, ongoing, stopping 