canonical: https://jentic.com/apis/discvision.de/discvision

# Discvision De DiscVision Internal REST API for Hotel

The DiscVision Internal REST API for Hotel runs an in-room voice-assistant hospitality platform built on Alexa for Hospitality. It provisions and configures the voice endpoints in each room, covering wake word, locale, timezone, maximum volume, do-not-disturb, Wi-Fi, and enabled skills, and it organises the property hierarchy of properties, room types, and rooms with per-level settings. On top of the devices it manages guest services such as meal plans, orders, food restrictions, reminders, and proactive campaigns, and it handles communication address books, inbound calls, room notifications, questionnaires, media libraries, and group, role, and user administration.

## For AI agents

Provision and configure in-room Alexa voice endpoints, organise properties, room types, and rooms, and manage meal plans, notifications, and guest services. Administers groups, roles, and users across 212 endpoints.

## Scope

Does not process payments, handle reservations and PMS billing, or run a booking engine. Use for managing in-room voice devices and hotel guest-experience services only.

## Capabilities

- Provision and configure in-room voice endpoints: wake word, locale, timezone, max volume, do-not-disturb, and connectivity status
- Manage each endpoint's Wi-Fi networks and enable or remove Alexa skills on a unit
- Organise the property hierarchy of properties, room types, and rooms with per-level settings
- Build meal plans with meals, options, orders, and food restrictions and export order statistics
- Send room and room-type notifications and run proactive campaigns
- Maintain communication address books, contacts, and inbound-call activation per unit
- Administer groups, roles, invitations, and per-unit admin and experience-admin rights for users

## Use cases

### An Agent Configuring In-Room Devices

An AI agent connected to DiscVision through Jentic can set up and adjust a room's voice endpoint without a technician: set the wake word, locale, timezone, and maximum volume, toggle do-not-disturb, connect Wi-Fi, and check connectivity status. Because each endpoint is addressed by its own id, the agent configures exactly one device at a time across a property.

Example prompt: Set the wake word and locale for one endpoint, connect its Wi-Fi network, and read its connectivity status to confirm it is online

### Meal Planning and Ordering

DiscVision manages the dining side of a stay: define meals and meal options, build a meal plan for a room type, capture meal orders and food restrictions per room, and export the orders and option counts for the kitchen. This lets a property run room-level dining from the same platform that drives the in-room devices.

Example prompt: Create a meal plan for a room type, add meal options, and export the current meal orders for the kitchen

### Guest Notifications and Proactive Campaigns

Properties can reach guests through their in-room devices by sending a notification to a single room or broadcasting to a room type, and by scheduling proactive campaigns. This turns the device fleet into a messaging channel for service updates and promotions without a separate system.

Example prompt: Send a notification to one room, then create a proactive campaign for a room type

### Property and Role Administration

DiscVision organises hotels as properties containing room types and rooms, each with its own settings, and it administers who can do what: groups, invitations, roles, and per-unit admin and experience-admin rights for users. An operator can stand up a property, place its rooms, and grant staff the access they need.

Example prompt: Add a property, create its room types and rooms, and grant a staff user admin rights for a unit

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/endpoints` | Get the list of voice endpoints |
| PUT | `/endpoints/{endpointId}/wakeWord` | Set the wake word of an endpoint |
| POST | `/wifi` | Set the Wi-Fi for an endpoint |
| POST | `/skills/{skillId}/enablements` | Enable an Alexa skill on a unit |
| GET | `/rooms` | Get the room list |
| PUT | `/mealplan` | Add or update a meal plan |
| POST | `/notification` | Send a notification to a room |
| GET | `/properties` | Get the property list |

## Key resources

- **Endpoints** — Provision and configure in-room voice devices, their Wi-Fi, and enabled skills
- **Properties** — Manage properties, room types, rooms, and their per-level settings
- **Meals** — Define meals, options, meal plans, orders, food restrictions, and order exports
- **Communication** — Manage address books, contacts, inbound calls, and room notifications
- **Guest Services** — Run proactive campaigns, reminders, questionnaires, radio, and media libraries
- **Users & Groups** — Administer groups, invitations, roles, and per-unit admin rights

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 42 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 53 / 100
  - Developer Experience & Jentic Compatibility: 73 / 100
  - AI-Readiness & Agent Experience: 24 / 100
  - Agent Usability: 43 / 100
  - Security: 90 / 100
  - AI Discoverability: 39 / 100
- **View full report:** https://jentic.com/apis/discvision.de/discvision/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring DiscVision by hand means running its OAuth 2.0 authorization-code flow through Amazon login, managing the Alexa enterprise and Wi-Fi management scopes, and keeping tokens fresh across a large surface. Through Jentic you install once, import DiscVision from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** DiscVision keys most operations to a property, room, or endpoint id in the URL path (`/properties/{propertyId}`, `/endpoints/{endpointId}`, `/rooms/{roomId}`), so a rule can pin your agent to one property or a single endpoint and the operations you pick. It can read and configure device settings for that scope while property deletion, role grants, and user admin changes stay out of reach unless you add them.
- **Credential handling:** Your DiscVision OAuth 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 'configure an in-room device' or 'send a notification to a room', and Jentic returns the matching DiscVision operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Particle API** — General IoT device provisioning and fleet management, versus DiscVision's hospitality-specific voice endpoints.
- **ecobee API** — Connected thermostats and sensors for rooms, versus DiscVision's voice-assistant and guest-services platform.
- **Cloudbeds API** — Hotel property management and reservations, complementing DiscVision's in-room device and guest-services layer.
- **apaleo API** — Property management system for hotels, complementing DiscVision's device and meal-planning operations.

## FAQ

### Is there a DiscVision MCP server?

You don't need an MCP server to give your agent DiscVision. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the endpoint-configuration, property, meal, and notification operations. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.

### Can I limit what my agent is allowed to do with DiscVision?

Yes. Write a rule that allows the endpoint configuration and room read operations for one property id but not property deletion, role assignment, or granting unit admin rights, so the agent can manage devices and rooms while account administration stays with you, and every call it makes is logged.

### What authentication does the DiscVision API use?

Per its OpenAPI spec, the DiscVision API uses OAuth 2.0 with the authorization-code flow through Amazon login, reflecting its Alexa for Hospitality basis, and requests the Alexa enterprise management, Wi-Fi management, and user profile scopes. Through Jentic the resulting token is stored encrypted by your own Jentic One instance and injected only at call time.

### Can I configure in-room voice devices with the DiscVision API?

Yes. Each endpoint is addressed by its id, and dedicated operations set its wake word, locale, timezone, maximum volume, do-not-disturb state, and distance and temperature units, connect or forget Wi-Fi networks, and report connectivity status. Skills can be enabled on or removed from a unit as well.

### What are the rate limits for the DiscVision API?

The OpenAPI spec does not specify rate limits, and this spec is published through a third-party aggregator rather than by DiscVision directly. Check discvision.de for current limits and the production base URL before relying on the development server listed in the spec.

### How do I set up an in-room device with the DiscVision API through Jentic?

Read the property's endpoints, then set the wake word, locale, and Wi-Fi for the target endpoint and confirm its connectivity status. In Jentic, search for 'configure an in-room voice device', store your credential once, and the agent runs the sequence. To run it on your own infrastructure, install Jentic One from its GitHub repo.