canonical: https://jentic.com/apis/amazonaws.com/aws-iot1click-projects

# AWS IoT 1-Click Projects Service

Jentic publishes the only available OpenAPI specification for AWS IoT 1-Click Projects Service, keeping it validated and agent-ready. The IoT 1-Click Projects API defines projects and placements that map physical 1-Click devices to specific business workflows - for example, a button at a hotel front desk that triggers a housekeeping request. The API manages projects, placements, device template associations, and per-placement attributes across 16 operations and is the application-side counterpart to the 1-Click Devices API.

## For AI agents

Define IoT 1-Click projects, placements, and device template associations to bind physical button devices to specific application workflows and per-placement context.

## Scope

Does not handle device claiming, click-event delivery, or downstream Lambda execution - use for IoT 1-Click project and placement modelling only.

## Capabilities

- Create projects with placement and device templates that define the workflow
- Create, update, and delete placements within a project
- Associate and disassociate devices with specific placement and template slots
- Update project description, placement template, and per-project tags
- List projects, placements within a project, and devices in a placement
- Retrieve attributes attached to a placement for routing decisions
- Tag projects and placements for ownership and reporting

## Use cases

### Hospitality Service Buttons

Run a hotel-wide service request system on 1-Click buttons. A project models the 'housekeeping request' workflow, each room is a placement with attributes such as floor and room number, and a claimed button device is associated with each placement. Button presses become AWS Lambda invocations enriched with placement context.

Example prompt: Call POST /projects to create a 'housekeeping' project with a placement template, then PUT /projects/{projectName}/placements/{placementName} to add a placement for room 412

### Retail Restock Notifications

Use 1-Click projects to model a retail restock workflow where each shelf or zone has its own placement and dedicated button. Per-placement attributes carry the SKU and reorder threshold, so the downstream Lambda routes notifications to the correct supplier without hard-coded mappings.

Example prompt: Call PUT /projects/restock/placements/aisle-7 with attributes={"sku":"BEV-COLA-12","threshold":"10"} and a deviceTemplateName referencing the restock button template

### Field Operations Workflow Binding

Bind buttons distributed to field engineers or contractors to per-engineer placements so their click events carry name, role, and team metadata into downstream automation. AssociateDeviceWithPlacement attaches the claimed hardware to a placement slot defined by the device template.

Example prompt: Call PUT /projects/field-ops/placements/engineer-jane/devices/dispatch-button with the deviceId of a claimed 1-Click device

### AI Agent Placement Operations

Through Jentic, an AI agent can reconcile a fleet of 1-Click placements with an external system of record - creating placements as new rooms or zones come online, updating attributes when ownership changes, and disassociating devices when buttons are returned. The 16 operations are exposed as discoverable Jentic tools.

Example prompt: Search Jentic for 'update aws iot 1-click placement', load the UpdatePlacement schema, and execute it with projectName, placementName, and updated attributes

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /projects | CreateProject - create a new 1-Click project |
| GET | /projects | ListProjects - list projects in the account |
| GET | /projects/{projectName} | DescribeProject - fetch project configuration |
| PUT | /projects/{projectName}/placements/{placementName} | CreatePlacement - create a placement in a project |
| GET | /projects/{projectName}/placements | ListPlacements - list placements in a project |
| GET | /projects/{projectName}/placements/{placementName} | DescribePlacement - fetch placement attributes |
| PUT | /projects/{projectName}/placements/{placementName}/devices/{deviceTemplateName} | AssociateDeviceWithPlacement - bind a device to a placement slot |
| GET | /projects/{projectName}/placements/{placementName}/devices | GetDevicesInPlacement - list devices associated with a placement |

## Key resources

- **Project** — Top-level container that defines the placement template and project tags
- **Placement** — Specific instance within a project carrying attributes and device associations
- **DeviceTemplate** — Slot definition that names a device role within each placement

## Why Jentic

- **Setup:** Wiring the IoT 1-Click Projects API by hand means building AWS Signature Version 4 signing, resolving the projects.iot1click.amazonaws.com host, and handling AWS throttling and retries yourself. Through Jentic you install once, import AWS IoT 1-Click Projects from the API Directory, store the AWS access key and secret once, and your agent calls it.
- **Permission scoping:** IoT 1-Click Projects puts the project and placement names in the URL path (/projects/{projectName}/placements/{placementName}/...), so a rule can pin your agent to one project: it can read and list placements there and nothing else. You choose the operations it may call, so destructive ones like DeletePlacement or DisassociateDeviceFromPlacement are not included unless you add them.
- **Credential handling:** Your AWS access key and secret for IoT 1-Click Projects are stored once, encrypted, by your own Jentic One instance and signed with SigV4 at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an iot 1-click project' or 'associate a device with a placement', and Jentic returns the matching IoT 1-Click Projects operation with its input schema so the agent calls the right endpoint without reading the AWS reference.

## Related APIs

- **AWS IoT 1-Click Devices Service** — Manages the device records that 1-Click Projects associates with placements
- **AWS IoT Events** — Detector models that consume button-press events emitted by placements
- **AWS Lambda** — Lambda functions are the typical handler invoked when a button press occurs in a placement

## FAQ

### Why is there no official OpenAPI spec for AWS IoT 1-Click Projects 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 Projects Service 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 AWS IoT 1-Click Projects 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 signed requests are issued server-side.

### Can I associate a device with a placement with the IoT 1-Click Projects API?

Yes. Call PUT /projects/{projectName}/placements/{placementName}/devices/{deviceTemplateName} with the deviceId of a device claimed via the IoT 1-Click Devices API. The device template name corresponds to a slot defined in the project's placement template.

### What are the rate limits for the AWS IoT 1-Click Projects Service API?

AWS applies per-account, per-region request quotas to IoT 1-Click Projects operations and these vary by call. List and describe operations have higher quotas than create and update operations. Check AWS Service Quotas for current limits.

### How do I create a new placement through Jentic?

Search Jentic for 'create aws iot 1-click placement', load the CreatePlacement schema, and execute with projectName, placementName, and an attributes map. The placement appears immediately in ListPlacements and is ready to associate with a device.

### Has AWS IoT 1-Click been deprecated?

AWS announced end of life for IoT 1-Click in 2025. Existing projects may continue to function but creation of new projects may be restricted. Check current AWS announcements before building new integrations against this service.

### Can I limit what my agent is allowed to do with the AWS IoT 1-Click Projects API?

Yes. Because you run Jentic One yourself, your own rules decide which of the 16 operations the agent may call and which AWS credentials it may use. Since the project and placement names sit in the URL path, such as /projects/{projectName}/placements/{placementName}, you can pin the agent to a single project so it only reads and lists placements there. Destructive operations like DeletePlacement and DisassociateDeviceFromPlacement are excluded unless you explicitly add them.