Reposit Customer API
Reposit's own documented REST API for the owner of a Reposit-controlled home energy system, described by a verbatim OpenAPI 3.0.3 contract that the company serves anonymously at https://api.repositpower.com/spec/ (filename openapi.yaml, last-modified 2024-11-28) and renders in Swagger UI at https://api.repositpower.com/docs/. Eleven operations across two declared tags. Two of them log in and refresh; one lists the userkeys — the battery system identifiers — attached to the calling account; the remaining eight read one deployment's hardware components, battery capacity, historical solar generation, battery-inverter real power, house consumption, battery state of charge in kWh, real power at the grid connection, and GridCredits earned in dollars. The spec's own info block calls it "an informal description of external Reposit API provided to Reposit customers" and points feedback at api@repositpower.com. Authentication is a bearer JWT (components.securitySchemes.bearerAuth, type http / scheme bearer / bearerFormat JWT) obtained by POSTing Reposit account credentials to /v2/auth/login/ with a Reposit-Auth header of either Stateless or API; the API variant additionally returns a refresh_token for /v2/auth/refresh/. Access is therefore customer-account-required: a developer who is not a Reposit customer has no way to obtain a token. Confirmed on 2026-07-27 that POST /v2/auth/login/ with junk credentials returns HTTP 401 {"error":"unauthorized"} and GET /v2/userkeys/ returns HTTP 401 anonymously.