Getscreen.me API

Name: Getscreen.me API
Brand: Getscreen.me API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey16 EndpointsREST

For Agents

Manage Getscreen.me remote-desktop agents, mint quick-support invitations, and audit connection history through an X-Api-Key header.

Connect the Getscreen.me API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Getscreen.me API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Getscreen.me API.

List managed devices with their online state and metadata

Generate a one-time connection link to launch a remote session against a device

Send Wake-on-LAN packets and request remote reboots through the API

Create quick-support invitations for ad-hoc end-user assistance

GET STARTED

Start building with Getscreen.me API

Explore with Jentic

View OpenAPI Document

Getscreen.me is a browser-based remote desktop service used by IT operators, MSPs, and helpdesk teams to access end-user devices without installing a heavy client. The HTTP API exposes 16 endpoints covering permanent agent management, on-demand quick-support invitations, connection-history retrieval, and helper actions such as Wake-on-LAN, reboot, and merge for duplicate device entries. It is the integration surface for embedding remote-control workflows into ticketing systems, asset inventories, and ops dashboards.

Use Cases

Patterns agents use Getscreen.me API for, with concrete tasks.

★ Helpdesk one-click remote support

Tier-1 helpdesk agents resolve tickets faster by minting a quick-support invitation directly from the ticket UI rather than asking the user to install software. The API returns a connection link the operator opens in-browser, removing the install friction that slows first-response times.

Create a quick-support invitation tied to ticket 5678 and post the connection link as an internal comment

Out-of-hours device wake and patch

MSPs run patch jobs overnight by waking machines via Wake-on-LAN, opening a remote session for verification, and closing it on success. The agents/wake and agents/connect endpoints make this scriptable rather than seat-by-seat.

For each device in inventory tag 'patch-window', call /agents/wake then /agents/connect and verify the session opened

Connection-history compliance audit

Regulated teams must produce an audit trail of every remote-control session into managed endpoints. The /history/list and /history/info endpoints expose session metadata that an audit job can periodically export to immutable storage.

Pull connection history for the last 30 days and write a CSV to S3 with operator, device, and session duration

AI agent triage for IT incidents

An AI agent connected through Jentic receives an incident, looks up the affected device, and chooses between rebooting or opening a remote session based on the symptoms. Jentic injects the X-Api-Key so the agent never holds the raw credential.

Given a ticket about a frozen screen on device id 1234, call /agents/reboot and post the result back to the ticket

Key Endpoints

16 endpoints — getscreen.

METHOD

PATH

DESCRIPTION

GET

/agents/list

List managed devices

POST

/agents/connect

Generate a remote-connection link

POST

/agents/wake

Trigger Wake-on-LAN on a device

POST

/agents/reboot

Reboot a managed device

POST

/support/create

Create a quick-support invitation

GET

/history/list

List connection-session history

POST

/agents/merge

Merge duplicate agent entries

GET

/agents/list

List managed devices

POST

/agents/connect

Generate a remote-connection link

POST

/agents/wake

Trigger Wake-on-LAN on a device

POST

/agents/reboot

Reboot a managed device

POST

/support/create

Create a quick-support invitation

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Getscreen.me X-Api-Key values are stored encrypted in the Jentic vault. Agents receive a scoped reference and the raw header is built per request without entering the prompt.

Intent-based discovery

Agents search by intent such as 'open a remote support session' and Jentic returns the matching Getscreen operation along with its input schema.

Time to first call

Direct Getscreen integration: 1-2 days to wire agent management, support invitations, and history pagination. Through Jentic: under 30 minutes to search, load, and execute.

FAQs

Specific to using Getscreen.me API through Jentic.

What authentication does the Getscreen.me API use?

Getscreen.me uses an API key sent as the X-Api-Key header on every request. Through Jentic the key is stored encrypted in the vault and injected per request, so the raw header value never lands in agent context.

Can I trigger Wake-on-LAN on a managed device through the API?

Yes. POST /agents/wake takes the agent identifier and triggers a Wake-on-LAN packet. Pair it with /agents/connect to open a remote session once the device is back online for unattended maintenance windows.

What are the rate limits for the Getscreen.me API?

The OpenAPI spec does not declare hard rate limits. Practical guidance is to avoid polling /agents/list more than once a minute, cache device metadata when possible, and back off on any 429 response rather than retrying immediately.

How do I create a quick-support invitation through Jentic?

Search Jentic for 'create getscreen support invitation', load the POST /support/create schema, then execute with the operator and optional comment fields. Jentic injects the X-Api-Key automatically and returns the connection link.

Can I pull a connection-history audit log?

Yes. GET /history/list returns paged session records and GET /history/info fetches a single session's full metadata, including operator, device, and duration. This is the supported audit data source for compliance reports.

Is the Getscreen.me API free?

Getscreen.me offers a free tier with limits on managed agents and concurrent sessions; paid plans unlock higher device counts and team features. Check getscreen.me for current pricing before scaling production-grade automation.

Getscreen.me API

Connect the Getscreen.me API to your agent

Capabilities

Start building with Getscreen.me API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs