1. Overview & Integration Scope
1.1 Target Audience & Purpose#
This documentation is exclusively designed for third-party Virtual Power Plant (VPP) operators and platform developers.Goal: Enable your platform to securely enroll end-users, collect telemetry data, and dispatch control commands to FoxESS battery devices.
Boundary: Your platform never communicates directly with hardware. FoxCloud acts as the mandatory intermediary for all data and commands.
1.2 Integration Architecture#
The integration follows a strict OAuth 2.0 flow for enrollment and a Brokered Data model for operations.1.
Enrollment (OAuth): The end-user grants permission via the FoxESS h5 page.
2.
Telemetry (Pull/Push): Data flows from Device → FoxCloud → Your Platform (via API Polling or Kafka).
3.
Control (API): Commands flow from Your Platform → FoxCloud → Device.
1.3 Documentation Roadmap#
This guide is structured as a linear journey. Follow these steps to go live:1.
Phase 1: User Enrollment (End-User Enrollment & OAuth Flow)Focus: How to get user permission and bind devices.
Key Flow: Redirect -> Consent -> Device SN callback.
2.
Phase 2: API Technical Foundation (API Technical Specifications)Focus: The universal rules for calling all FoxCloud APIs (Authentication, Signing, Error Handling).
Key Concept: signature header, timestamp, and response codes.
3.
Phase 3: Data & Control (Telemetry & Command Modules)Focus: Specific payloads for fetching data and sending commands.
Modified at 2026-08-04 02:41:31