1. Control Commands & Dispatch
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. Control Commands & Dispatch

2. Scheduler V3 Operations

Scheduler V3 is designed for advanced VPP use cases. It supports highly flexible segment definitions and allows for batch configuration of multiple devices.

2.1 Core Business Logic & Constraints#

Before integrating the Scheduler V3 APIs, it is crucial to understand the following operational rules to ensure successful dispatching:
24-Hour Forward Scheduling: All scheduling interfaces only accept plans for the next 24 hours. You cannot schedule commands beyond this window.
96-Segment Limit & Full Coverage: The Scheduler supports a maximum of 96 time segments per request.
Auto-Cleanup Rule: When you submit a new schedule, FoxCloud will completely overwrite the device's existing plan. If your request contains fewer than 96 segments, the system will automatically disable/close the remaining time slots. This ensures that the device strictly follows only the instructions you have explicitly sent.
Cross-Midnight Scheduling: If you need to schedule a continuous operation that crosses midnight (e.g., charging from 23:00 to 01:00), you must split it into two separate segments: one from 23:00 to 23:59, and another from 00:00 to 01:00. The system does not automatically merge cross-day segments.
Reference: For the complete JSON request body structure, parameter definitions, and response examples, please refer to the Full API Reference List and search for /op/v3/device/scheduler.

2.2 Core API Endpoints#

Query Scheduler: POST /op/v3/device/scheduler/get
Enable/Set Scheduler: POST /op/v3/device/scheduler/enable
To Cancel All Schedules: Send an empty list [] as the segment parameter to this endpoint to wipe all persistent schedules from the device.

2.3 Batch Asynchronous Dispatch#

️ High-Volume Dispatching
We understand that VPP operators often need to dispatch thousands of devices simultaneously. Scheduler V3 provides a dedicated batch endpoint to handle these scenarios efficiently.
API Endpoint: POST /op/v3/device/scheduler/enable/batch
Business Logic: When using the batch enable endpoint, the operation is processed asynchronously. The API will return an immediate acknowledgment, and you can configure a Webhook callback to receive the final execution result for each device in the batch.
Modified at 2026-07-09 12:18:06
Previous
1. Core Dispatch Architecture: Scheduler V3
Next
3. Real-time Device Settings
Built with