canonical: https://jentic.com/apis/amazonaws.com/alexaforbusiness # AWS Alexa For Business Jentic publishes the only available OpenAPI specification for Alexa For Business, keeping it validated and agent-ready. Alexa for Business gives organisations programmatic control over Alexa devices deployed in conference rooms, hotels, and shared workspaces. The API exposes 93 operations covering rooms, profiles, devices, contacts, address books, skills, skill groups, gateways, and network profiles, plus user enrolment and meeting room management. Note that AWS deprecated the Alexa for Business service in 2023; this catalogue entry remains for legacy fleet operations and migration tooling. ## For AI agents Manage Alexa devices, conference rooms, skill groups, and contacts across an organisation through 93 administrative operations. Note: AWS has deprecated this service. ## Scope Does not handle Alexa skill development, voice model training, or consumer Alexa account management - use for organisational management of enrolled Alexa devices, rooms, and skill groups only. ## Capabilities - Provision and manage Alexa-enabled devices and assign them to rooms or shared profiles - Create address books and contacts that the device can dial through hands-free calling - Group Alexa skills and assign skill groups to specific rooms or organisational units - Configure room profiles with locale, timezone, and meeting-room preferences - Send announcements to one or many rooms and search for skill or device entities by tag - Operate gateways and network profiles for fleet-wide device connectivity ## Use cases ### Conference Room Voice Provisioning IT teams use Alexa for Business to fit out meeting rooms with voice-controlled assistants that can start meetings, dial conference bridges, and run office-specific skills. CreateRoom defines a room, AssociateDeviceWithRoom binds an Alexa device, and AssociateSkillGroupWithRoom attaches the right collection of skills. Devices in different offices can run different localisations by attaching different room profiles. Example prompt: Call CreateRoom with a name and profile, then AssociateDeviceWithRoom for the device serial, and finally AssociateSkillGroupWithRoom for the meeting-room skill group ### Hospitality Fleet Management Hotels deploying Alexa devices in guest rooms use the API to operate the fleet at scale. ListDevices and SearchDevices surface offline or unhealthy devices, while UpdateRoom and PutRoomSkillParameter let operations teams change wake words, language, or skill behaviour without touching individual devices. Network profiles applied via AssociateDeviceWithNetworkProfile let entire floors join a managed Wi-Fi network simultaneously. Example prompt: Call SearchDevices filtered by ConnectionStatus=OFFLINE and trigger a follow-up DescribeDevice for each ARN to identify the affected room and floor ### Skill Distribution Across an Organisation Enterprises that build private Alexa skills use Alexa for Business to publish them to their fleet without going through the public Skills Store. ApproveSkill makes a skill available, CreateSkillGroup bundles a set of skills, and AssociateSkillGroupWithRoom assigns the bundle to specific rooms. Updates to the skill propagate to all rooms that share the skill group on the next refresh. Example prompt: Call ApproveSkill for the new skill id, CreateSkillGroup, AssociateSkillWithSkillGroup, and AssociateSkillGroupWithRoom for the target rooms ### AI Agent Migration Tooling Because AWS announced the end-of-life of Alexa for Business, AI agents invoked through Jentic can use the API to inventory existing rooms, devices, and skill groups so administrators can migrate to a replacement voice platform. The agent searches Jentic for the list-rooms and list-devices operations, loads their schemas, and executes calls without handling SigV4 signing manually. Example prompt: Search Jentic for list alexa rooms and list alexa devices, execute both operations, and write a CSV inventory of rooms, profiles, and device serials for migration planning ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /#X-Amz-Target=AlexaForBusiness.CreateRoom | Create a meeting room and associate it with a profile | | POST | /#X-Amz-Target=AlexaForBusiness.AssociateDeviceWithRoom | Bind an Alexa device to a specific room | | POST | /#X-Amz-Target=AlexaForBusiness.AssociateSkillGroupWithRoom | Attach a skill group so it is available in a room | | POST | /#X-Amz-Target=AlexaForBusiness.SearchDevices | Search Alexa devices across the organisation by status, room, or tags | | POST | /#X-Amz-Target=AlexaForBusiness.CreateAddressBook | Create a shared address book for hands-free calling | | POST | /#X-Amz-Target=AlexaForBusiness.ApproveSkill | Approve an Alexa skill for use within the organisation | ## Key resources - **Rooms** — Create, update, and assign meeting rooms and shared spaces that hold Alexa devices - **Devices** — Register, search, and manage Alexa hardware enrolled in the organisation - **Profiles** — Define room profile defaults including locale, timezone, and address - **Skills and Skill Groups** — Approve skills and bundle them into groups assigned to rooms - **Contacts and Address Books** — Manage contact directories that devices can dial via hands-free calling - **Network Profiles** — Define and assign Wi-Fi network profiles to devices for fleet-wide connectivity - **Users** — Enrol, search, and manage user accounts with personal Alexa profiles ## Why Jentic - **Setup:** Wiring Alexa for Business by hand means signing every request with AWS Signature Version 4, resolving the a4b.{region}.amazonaws.com host, and setting the correct X-Amz-Target header across a large operation surface. Through Jentic you install once, import Alexa for Business from the API Directory, store your AWS access key and secret once, and your agent calls it. - **Permission scoping:** These operations pass room, device, and skill-group identifiers in the request body rather than the URL path, so limit the agent to the operations it needs, such as CreateRoom, AssociateDeviceWithRoom, and SearchDevices. You choose which operations it may call, so actions like ApproveSkill or associating skill groups are not included unless you add them. - **Credential handling:** Your AWS access key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a meeting room' or 'assign a skill group to a room', and Jentic returns the matching Alexa for Business operation with its input schema so the agent does not have to know the X-Amz-Target naming convention. ## Related APIs - **Amazon Managed Service for Prometheus** — Collect device telemetry from Alexa-fleet observability pipelines via Prometheus-compatible metrics - **Amazon Route 53** — Manages DNS for in-room captive portals and skill HTTPS endpoints - **Amazon API Gateway** — Often used to host private skill backends invoked by Alexa devices in the fleet ## FAQ ### Why is there no official OpenAPI spec for Alexa For Business? AWS does not publish an OpenAPI specification for Alexa for Business; the official surface is the AWS SDKs and the Smithy model. Jentic generates and maintains this spec so that AI agents and developers can call Alexa For Business via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Alexa For Business API use? Alexa for Business uses AWS Signature Version 4 (SigV4) signed with an IAM access key id and secret access key, optionally with an STS session token. Through Jentic these credentials are stored encrypted in the vault and SigV4 signing is performed server side, so the agent never handles the raw secret access key. ### Can I provision new Alexa devices using the Alexa For Business API? Yes, but only devices that have been registered to your AWS account. Use SearchDevices to locate an unassigned device by serial, then AssociateDeviceWithRoom to bind it to a room. Initial out-of-box pairing still requires the device to be claimed via the Alexa for Business setup flow. ### What are the rate limits for the Alexa For Business API? Alexa for Business applies per-region throttling on each operation, with read operations like SearchDevices and ListRooms typically throttled at a higher rate than mutating operations like CreateRoom and ApproveSkill. ThrottlingException responses should be retried with exponential backoff. ### How do I list Alexa rooms with the Alexa For Business API through Jentic? Install the SDK with pip install jentic, search Jentic for list alexa for business rooms, load the SearchRooms operation schema, and execute it with optional filters such as ProfileArn. Jentic handles SigV4 signing and returns the room metadata you can iterate over for migration or reporting. ### Is Alexa For Business still supported by AWS? AWS announced end-of-life for Alexa for Business; new customer onboarding has been closed and existing customers have been transitioned away. The API remains available for legacy fleet inventory and migration tooling, but new deployments should target a different voice platform. ### Can I limit what my agent is allowed to do with the Alexa For Business API? Yes. Because you run Jentic One yourself, your own rules decide which Alexa For Business operations the agent may call and which AWS credentials it may use. These operations pass room, device, and skill-group identifiers in the request body rather than the URL path, so you scope access at the operation level, allowing only what the agent needs, such as CreateRoom, AssociateDeviceWithRoom, and SearchDevices. Sensitive actions like ApproveSkill or associating skill groups with rooms stay out of reach unless you explicitly add them.