Reposit Power Market API
The larger of Reposit's two published contracts, and the one that actually controls hardware. A verbatim OpenAPI 3.0.1 document served anonymously at https://marketapi.repositpower.com/docs/spec/ (filename public-fleet-api.yaml, last-modified 2025-06-24) and rendered in Swagger UI at https://marketapi.repositpower.com/docs/ under the title "Reposit Power Fleet API". The spec describes itself as the API "used by fleet.repositpower.com and related services". Twenty-eight operations across twenty-two paths, tagged by the audience allowed to call them — Network, Retailer, Installer, Customer — and by subject: Node (list deployments and read their address, network NMI, operational status, name plate and events), Power Station (full CRUD over aggregations of nodes, plus downsampled, raw and latest telemetry), Data (fleet-wide downsampled metrics), Curtailment (read constraints, create, list, cancel, get and change an export setpoint, and post a heartbeat), Dispatch (create, list and get export dispatches), Capabilities (assign customers to a capability) and Users. This is the virtual-power-plant control plane: a network or retailer partner can curtail or dispatch the exports of real Australian households through it. Authentication is a bearer API key (components.securitySchemes.AccessToken, type apiKey, in header, name Bearer) that cannot be self-served — the spec's own description states the key is generated inside the logged-in Reposit Fleet web app at https://fleet.repositpower.com/user/settings, inherits that account's permissions, never expires, may be pinned to whitelisted origin IP addresses, and is revocable from the same screen. Fleet accounts are issued to partner organisations, so the real gate is a commercial relationship with Reposit. Confirmed on 2026-07-27 that GET /api/nodes, /api/powerstations, /api/data, /api/curtailments, /api/dispatches and /api/users all return HTTP 401 {"error":"unauthorized"} anonymously.