canonical: https://jentic.com/apis/teamviewer.com/teamviewer

# TeamViewer Web API

TeamViewer Web API - OpenAPI Specification. The API exposes 259 endpoints secured with apiKey authentication.

## For AI agents

Programmatically creates a new account, returns the account. Covers 259 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Creates a new account
- Returns the account
- Updates the account
- Create or update account IoT preferences
- Get the account IoT preferences
- Delete the account IoT preferences

## Use cases

### Developer Tools Operations

Use the TeamViewer Web API to perform developer tools operations programmatically. The API provides 259 endpoints covering core functionality including creates a new account, returns the account, updates the account.

Example prompt: Call POST `/api/v1/account` to creates a new account

### Automated Account Management Management

Automate account management operations by combining multiple TeamViewer Web API endpoints. Agents can returns the account and then updates the account in a single workflow.

Example prompt: Call GET `/api/v1/account` to returns the account, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TeamViewer Web API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'creates a new account', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/account` | Creates a new account |
| GET | `/api/v1/account` | Returns the account |
| PUT | `/api/v1/account` | Updates the account |
| GET | `/api/v1/account/TenantIds` | Returns the account's tenants |
| POST | `/api/v1/account/iot/preferences` | Create or update account IoT preferences |
| GET | `/api/v1/account/iot/preferences` | Get the account IoT preferences |
| DELETE | `/api/v1/account/iot/preferences` | Delete the account IoT preferences |
| GET | `/api/v1/account/licenses/iot` | Returns the account's IoT license information |

## Key resources

- **Account Management** — Operations related to Account Management
- **Chat** — Operations related to Chat
- **Company Address Book** — Operations related to Company Address Book
- **Company Management** — Operations related to Company Management
- **Computers & Contacts** — Operations related to Computers & Contacts

## Why Jentic

- **Setup:** Wiring the TeamViewer Web API by hand means registering its API token, attaching that header to every call against webapi.teamviewer.com, and building the paging and retry handling across its many account endpoints yourself. Through Jentic you install once, import the TeamViewer Web API from the API Directory, store the API token once, and your agent calls it.
- **Permission scoping:** The TeamViewer Web API works against your account, so limit the agent to the operations it needs, such as reading account details or IoT preferences. You choose that allowed set, so write and delete operations like updating the account or removing IoT preferences are not included unless you add them.
- **Credential handling:** Your TeamViewer API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get account details' or 'read IoT preferences', and Jentic returns the matching TeamViewer Web API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the TeamViewer Web API use?

The TeamViewer Web API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I creates a new account with the TeamViewer Web API?

Yes. Use the POST `/api/v1/account` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the TeamViewer Web API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I creates a new account through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates a new account'. Jentic returns the matching TeamViewer Web API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TeamViewer Web API have?

The TeamViewer Web API exposes 259 endpoints covering account management, chat, company address book operations.

### Can I limit what my agent is allowed to do with the TeamViewer Web API?

Yes. Jentic One is self-hosted, so you define the rules that decide which TeamViewer Web API operations and credentials your agent may use. You can allow only the read operations it needs, such as GET `/api/v1/account` to return account details or GET `/api/v1/account/iot/preferences` to read IoT preferences, while excluding write and delete operations like PUT `/api/v1/account` or DELETE `/api/v1/account/iot/preferences` unless you add them. Because the API acts against your own account, the agent can call only the endpoints you have permitted.