Alexa For Business

Name: Alexa For Business API
Brand: Alexa For Business
Availability: InStock

★ Only Publicly Available SpecIOTDevice ManagementapiKey93 EndpointsREST

For Agents

Manage Alexa devices, conference rooms, skill groups, and contacts across an organisation through 93 administrative operations. Note: AWS has deprecated this service.

Quickstart

Get started with Alexa For Business in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list alexa for business rooms"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Alexa For Business API.

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

GET STARTED

Start building with Alexa For Business API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Alexa For Business, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Alexa For Business API for, with concrete tasks.

★ 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.

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.

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.

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.

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

93 endpoints — jentic publishes the only available openapi specification for alexa for business, keeping it validated and agent-ready.

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

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

Why though Jentic?

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

Credential isolation

AWS access key id and secret access key for Alexa for Business are stored encrypted in the Jentic vault. Jentic performs SigV4 signing server side and supports STS temporary credentials, so the agent never sees the raw secret access key.

Intent-based discovery

Agents search Jentic with phrases like list alexa rooms or assign skill group to 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.

Time to first call

Direct integration: 3 to 5 days including SigV4 signing, IAM scoping, and the wide surface area of room, profile, skill, and device resources. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amazon Managed Service for Prometheus

Collect device telemetry from Alexa-fleet observability pipelines via Prometheus-compatible metrics

Use Amazon Managed Prometheus alongside Alexa for Business when the agent needs to record connectivity or skill-usage metrics emitted by fleet operations.

Complementary

Amazon Route 53

Manages DNS for in-room captive portals and skill HTTPS endpoints

Use Route 53 alongside Alexa for Business when the agent provisions custom skill endpoints that the fleet must reach by domain name.

Alternative

Amazon API Gateway

Often used to host private skill backends invoked by Alexa devices in the fleet

Choose API Gateway when the work is hosting the skill HTTPS backend rather than managing the Alexa devices themselves.

FAQs

Specific to using Alexa For Business API through Jentic.

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 at https://app.jentic.com/sign-up.

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.