The OhrTech SDK
Your fleet, from your own code
Everything the OhrTech Portal does to a device, your servers and tools can do too. List and configure devices, message them, and open a live, controllable screen inside your own app, with access you can limit to the fleets, networks and sites you choose.
using OhrTech.Management;
using var api = OhrManagementClient.ForServiceAccount(token);
// Every device in your fleets, live
foreach (var d in await api.ListDevicesAsync(online: true))
Console.WriteLine($"{d.Serial} {d.BatteryLevel}%");
// Its screen, inside your own help desk
var rc = await api.OpenRemoteControlSessionAsync(42, new()
{
EmbedOrigins = ["https://support.example.com"]
});
// <iframe src={rc.Embed.Url}>Two parts, one SDK
Where does your code run?
Section titled “Where does your code run?”The OhrTech SDK has two parts. The Management API is for code that runs on your servers and desktops and manages many devices at once. The Device SDK is for the app you ship on the device itself.
Management API
From your servers and tools
Manage every device in your fleets over HTTPS: status, settings, messages, remote control in your own app, and remote ADB. Sign in as a service account or as a person.
Read the docs →Coming soonDevice SDK
From your app, on the device
Let the app you ship on OhrTech devices work with the OhrTech Agent: change device settings, manage network and power, lock the screen to one app, reboot on a schedule and install its own updates.
What's coming →Management API
What you can build with it
Section titled “What you can build with it”Remote support inside your own help desk
One call opens a session and returns a link you put in an <iframe>. Your support staff see the
device’s screen and control it from your app, without an OhrTech Portal account. Your page hears
what happens (waiting, the person allowed it, connected, ended) and can press keys or end the
session.
Every device setting, with inheritance
Wi-Fi networks, screen lock, brightness and volume, home screen layout, allowed keyboards, USB and Bluetooth: nearly 50 settings, each set (the person may change it) or locked. Fleets pass them down; a device can override. Every change is validated before it is stored, and you see what each device reports back.
Fleets that follow your inventory
Move devices between fleets from your own systems, by serial number. A device moved into a fleet gets that fleet’s settings at once.
Know before your users call
Every device’s last check-in, battery, network, OS build, installed apps and whether its settings applied. Ask any device to check in now. Turn it into alerts, reports and audit evidence.
Access
Made to pass your security review
Section titled “Made to pass your security review”- A service account per integration. Each has only the permissions you grant it, can be limited to particular fleets or devices, to the networks it may call from, and to the web sites that may show its remote control sessions.
- Checked on every call. A token only says who is calling. Remove a permission, disable an account or lock a person out, and the next call fails, not the next hour’s.
- Secrets stay put. Wi-Fi passwords and screen lock codes go in and never come back out.
- People sign in as themselves. Tools your staff run use the device code flow, with the OhrTech Portal’s own sign-in and two-factor authentication.
How permissions and limits work →
Start