Content & ServicesDeveloper Platform
Switch to Next Content
Quick Guide
Prerequisites
- Make sure you have retrieved and saved your API key in the Dot. App;
- Make sure you own at least one device and have obtained its device serial number;
- Make sure your device is connected to power;
- Make sure your device is connected to the network;
The API rate limit is 10 requests per second. With the API, you can control device behavior and responses more flexibly.
Placeholders wrapped in '{{variable}}' indicate values you must replace. Fill them with your actual values and remove the '{{}}' braces.
Request Examples
POST
/api/authV2/open/device/:id/nextGenerated Code
1// Generating...Response Example
{
"code": 200,
"message": "Device ABCD1234ABCD successfully switched to next content",
"result": {
"message": "Device ABCD1234ABCD successfully switched to next content"
}
}Reference Usage
This API allows you to control the device to immediately switch to the next item in the content loop without waiting for the scheduled refresh time. This is particularly useful for:
- Remotely triggering content updates
- Testing content switching functionality
- Implementing custom content scheduling logic
Troubleshooting
Endpoint
/api/authV2/open/device/:id/next
Method
POST
Path Parameters
Prop
Type
Device serial number
Request Schema
This interface does not require a request body, only an API key in the request header and a device ID in the path parameter.
Response Schema
Prop
Type
Status code
Response description
Status Codes
| code | Meaning | Description |
|---|---|---|
200 | Success | Device successfully switched to next content |
400 | Invalid params | Invalid device ID format |
401 | Unauthorized | Invalid or expired API key |
403 | Forbidden | No permission to operate this device |
404 | Not found | Device not found or not registered |
500 | Device response failure | Device offline or switch failed |
Did this solve your problem?
Join our community