Schedule device reboots using the Scheduling API

Android

When the Esper Console does not provide a built-in UI for scheduling reboots, you can trigger timed or recurring device reboots programmatically using the Esper Scheduling API — for individual devices or entire groups.

Why this happens

Scheduled reboots are not yet configurable through the Esper Console interface. The Scheduling API exposes this capability directly, letting you define execution time, recurrence pattern, and timezone for any REBOOT command sent to a device or group.

Before you begin

Gather the following before making any API calls:

• An active Esper API key — available from Esper Console → API Key Management
• The serial number of the target device, or the group ID if targeting a device group
• Your intended schedule: execution time, recurrence pattern (one-time or repeating), and timezone

Schedule a reboot via the Scheduling API

1. Open the Esper API Reference and navigate to the Scheduling API → Commands section. This is where all schedulable device commands, including REBOOT, are documented.
2. Construct a POST request to the Scheduling API endpoint. Include the following in your request body:
   • command_type set to REBOOT
   • device_id or group_id for your target
   • schedule object containing start_datetime, timezone, and recurrence (if repeating)
3. Add your Esper API key as a Bearer token in the Authorization header. Without a valid, active key the request will be rejected with an authentication error.
4. Submit the request and confirm the API returns a 201 Created response with a schedule_id in the response body. Record this ID — it identifies the scheduled job for future reference or cancellation.

Verify the reboot executed

After the scheduled time passes:

1. Navigate to Devices & Groups → [Device Name] → Activity Feed in the Esper Console.
2. Look for a REBOOT command entry with a status of Success and a timestamp matching your scheduled execution time.

Verify: The REBOOT command should appear as Success in the Activity Feed within a few minutes of the scheduled execution time. If the device was offline at the scheduled time, the command will execute the next time the device comes online.

If this doesn't resolve it

If the reboot does not appear in the Activity Feed or the API returns an error, check the following before contacting support:

• Authentication failure (401 Unauthorized): Confirm your API key is active in Esper Console → API Key Management. Regenerating a key invalidates the previous one.
• Malformed request (400 Bad Request): Validate your start_datetime format (ISO 8601) and confirm the timezone string is a valid IANA timezone identifier (for example, America/Los_Angeles).
• Invalid target (404 Not Found): Verify the device_id or group_id exists in Devices & Groups and that it is spelled exactly as shown in the Console.
• Device offline: The Esper Agent must be able to reach Esper's servers to receive the command. Check device connectivity and review the Activity Feed for any connectivity events around the scheduled time.

If the issue persists, contact Esper Support with the following information: your schedule_id, the device serial number or group ID, the API response body, and a screenshot of the Activity Feed for the affected device.

Still need help?

Still need help? Submit a support ticket and include details about your reboot schedule configuration, the devices affected, and any error messages you received when using the Scheduling API.