TeamViewer API

This connector reads a TeamViewer account through the Web API (webapi.teamviewer.com/api/v1): the token's account, the devices and contacts in its Computers & Contacts list, groups and service-queue sessions. All six tools only read: they cannot start a remote connection, create a session or change a device.

Getting credentials

1. The Web API needs a Business, Premium, Corporate or Tensor plan.
2. Sign in to the TeamViewer Management Console, click your profile avatar, open Edit profile → Apps & Tokens and choose Create app or token to create a script token.
3. Tick only the read permissions this connector needs: account information, Computers & Contacts, group management and session management.
4. Paste the token into TEAMVIEWER_API_TOKEN. It is sent as Authorization: Bearer <token>. A 401 invalid_token means the token is wrong or was deleted; a permission error on one tool means the token lacks that area.

Scope follows the token's user: devices, contacts and groups are those visible to the user who created the token, not necessarily the whole company.

IDs: TeamViewer prefixes its IDs. teamviewer_get_device takes the device_id from teamviewer_list_devices (starts with d), not the TeamViewer ID that users read on screen (remotecontrol_id, starts with r, or the numeric teamviewer_id). Group IDs start with g, contact IDs with c. To find a device by name, list devices and match on alias.

Devices: online_state filters by online or offline; leave it empty for all. Each device carries alias, groupid, description, online_state, last_seen and assigned_to.

Sessions are service-queue cases (session codes such as s12-345-678) with state, assigned_userid, created_at and end_customer, not a log of past connections. The API returns them in pages (next_offset, sessions_remaining); this tool only reads the first page.

Cloud reachability: webapi.teamviewer.com is public over HTTPS. If you get a 429, wait before retrying.