If you want remote control inside your own product — one-click remote from a ticket, device management in an ops platform — the open interfaces make it possible.
What you can do
List devices and their status, start remote sessions, query session and audit records, and sync members and groups into your existing workflows.
- List devices and online status
- Start remote sessions
- Query session and audit records
- Sync member and group information
How to integrate
Create an application on the open platform to get credentials, call the server-side interfaces, and follow the documentation for authentication and callbacks.
- Create an app and obtain keys
- Complete interface authentication
- Configure callbacks for events
- Validate in a test environment first
Security and rate limits
Keep keys server-side and never in client code; interfaces have rate limits, so build in retries and idempotency.
- Store keys only on the server
- Respect rate limits
- Design retries and idempotency
- Rotate keys periodically
FAQ
Can sessions start without the user noticing?
No. Remote control sessions always require authorisation and notification, and API calls are subject to the same permissions and auditing.
Are there call limits?
Yes, rate and quota limits apply as documented. Beyond them, cache locally and process asynchronously.