AWS IoT 1-Click Devices Service
Browse all AWS APIs★ Only Publicly Available OpenAPI DocumentIOTDevice Managementhmac13 EndpointsREST
For Agents
Claim, describe, enable, disable, and unclaim AWS IoT 1-Click button-style devices and inspect the events and methods exposed by each device.
Use for: I need to claim a new batch of 1-Click devices into our account, Describe a specific device to read its model and current state, Disable a device that has been reported lost, List events from a button device within the last 24 hours
Not supported: Does not handle project workflow definitions, telemetry routing, or detector models — use for AWS IoT 1-Click device claiming and lifecycle management only.
Jentic publishes the only available OpenAPI specification for AWS IoT 1-Click Devices Service, keeping it validated and agent-ready. The IoT 1-Click Devices API manages the lifecycle of single-purpose, button-style hardware — claiming devices into an AWS account, querying their methods and events, enabling or disabling them, and unclaiming them when they are returned. With 13 operations it is the device-side counterpart to the 1-Click Projects API used to wire devices into application workflows.
Install Jentic One Beta
Connect the AWS IoT 1-Click Devices Service to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS IoT 1-Click Devices Service, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AWS IoT 1-Click Devices Service API.
Claim batches of devices into the account using a printed claim code
Initiate and finalise per-device claim flows for retail or enterprise distribution
Describe a single device to read its type, attributes, and enabled state
Enable and disable individual devices without unclaiming them
List events emitted by a device within a given time window
List the device-specific methods available for invocation
Unclaim a device when it is returned, lost, or reassigned
Use Cases
Patterns agents use AWS IoT 1-Click Devices Service API for, with concrete tasks.
★ Retail Device Onboarding
Claim batches of buttons or compatible 1-Click devices using a single claim code provided in a shipment manifest. ClaimDevicesByClaimCode imports every device in the batch into the account in one call. From there, individual devices can be enabled, disabled, or assigned to projects without further claim steps.
Call PUT /claims/{claimCode} with the printed claim code to register the entire device batch into the account
Enterprise Asset Tracking
Track which 1-Click devices are deployed where by listing devices with ListDevices and reading per-device state with DescribeDevice. Enable and disable individual devices to disable lost hardware without unclaiming it, preserving the device record. Tags can be used to associate devices with locations or owners.
Call PUT /devices/{deviceId}/state with enabled=false to disable a reported-lost device, then list-tags to verify location and owner metadata
Event-Driven Diagnostics
Inspect a device's event history with ListDeviceEvents to diagnose why a button is misbehaving. The endpoint returns time-bound events including click types and device-side errors, which can be paired with cloud-side workflow logs for end-to-end debugging without physical access.
Call GET /devices/{deviceId}/events with fromTimeStamp set to 24 hours ago and toTimeStamp now to retrieve recent click and error events
AI Agent Fleet Operations
Through Jentic, an AI agent can manage a fleet of 1-Click devices in response to support tickets — disabling lost units, listing recent events for diagnostics, and unclaiming devices that have been returned. The 13 operations are exposed as discoverable Jentic tools.
Search Jentic for 'disable aws iot 1-click device', load the UpdateDeviceState schema, and execute with deviceId and enabled=false
Key Endpoints
13 endpoints — jentic publishes the only available openapi specification for aws iot 1-click devices service, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/claims/{claimCode}
ClaimDevicesByClaimCode — claim a batch of devices by printed claim code
GET
/devices/{deviceId}
DescribeDevice — fetch a device's attributes and state
PUT
/devices/{deviceId}/finalize-claim
FinalizeDeviceClaim — finalise an individual device claim
GET
/devices/{deviceId}/methods
GetDeviceMethods — list methods on a device
PUT
/devices/{deviceId}/initiate-claim
InitiateDeviceClaim — start a per-device claim flow
GET
/devices/{deviceId}/events
ListDeviceEvents — list events emitted by a device
PUT
/devices/{deviceId}/state
UpdateDeviceState — enable or disable a device
DELETE
/devices/{deviceId}
UnclaimDevice — remove a device from the account
PUT
/claims/{claimCode}
ClaimDevicesByClaimCode — claim a batch of devices by printed claim code
GET
/devices/{deviceId}
DescribeDevice — fetch a device's attributes and state
PUT
/devices/{deviceId}/finalize-claim
FinalizeDeviceClaim — finalise an individual device claim
GET
/devices/{deviceId}/methods
GetDeviceMethods — list methods on a device
PUT
/devices/{deviceId}/initiate-claim
InitiateDeviceClaim — start a per-device claim flow
GET
/devices/{deviceId}/events
ListDeviceEvents — list events emitted by a device
PUT
/devices/{deviceId}/state
UpdateDeviceState — enable or disable a device
DELETE
/devices/{deviceId}
UnclaimDevice — remove a device from the account
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys for IoT 1-Click Devices are stored encrypted in the Jentic vault. Agents never see the raw credentials — Jentic signs each request with SigV4 server-side.
Intent-based discovery
Agents search Jentic with intents like 'claim aws iot 1-click device' or 'disable button' and get back the matching operation with its input schema.
Time to first call
Direct integration: half a day to wire up the AWS SDK and IAM policies. Through Jentic: under 30 minutes.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS IoT 1-Click Devices Service API through Jentic.
Why is there no official OpenAPI spec for AWS IoT 1-Click Devices Service?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS IoT 1-Click Devices Service 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 AWS IoT 1-Click Devices Service API use?
The API uses AWS Signature Version 4 (HMAC) request signing with an AWS access key ID and secret access key. Through Jentic, AWS credentials are stored encrypted in the vault and the agent never holds raw access keys.
Can I claim devices in bulk with the IoT 1-Click Devices API?
Yes. Call PUT /claims/{claimCode} with a claim code that ships with a batch of devices and every device in that batch is added to the account in a single operation. To claim individual devices, use InitiateDeviceClaim followed by FinalizeDeviceClaim.
What are the rate limits for the AWS IoT 1-Click Devices Service API?
AWS applies per-account, per-region request quotas to IoT 1-Click operations and these vary by call. List and describe operations have higher quotas than claim and unclaim operations. Check AWS Service Quotas for current limits.
How do I disable a lost device through Jentic?
Search Jentic for 'disable aws iot 1-click device', load the UpdateDeviceState schema, and execute with the deviceId and enabled=false. The device record is preserved so it can be re-enabled if it is later recovered.
Has AWS IoT 1-Click been deprecated?
AWS announced the end of life of IoT 1-Click in 2025. The API may still be reachable for existing accounts but new device claims may be restricted. Check AWS announcements before building new integrations against this service.
GET STARTED