# Podero Documentation - [Partner API Overview](https://developers.podero.com/partner-api/overview/introduction.md): Comprehensive guide to the Podero Partner API for server-to-server integration - [Authentication](https://developers.podero.com/partner-api/overview/authentication.md): OAuth2 Client Credentials flow for server-to-server authentication - [Prerequisites](https://developers.podero.com/partner-api/getting-started/prerequisites.md): What you need before getting started with the Podero Partner API - [Register Application](https://developers.podero.com/partner-api/getting-started/register-application.md): Create an OAuth2 application to access the Partner API - [Get Access Token](https://developers.podero.com/partner-api/getting-started/get-access-token.md): Generate an OAuth2 access token for API authentication - [Create User](https://developers.podero.com/partner-api/getting-started/create-user.md): Create your first end-user account via the Partner API - [Connect Heat Pump](https://developers.podero.com/partner-api/getting-started/connect-heat-pump.md): Add a heat pump device using the Podero Connect UI - [Retrieve Device Data](https://developers.podero.com/partner-api/getting-started/retrieve-device-data.md): Read operational data and status from your connected device - [Device Onboarding](https://developers.podero.com/partner-api/user-journeys/end-user/device-onboarding.md): Complete workflow for adding and connecting end-user devices - [Setting Preferences](https://developers.podero.com/partner-api/user-journeys/end-user/setting-preferences.md): Configure device-specific settings and optimization preferences - [Dashboard Integration](https://developers.podero.com/partner-api/user-journeys/end-user/dashboard-integration.md): Display device status, consumption data, and optimization insights to end-users - [Notifications](https://developers.podero.com/partner-api/user-journeys/end-user/notifications.md): Surface pending device issues to end-users and guide them to resolution - [User Management](https://developers.podero.com/partner-api/user-journeys/back-office/user-management.md): Manage end-users, their devices, and data from the partner back-office - [Team Administration](https://developers.podero.com/partner-api/user-journeys/back-office/team-administration.md): Manage staff and admin users within your organization - [Notifications Overview](https://developers.podero.com/partner-api/notifications/overview.md): Receive real-time notifications from Podero via signed webhooks - [Integration Guide](https://developers.podero.com/partner-api/notifications/integration.md): Build, secure, and verify an endpoint that receives Podero notifications - [Resolving actions](https://developers.podero.com/partner-api/notifications/resolving-actions.md): Turn a collected action into a resolved one — the resolve, redirect, and report flow - [Reference](https://developers.podero.com/partner-api/notifications/reference.md): Webhook Management API, Notification Content API, message envelope, headers, topics, signatures, and delivery semantics - [Device Explainers](https://developers.podero.com/partner-api/explainers/integration.md): Show customers why Podero is steering their heat pump or solar inverter - [Explainer API Reference](https://developers.podero.com/partner-api/explainers/reference.md): Endpoints, parameters, and schemas for heat-pump and solar-inverter explainers - [User Parameters](https://developers.podero.com/partner-api/reference/users.md): Complete reference for user account attributes and properties - [Heat Pump Attributes](https://developers.podero.com/partner-api/reference/heat-pumps/attributes.md): Writable parameters for configuring heat pump devices - [Heat Pump State](https://developers.podero.com/partner-api/reference/heat-pumps/state.md): Read-only state data and current readings from heat pump devices - [Electric Vehicle Attributes](https://developers.podero.com/partner-api/reference/electric-vehicles/attributes.md): Writable parameters for configuring electric vehicle charging - [Electric Vehicle State](https://developers.podero.com/partner-api/reference/electric-vehicles/state.md): Read-only state data and current readings from electric vehicles - [Solar Inverter Attributes](https://developers.podero.com/partner-api/reference/inverters/attributes.md): Writable parameters for configuring solar inverters and battery systems - [Solar Inverter State](https://developers.podero.com/partner-api/reference/inverters/state.md): Read-only state data and current readings from solar inverters - [Get all registered device models](https://developers.podero.com/api-reference/device-models/get-all-registered-device-models.md): Get all registered device models that satisfy an optional OData query. Such a query can be used for advanced filtering and sorting and follows the OData v4.0 standard. OData query examples: - `q="manufacturer eq 'Firma X')"` - `q="device_type/any(x: x/short_name ne 'ev')"` - [List filtered hourly prices](https://developers.podero.com/api-reference/prices/list-filtered-hourly-prices.md): Retrieve hourly price list for a specific market and price zone. It can be filtered to be in a time window. - [Token](https://developers.podero.com/api-reference/authentication/token.md) - [Federated Providers](https://developers.podero.com/api-reference/authentication/federated-providers.md): Enabled utility SSO providers — public PKCE config the app's sign-in screen renders from. - [Federated Token](https://developers.podero.com/api-reference/authentication/federated-token.md) - [Me](https://developers.podero.com/api-reference/authentication/me.md) - [Signup Request](https://developers.podero.com/api-reference/authentication/signup-request.md) - [Signup Confirm](https://developers.podero.com/api-reference/authentication/signup-confirm.md) - [Current Branding](https://developers.podero.com/api-reference/organization-branding/current-branding.md): The branding of the organization the request names: identity, copy, languages, theme, text overrides and absolute asset URLs. - [Current App Settings](https://developers.podero.com/api-reference/organization-branding/current-app-settings.md): The app settings of the organization the request names: which tabs and controls the app shows, its stored switches, and the device brands and categories its members may connect. - [Retrieve Organization](https://developers.podero.com/api-reference/organization/retrieve-organization.md): Org detail for the console. Restricted to support/admin, plus Console Support reading across orgs — the org's own end users have no need for it and it carries the standing join link, a self-signup secret. - [Update Organization](https://developers.podero.com/api-reference/organization/update-organization.md): Update the organization data for the specified organization ID, with a JSON payload. - [Create Organization Join Link](https://developers.podero.com/api-reference/organization/create-organization-join-link.md): Mint the org's standing self-signup link — the console face of the admin's generate action. - [Revoke Organization Join Link](https://developers.podero.com/api-reference/organization/revoke-organization-join-link.md): Kill the standing link so its holders can no longer sign themselves up. Idempotent: with no link standing the caller's intent is already satisfied, and 404 would only invite retries. - [Get Org Cues Issue Flow](https://developers.podero.com/api-reference/organization/get-org-cues-issue-flow.md): Daily raised/resolved cues with the end-of-day open backlog, over ``[start, end]`` inclusive. - [Get Org Growth](https://developers.podero.com/api-reference/organization/get-org-growth.md): Cumulative assigned members, all members, and operational devices connected per day, over ``[start, end]`` inclusive. Each point is ``{date, users, all_users, devices}`` — the running totals standing at that UTC day's end. - [List Organization Invitations](https://developers.podero.com/api-reference/organization/list-organization-invitations.md): List the organization's invitations for the console tables — the newest send per email across both invite surfaces (end-user and console support/admin), each with its derived lifecycle status (pending / accepted / expired / revoked / invalidated), newest first. - [Invite User](https://developers.podero.com/api-reference/organization/invite-user.md): Invite a user to the organization by email, granting a member role on acceptance. - [Resend Invitation](https://developers.podero.com/api-reference/organization/resend-invitation.md): Re-send an invitation: a fresh email and a fresh validity window for the same email, role and Podero profile — so re-sending a profile-carrying invite needs the same developer standing. Create-again under the hood, so an already-accepted (active member) invite is refused with 400, the same as inviti… - [Revoke Organization Invitation](https://developers.podero.com/api-reference/organization/revoke-organization-invitation.md): Revoke an invitation so its link no longer grants — enforced at sign-up confirmation. The actor must outrank the invited role. Idempotent on an already-revoked invite; 409 on an accepted one, since revoking would record a false state without removing the member. - [List Organizations](https://developers.podero.com/api-reference/organization/list-organizations.md): List every organization (id + name) for the cross-org switcher, name-ordered. - [Get Branding](https://developers.podero.com/api-reference/organization-configuration/get-branding.md): The organization's branding: product name, copy, languages, theme and assets, and read-only the text overrides that Podero writes. - [Post Branding](https://developers.podero.com/api-reference/organization-configuration/post-branding.md): Save the branding: one ``payload`` form field with the JSON document, and the asset files. - [Get Settings](https://developers.podero.com/api-reference/organization-configuration/get-settings.md): The organization's settings: app switches, policy, defaults, the device catalog, and read-only the organization's identity and what Podero grants it. - [Post Settings](https://developers.podero.com/api-reference/organization-configuration/post-settings.md): Save the settings. The organization's fields cannot be written here: a document that carries one is a 422. - [Get Admin](https://developers.podero.com/api-reference/organization-configuration/get-admin.md): What Podero writes for the organization: its identity, trading, optimization basis, audit log and the text overrides of its apps, and read-only the managed values of its settings. - [Post Admin](https://developers.podero.com/api-reference/organization-configuration/post-admin.md): Save the admin document. The managed values cannot be written here. - [Organization Fleet](https://developers.podero.com/api-reference/platform/organization-fleet.md) - [Organization Service Health](https://developers.podero.com/api-reference/platform/organization-service-health.md): Current service health of one organization's fleet, counted from the stored chains. - [Platform Fleet](https://developers.podero.com/api-reference/platform/platform-fleet.md): Podero-wide aggregates. No organization or device identifiers leave this route. - [Platform Services](https://developers.podero.com/api-reference/platform/platform-services.md) - [Platform Service Health](https://developers.podero.com/api-reference/platform/platform-service-health.md): Podero-wide current service health. No organization or device identifiers leave this route. - [List users in the organization](https://developers.podero.com/api-reference/users/list-users-in-the-organization.md): List users within the specified organization. - [Register a new user](https://developers.podero.com/api-reference/users/register-a-new-user.md): Create a new user in the specified organization, with a JSON payload. - [Count of members matching the filters](https://developers.podero.com/api-reference/users/count-of-members-matching-the-filters.md): Number of members matching the same filters as the users list — the filtered total the paginated list response can't carry itself, so the console can size its pager range and page count to the active filters. Filters compose (AND) exactly as on the list. - [Aggregate member counts, buckets and facets](https://developers.podero.com/api-reference/users/aggregate-member-counts-buckets-and-facets.md): Org-wide aggregate for the console Users screen: member counts, Support and health bucket counts (a server-side count over the same per-member classification the users list serves), and the facet options (OEMs and device kinds present) that drive the filter dropdowns — without the client fetching th… - [Get details about a user](https://developers.podero.com/api-reference/users/get-details-about-a-user.md): Get the data of a user by its ID and by the ID of the user's organization. - [Update the user information](https://developers.podero.com/api-reference/users/update-the-user-information.md): Update the user data through the user ID and through the ID of the user's organization, with a JSON payload. - [Remove a user](https://developers.podero.com/api-reference/users/remove-a-user.md): Delete a user by its user ID and the ID of the user's organization. - [Get details about an user by external ID](https://developers.podero.com/api-reference/users/get-details-about-an-user-by-external-id.md): Get the data of a user by its external ID. - [Get the user's charging configuration](https://developers.podero.com/api-reference/user-charging-config/get-the-users-charging-configuration.md): Owner-level steering mode, HEMS eligibility, available modes with reason codes, thresholds, and the live solar-charging status. - [Update the user's charging configuration](https://developers.podero.com/api-reference/user-charging-config/update-the-users-charging-configuration.md): Apply mode and/or threshold changes to all of the user's charging devices in one transaction. Rejects modes outside ``available_modes`` and thresholds below any device's band minimum (422). - [List completed charging sessions across a user's EVs and wallboxes](https://developers.podero.com/api-reference/user-charging-sessions/list-completed-charging-sessions-across-a-users-evs-and-wallboxes.md) - [Get all currently-open charging sessions for a user](https://developers.podero.com/api-reference/user-charging-sessions/get-all-currently-open-charging-sessions-for-a-user.md): Returns `{ "sessions": [...] }` with one full detail per open session (a user can have several EVs and wallboxes charging at once). Returns 200 with an empty list when nothing is active, so clients can poll without exception handling. Wallbox energy/savings and command counters are running totals co… - [Get one finished charging session as aligned 15-minute series](https://developers.podero.com/api-reference/user-charging-sessions/get-one-finished-charging-session-as-aligned-15-minute-series.md): Battery level, wallbox power, price and one series per authenticated inverter on one 15-minute grid, over a server-determined window that pads the charge on each side. Finished sessions only: a session that is still running returns 404. - [Get one charging session with its decision timeline, command verdicts and home-energy context](https://developers.podero.com/api-reference/user-charging-sessions/get-one-charging-session-with-its-decision-timeline-command-verdicts-and-home-energy-context.md) - [Get a user's electric vehicles](https://developers.podero.com/api-reference/user-electric-vehicles/get-a-users-electric-vehicles.md): List all electric vehicles of a specific user, at a fixed query cost regardless of fleet size. - [Register a user's electric vehicle](https://developers.podero.com/api-reference/user-electric-vehicles/register-a-users-electric-vehicle.md): Create a new electric vehicle for a specific user under a specific organization, with a JSON payload. - [Get EV data](https://developers.podero.com/api-reference/user-electric-vehicles/get-ev-data.md): Time-bucketed telemetry for one electric vehicle between `from_datetime` and `to_datetime` at the requested `resolution` (15MIN by default; 1HOUR, 1DAY, 1WEEK and 1MONTH aggregate). Each point carries `battery_level` in percent, `is_charging`, `is_plugged_in`, `is_at_optimized_location`, the `price`… - [Get details about a user's electric vehicle](https://developers.podero.com/api-reference/user-electric-vehicles/get-details-about-a-users-electric-vehicle.md): Get the electric vehicle related to a specific user under a specific organization. - [Update details of a user's electric vehicle](https://developers.podero.com/api-reference/user-electric-vehicles/update-details-of-a-users-electric-vehicle.md): Modify the data of an electric vehicle related to a specific user under a specific organization, with a JSON payload. - [Remove a user's electric vehicle](https://developers.podero.com/api-reference/user-electric-vehicles/remove-a-users-electric-vehicle.md): Remove an electric vehicle related to a specific user under a specific organization. - [Reauthenticate a user's electric vehicle](https://developers.podero.com/api-reference/user-electric-vehicles/reauthenticate-a-users-electric-vehicle.md): Reauthenticate a electric vehicle related to a specific user under a specific organization. - [Get savings data for a specified electric vehicle](https://developers.podero.com/api-reference/user-electric-vehicles/get-savings-data-for-a-specified-electric-vehicle.md): Retrieve time-bucketed savings data for a specified electric vehicle within a given date range. - [Trigger a boost charge or arm boost for the next session](https://developers.podero.com/api-reference/user-electric-vehicles/trigger-a-boost-charge-or-arm-boost-for-the-next-session.md): Trigger boost on the EV. - [Cancel a live boost and disarm a boost armed for the next session](https://developers.podero.com/api-reference/user-electric-vehicles/cancel-a-live-boost-and-disarm-a-boost-armed-for-the-next-session.md): Undo a boost on the EV — unified "stop boosting" affordance. - [(Alpha) Get statistics for a specified electric vehicle](https://developers.podero.com/api-reference/user-electric-vehicles/alpha-get-statistics-for-a-specified-electric-vehicle.md): Retrieve savings and consumption data for a specified electric vehicle, allowing filtering by keywords and aggregation by various time resolutions. This endpoint is currently in Alpha release and should only be used for testing. - [Get a vehicle's charge policy](https://developers.podero.com/api-reference/electric-vehicle-charge-policies/get-a-vehicles-charge-policy.md) - [Set a vehicle's charge policy](https://developers.podero.com/api-reference/electric-vehicle-charge-policies/set-a-vehicles-charge-policy.md) - [Override a vehicle's charge policy by settings a deadline](https://developers.podero.com/api-reference/electric-vehicle-charge-policy-overrides/override-a-vehicles-charge-policy-by-settings-a-deadline.md) - [Override a vehicle's charge policy by settings a deadline](https://developers.podero.com/api-reference/electric-vehicle-charge-policy-overrides/override-a-vehicles-charge-policy-by-settings-a-deadline-1.md) - [Override a vehicle's charge policy by settings a deadline](https://developers.podero.com/api-reference/electric-vehicle-charge-policy-overrides/override-a-vehicles-charge-policy-by-settings-a-deadline-2.md) - [List completed charging sessions for an electric vehicle](https://developers.podero.com/api-reference/electric-vehicle-sessions/list-completed-charging-sessions-for-an-electric-vehicle.md): One row per completed charging session of this vehicle, newest first, for sessions that started on a UTC day between `from` and `to` inclusive. Each row carries the session outcome, the energy delivered in kWh, the savings figures in EUR with their attribution reason, the state of charge at start an… - [Get the currently active charging session for an electric vehicle](https://developers.podero.com/api-reference/electric-vehicle-sessions/get-the-currently-active-charging-session-for-an-electric-vehicle.md): Returns the active session wrapped as `{ "session": ... }`. When no session is active, returns 200 with `{ "session": null }` instead of 404 so clients can poll without exception handling. - [Dismiss Heat Pump Explainer](https://developers.podero.com/api-reference/user-heat-pumps/dismiss-heat-pump-explainer.md) - [Get the current plan explanation for a heat pump](https://developers.podero.com/api-reference/user-heat-pumps/get-the-current-plan-explanation-for-a-heat-pump.md): The customer-facing narrative of what this heat pump is planned to do next, written in the organization's language unless `language` overrides it. It is generated on the first read of a plan and cached, so a call that finds no cached explanation writes one and can take several seconds. `null` means… - [Get the explanation of a past window for a heat pump](https://developers.podero.com/api-reference/user-heat-pumps/get-the-explanation-of-a-past-window-for-a-heat-pump.md): The customer-facing narrative of what this heat pump did over a past window, written in the organization's language unless `language` overrides it. It is generated on the first read of a window and cached, so a call that finds no cached explanation writes one and can take several seconds. `null` mea… - [Submit Heat Pump Explainer Feedback](https://developers.podero.com/api-reference/user-heat-pumps/submit-heat-pump-explainer-feedback.md) - [Get heat pump data](https://developers.podero.com/api-reference/user-heat-pumps/get-heat-pump-data.md): Retrieve time series data for a specified heat pump within a given time range. This endpoint is currently in beta release and may be subject to changes. - [Get schedules for a heat pump](https://developers.podero.com/api-reference/user-heat-pumps/get-schedules-for-a-heat-pump.md): Endpoint to retrieve schedules for a specified heat pump within a given time range. This endpoint is currently in beta release and may be subject to changes. - [Get savings data for a specified heat pump](https://developers.podero.com/api-reference/user-heat-pumps/get-savings-data-for-a-specified-heat-pump.md): Retrieve time-bucketed savings data for a specified heat pump within a given date range. - [Get statistics for a specified heat pump](https://developers.podero.com/api-reference/user-heat-pumps/get-statistics-for-a-specified-heat-pump.md): Retrieve savings and consumption data for a specified heat pump, allowing filtering by keywords and aggregation by various time resolutions. This endpoint is currently in Alpha release and should only be used for testing. - [Get all of a user's heat pumps](https://developers.podero.com/api-reference/user-heat-pumps/get-all-of-a-users-heat-pumps.md): List all heat pumps of a specific user, at a fixed query cost regardless of fleet size. - [Register a user's heat pump](https://developers.podero.com/api-reference/user-heat-pumps/register-a-users-heat-pump.md): Create a new heat pump for a specific user under a specific organization, with a JSON payload. - [Get details about a user's specific heat pump](https://developers.podero.com/api-reference/user-heat-pumps/get-details-about-a-users-specific-heat-pump.md): Get the heat pump related to a specific user under a specific organization. - [Update details of a user's heat pump](https://developers.podero.com/api-reference/user-heat-pumps/update-details-of-a-users-heat-pump.md): Modify the data of a heat pump related to a specific user under a specific organization, with a JSON payload. - [Remove a user's heat pump](https://developers.podero.com/api-reference/user-heat-pumps/remove-a-users-heat-pump.md): Remove a user's heat pump. - [Reauthenticate a user's heat pump](https://developers.podero.com/api-reference/user-heat-pumps/reauthenticate-a-users-heat-pump.md): Reauthenticate a heat pump related to a specific user under a specific organization. - [Get applied-mode history for a heat pump](https://developers.podero.com/api-reference/user-heat-pumps/get-applied-mode-history-for-a-heat-pump.md): The mode changes one heat pump was actually put into over a window, oldest first — the measured companion of the planned `/schedules`, drawn instead from the steering workflow's own record of what it sent and what the manufacturer accepted. Each item is one change: the time it took effect, the mode,… - [Get the current plan explanation for an inverter](https://developers.podero.com/api-reference/user-solar-inverters/get-the-current-plan-explanation-for-an-inverter.md): The customer-facing narrative of what this inverter's battery is planned to do next, written in the organization's language unless `language` overrides it. It is generated on the first read of a plan and cached, so a call that finds no cached explanation writes one and can take several seconds. `nul… - [Get the explanation of a past window for an inverter](https://developers.podero.com/api-reference/user-solar-inverters/get-the-explanation-of-a-past-window-for-an-inverter.md): The customer-facing narrative of what this inverter's battery did over a past window, written in the organization's language unless `language` overrides it. It is generated on the first read of a window and cached, so a call that finds no cached explanation writes one and can take several seconds. `… - [Dismiss Inverter Explainer](https://developers.podero.com/api-reference/user-solar-inverters/dismiss-inverter-explainer.md) - [Submit Inverter Explainer Feedback](https://developers.podero.com/api-reference/user-solar-inverters/submit-inverter-explainer-feedback.md) - [Get a user's solar inverters](https://developers.podero.com/api-reference/user-solar-inverters/get-a-users-solar-inverters.md): List all solar inverters of a specific user, at a fixed query cost regardless of fleet size. - [Register a user's solar inverter](https://developers.podero.com/api-reference/user-solar-inverters/register-a-users-solar-inverter.md): Create a new solar inverter for a specific user under a specific organization, with a JSON payload. - [Get details about a user's solar inverter](https://developers.podero.com/api-reference/user-solar-inverters/get-details-about-a-users-solar-inverter.md): Get the solar inverter related to a specific user under a specific organization. - [Update details of a user's solar inverter](https://developers.podero.com/api-reference/user-solar-inverters/update-details-of-a-users-solar-inverter.md): Modify the data of a solar inverter related to a specific user under a specific organization, with a JSON payload. - [Remove a user's solar inverter](https://developers.podero.com/api-reference/user-solar-inverters/remove-a-users-solar-inverter.md): Remove a solar inverter related to a specific user under a specific organization. - [Get inverter data](https://developers.podero.com/api-reference/user-solar-inverters/get-inverter-data.md): Retrieve time series data for a specified inverter within a given time range. This endpoint is currently in beta release and may be subject to changes. - [Get statistics for a specified inverter](https://developers.podero.com/api-reference/user-solar-inverters/get-statistics-for-a-specified-inverter.md): Retrieve savings and consumption data for a specified inverter, allowing filtering by keywords and aggregation by various time resolutions.This endpoint is currently in Alpha release and should only be used for testing. - [Get savings data for a specified inverter](https://developers.podero.com/api-reference/user-solar-inverters/get-savings-data-for-a-specified-inverter.md): Retrieve time-bucketed savings data for a specified inverter within a given date range. - [Reauthenticate a user's inverter](https://developers.podero.com/api-reference/user-solar-inverters/reauthenticate-a-users-inverter.md): Reauthenticate an inverter related to a specific user under a specific organization. - [Get schedules for an inverter](https://developers.podero.com/api-reference/user-solar-inverters/get-schedules-for-an-inverter.md): Endpoint to retrieve schedules for a specified inverter within a given time range. This endpoint is currently in beta release and may be subject to changes. - [Get a user's wallboxes](https://developers.podero.com/api-reference/user-wallboxes/get-a-users-wallboxes.md): List all wallboxes of a specific user, at a fixed query cost regardless of fleet size. - [Register a user's wallbox](https://developers.podero.com/api-reference/user-wallboxes/register-a-users-wallbox.md): Create a new wallbox for a specific user under a specific organization, with a JSON payload. - [Mint a one-time wallbox claim token for the user](https://developers.podero.com/api-reference/user-wallboxes/mint-a-one-time-wallbox-claim-token-for-the-user.md) - [Get details about a user's wallbox](https://developers.podero.com/api-reference/user-wallboxes/get-details-about-a-users-wallbox.md): Get the wallbox related to a specific user under a specific organization. - [Update details of a user's wallbox](https://developers.podero.com/api-reference/user-wallboxes/update-details-of-a-users-wallbox.md): Modify the data of an wallbox related to a specific user under a specific organization, with a JSON payload. - [Remove a user's wallbox](https://developers.podero.com/api-reference/user-wallboxes/remove-a-users-wallbox.md): Remove a wallbox related to a specific user under a specific organization. - [Send a raw start-charging command to an EV charger (wallbox)](https://developers.podero.com/api-reference/user-wallboxes/send-a-raw-start-charging-command-to-an-ev-charger-wallbox.md): Push a raw start command onto the wire of the EV charger identified by the given UUID. - [Send a raw stop-charging command to an EV charger (wallbox)](https://developers.podero.com/api-reference/user-wallboxes/send-a-raw-stop-charging-command-to-an-ev-charger-wallbox.md): Push a raw stop command onto the wire of the EV charger identified by the given UUID. - [Trigger a boost charge or arm boost for the next session](https://developers.podero.com/api-reference/user-wallboxes/trigger-a-boost-charge-or-arm-boost-for-the-next-session.md): Trigger a "charge now" boost on the wallbox, overriding whatever optimization it is under — solar-surplus control, price windows, or both. - [Cancel a live boost and disarm a boost armed for the next session](https://developers.podero.com/api-reference/user-wallboxes/cancel-a-live-boost-and-disarm-a-boost-armed-for-the-next-session.md): Undo a boost on the wallbox — unified "stop boosting" affordance. - [Enter the connected car's state of charge and schedule for the current charging session](https://developers.podero.com/api-reference/user-wallboxes/enter-the-connected-cars-state-of-charge-and-schedule-for-the-current-charging-session.md): Provide what is known about the car plugged into the wallbox right now. - [Reauthenticate a user's wallbox](https://developers.podero.com/api-reference/user-wallboxes/reauthenticate-a-users-wallbox.md): Reauthenticate a wallbox related to a specific user under a specific organization. - [List standalone HEMS steering sessions for a wallbox](https://developers.podero.com/api-reference/wallbox-hems-sessions/list-standalone-hems-steering-sessions-for-a-wallbox.md): One row per charging session the wallbox steered on its own, without a connected vehicle account, newest first, for sessions that started on a UTC day between `from` and `to` inclusive. Each row carries the rolled-up outcome, the energy taken from solar, the home battery and the grid in kWh, the sav… - [Get the currently running standalone HEMS session for a wallbox](https://developers.podero.com/api-reference/wallbox-hems-sessions/get-the-currently-running-standalone-hems-session-for-a-wallbox.md): Returns the open session wrapped as `{ "session": ... }` with its decision timeline and per-command steering verdicts. When none is running, returns 200 with `{ "session": null }` so clients can poll without exception handling. `energy_from_solar_kwh` and `savings_eur` are running totals computed as… - [Get one standalone HEMS session with its decision timeline and command verdicts](https://developers.podero.com/api-reference/wallbox-hems-sessions/get-one-standalone-hems-session-with-its-decision-timeline-and-command-verdicts.md) - [Update general device attributes](https://developers.podero.com/api-reference/user-devices/update-general-device-attributes.md): Update general attributes of a device, like `is_smart_optimization_active` or `is_authenticated`. - [Deactivates smart optimization and resets the device](https://developers.podero.com/api-reference/user-devices/deactivates-smart-optimization-and-resets-the-device.md) - [Queue a device-related message to a user](https://developers.podero.com/api-reference/user-notifications/queue-a-device-related-message-to-a-user.md): Use the same device-bound information-cue flow as the Django admin action. - [Get an Organisation's Devices](https://developers.podero.com/api-reference/devices/get-an-organisations-devices.md): Get the list of all devices for the specified organization ID. By default returns ALL devices with ALL fields. - [Resolve a Device to its owner and type](https://developers.podero.com/api-reference/devices/resolve-a-device-to-its-owner-and-type.md): Resolve a device uuid (from `GET /org/{org_id}/devices`) to its owner and type without prior knowledge of either, so cockpit deep links can follow the existing nested per-type detail route. Scoped to the org: a device in another org 404s. - [Get an Organisation's Devices Savings](https://developers.podero.com/api-reference/devices/get-an-organisations-devices-savings.md): Get the savings for the specified organization ID within a date range. - [Get an Organisation's Devices Summary](https://developers.podero.com/api-reference/devices/get-an-organisations-devices-summary.md): Whole-fleet device counts for the console Fleet screen in one call — the server-side counterpart of the client folds over the full device list (`fleetReal.ts::healthRows` / `deviceTypeShares` / `deviceSavingsLeg`): health-tone counts, type-bucket shares, and per-savings-leg device counts to sit besi… - [Scored forecast accuracy for an inverter, by hour and forecast tier](https://developers.podero.com/api-reference/devices/scored-forecast-accuracy-for-an-inverter-by-hour-and-forecast-tier.md): The scored accuracy of one inverter's forecasts over the last ``days``, per hour and tier. - [Counts of pending actions and unread information notifications, grouped by device type.](https://developers.podero.com/api-reference/notifications/counts-of-pending-actions-and-unread-information-notifications-grouped-by-device-type.md): ``action_required`` counts cues whose projection's ``action_required(events)`` is True — the same semantic as the per-device ``action_needed`` flag, so a cue mid-resolution (``ReauthenticationSucceeded`` event landed, cue not yet flipped to DONE) doesn't count. ``information_available`` counts unrea… - [List an organization's pending user-facing action projections.](https://developers.podero.com/api-reference/notifications/list-an-organizations-pending-user-facing-action-projections.md): Render pending cues + unread information notifications into a merged, newest-first list of ``DeviceAction`` projections. Both source tables are capped at ``limit + offset`` rows at SQL before the Python-side merge + sort + slice, so page cost scales with the requested window, not the org's total pen… - [List an organization's information notifications.](https://developers.podero.com/api-reference/notifications/list-an-organizations-information-notifications.md): Newest-first history of information notifications across the organization, bounded at SQL. Resolution links are minted per record for that notification's owner. - [List an organization's notification webhooks](https://developers.podero.com/api-reference/notification-webhooks/list-an-organizations-notification-webhooks.md): List the organization's registered notification webhooks in a stable order, so pagination is deterministic. The order is not a chronological contract: it keys on the projection row's own creation time, which a projection rebuild would reset. Results are paginated with 50 items per page. The signing… - [Register a notification webhook](https://developers.podero.com/api-reference/notification-webhooks/register-a-notification-webhook.md): Register a webhook for the organization, provision its signing secret, and subscribe it to the given topics — all in one atomic append. The signing secret is returned once in this response and never again, so the caller must store it now. A malformed or disallowed URL (non-https outside dev, or an S… - [Retrieve a notification webhook](https://developers.podero.com/api-reference/notification-webhooks/retrieve-a-notification-webhook.md): Retrieve one of the organization's webhooks. A webhook that does not exist or belongs to another organization is reported as not found. - [Delete a notification webhook](https://developers.podero.com/api-reference/notification-webhooks/delete-a-notification-webhook.md): Remove a webhook, ending its stream and dropping it from the listing. A webhook that does not exist or belongs to another organization is reported as not found. - [Update a notification webhook](https://developers.podero.com/api-reference/notification-webhooks/update-a-notification-webhook.md): Update a webhook's delivery switch and/or its subscribed topics. Only the fields present in the request change; ``topics`` replaces the whole set. The endpoint URL is immutable — delete and recreate to change it. A webhook that does not exist or belongs to another organization is reported as not fou… - [Rotate a webhook's signing secret](https://developers.podero.com/api-reference/notification-webhooks/rotate-a-webhooks-signing-secret.md): Mint a fresh signing secret for the webhook, superseding the previous one — the next delivery signs with it. The new secret is returned once in this response and never again, so the caller must store it now. A webhook that does not exist or belongs to another organization is reported as not found. - [Send a test message to a webhook for one of its subscribed topics](https://developers.podero.com/api-reference/notification-webhooks/send-a-test-message-to-a-webhook-for-one-of-its-subscribed-topics.md): Deliver a synthetic sample of one subscribed topic to the webhook and return the delivery outcome, so a partner can verify their endpoint receives and accepts what a real notification for that topic looks like. The topic must be one the webhook is subscribed to (else 400); the sample is addressed st… - [Get the day-ahead prices the organisation trades against](https://developers.podero.com/api-reference/trading/get-the-day-ahead-prices-the-organisation-trades-against.md): The day-ahead price series for one `price_zone` between `from_dt` and `to_dt`, as supplied to the organisation's price feed: one `price` per delivery interval, in the unit and currency of that feed. These are the prices the fleet's day-ahead optimisation planned against, not settled market prices, a… - [Create Trading Dayahead Prices](https://developers.podero.com/api-reference/trading/create-trading-dayahead-prices.md) - [Update Trading Dayahead Prices](https://developers.podero.com/api-reference/trading/update-trading-dayahead-prices.md) - [Get the organisation's day-ahead load curve for one delivery day](https://developers.podero.com/api-reference/loadcurves/get-the-organisations-day-ahead-load-curve-for-one-delivery-day.md): The organisation's aggregated load curve for one delivery `day` at the requested `resolution` (15MIN or 1HOUR): the optimised curve the fleet is planned to follow and the unoptimised curve it would have followed without steering, as energy per interval. `keywords` selects which of the two curves is… - [Get By Price Zone](https://developers.podero.com/api-reference/loadcurves/get-by-price-zone.md) - [Get one prepared day-ahead forecast response](https://developers.podero.com/api-reference/loadcurves/get-one-prepared-day-ahead-forecast-response.md) - [Post](https://developers.podero.com/api-reference/loadcurves-confirmation/post.md) - [Create a new Device Onboarding Session](https://developers.podero.com/api-reference/device-onboarding-sessions/create-a-new-device-onboarding-session.md): This endpoint creates a new onboarding session and generates an authentication URL which leads to Connect UI. This application takes end-users through onboarding their device. Upon success, it redirects back to the success_url. If unsuc… - [Mint a wallbox claim token for the onboarding session's user](https://developers.podero.com/api-reference/device-onboarding-sessions/mint-a-wallbox-claim-token-for-the-onboarding-sessions-user.md) - [Check if a wallbox claim token has been claimed](https://developers.podero.com/api-reference/device-onboarding-sessions/check-if-a-wallbox-claim-token-has-been-claimed.md) - [Get Device Onboarding Session](https://developers.podero.com/api-reference/device-onboarding-sessions/get-device-onboarding-session.md): Fetch information about a device onboarding session - [Start a pending action](https://developers.podero.com/api-reference/cues/start-a-pending-action.md): Start the action identified by the URL. Both `cue_id` and `secret` are obtained from the action's `resolution_link.url`; the `secret` is a signed token bound to the action's owner and expires 1 hour after it is issued. The caller must be the owner's own session or a token of the owner's organisation… - [Get the pairing link of a virtual-key action](https://developers.podero.com/api-reference/cues/get-the-pairing-link-of-a-virtual-key-action.md): Return the Tesla link that adds the Podero virtual key to the car of a `virtual_key_required` action. Both `cue_id` and `secret` come from the action's `resolution_link.url`. The `secret` is a signed token bound to the car's owner and expires 1 hour after it is issued. The caller must be the owner's… - [Report the outcome of an active action](https://developers.podero.com/api-reference/cues/report-the-outcome-of-an-active-action.md): Report the outcome of an action previously started via `/cues/{cue_id}/resolve`. Requires the same signed `secret` used to start it. The action must still be active — otherwise a 404 is returned. - [Mark an information action as read](https://developers.podero.com/api-reference/cues/mark-an-information-action-as-read.md): Acknowledge that the end-user has read the information message identified by the URL. Both `cue_id` and `secret` are obtained from the action's `resolution_link.url`; the `secret` is a signed token bound to the message's owner and expires 1 hour after it is issued. The caller must be the owner's own… - [Get Control](https://developers.podero.com/api-reference/trading-control/get-control.md) - [Control Action](https://developers.podero.com/api-reference/trading-control/control-action.md) - [Get Accounts](https://developers.podero.com/api-reference/trading-control/get-accounts.md) - [Create Account](https://developers.podero.com/api-reference/trading-control/create-account.md) - [Overview](https://developers.podero.com/deep-dives/day-ahead-trading/overview.md): Understand how Podero optimizes your energy portfolio through day-ahead market participation - [Integration Guide](https://developers.podero.com/deep-dives/day-ahead-trading/integration.md): Step-by-step API integration for Day-Ahead Trading - [Data Reference](https://developers.podero.com/deep-dives/day-ahead-trading/data-reference.md): Data specifications and formats for Day-Ahead Trading ## OpenAPI Specs - [openapi](https://app.podero.com/api/partners/v2.0/openapi.json) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.