1. End-User Enrollment & OAuth Flow
FoxCloud OpenAPI
Vpp Flow
  • Vpp Flow
  • Full API Reference
  • What's New & Milestones
  • Getting Started
    • 1. Overview & Integration Scope
    • 2. Environments & Prerequisites
  • End-User Enrollment & OAuth Flow
    • 0. Introduction
    • 1. The User Authorization Journey
    • 2. OAuth Token Operating Model
    • 3. Implementation Guide
  • API Technical Specifications
    • 1. Universal Request Rules
    • 2. Rate Limiting Strategy
    • 3. Response Structure
    • 4. Error Code Reference
  • Telemetry & Data Acquisition
    • 1. Data Pipeline & Scaling Strategy
    • 2. Telemetry Data Query (Real-time)
    • 4. Telemetry Variable Dictionary
    • 5. System Performance & SLA
    • 3. Device Configuration & Settings: Pre-Dispatch State Awareness
  • Control Commands & Dispatch
    • 1. Core Dispatch Architecture: Scheduler V3
    • 2. Scheduler V3 Operations
    • 3. Real-time Device Settings
    • 4. Strategic Roadmap: Scaling for Massive Fleets
  • FAQ
    • Troubleshooting Quick Guide
  1. End-User Enrollment & OAuth Flow

1. The User Authorization Journey

The enrollment process begins when a user registers on the VPP platform and initiates the binding process. They are redirected to the FoxESS H5 Authorization Page. Crucially, upon successful authorization, the user will see a "VPP in Control" indicator in their Fox app, restricting their ability to manually control the device.
Key States in H5 Page:
StateDescriptionRequired Action
AvailableCompatible and free to bind.User selects & confirms to proceed.
UsedAlready bound to another VPP.Stop: User must return to the original VPP app to unbind before proceeding.
Not SupportedHardware model is not on the VPP whitelist.Stop: Hardware is incompatible.
Upgrade RequiredModel is supported but requires a firmware update.Stop: Firmware update is needed.
Note on User Experience
Once the binding is confirmed, the device enters the "VPP in Control" state. This is visually enforced in the Fox mobile application to prevent user-VPP conflicts. Do not expect users to have manual control over dispatch parameters while enrolled in your program.
Modified at 2026-08-04 02:42:35
Previous
0. Introduction
Next
2. OAuth Token Operating Model
Built with