AWS IoT 1-Click Projects Service

Name: AWS IoT 1-Click Projects Service API
Brand: AWS IoT 1-Click Projects Service
Availability: InStock

★ Only Publicly Available SpecIOTDevice Managementhmac16 EndpointsREST

For Agents

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

Quickstart

Get started with AWS IoT 1-Click Projects Service 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:
"create an aws iot 1-click project"

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

Capabilities

What an agent can do with AWS IoT 1-Click Projects Service API.

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

GET STARTED

Start building with AWS IoT 1-Click Projects Service API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for AWS IoT 1-Click Projects Service, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use AWS IoT 1-Click Projects Service API for, with concrete tasks.

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

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.

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.

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.

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

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for aws iot 1-click projects service, keeping it validated and agent-ready.

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

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

Why though Jentic?

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

Credential isolation

AWS access keys for IoT 1-Click Projects 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 'create iot 1-click project' or 'associate device with placement' 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 project/placement modelling. Through Jentic: under 30 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS IoT 1-Click Devices Service

Manages the device records that 1-Click Projects associates with placements

Use 1-Click Devices to claim and manage hardware records; use 1-Click Projects to bind those devices to workflows.

Complementary

AWS IoT Events

Detector models that consume button-press events emitted by placements

Use IoT Events to drive state-machine logic from button presses; use 1-Click Projects to model the placements that emit those presses.

Complementary

AWS Lambda

Lambda functions are the typical handler invoked when a button press occurs in a placement

Use Lambda to process button-press events with placement context; use 1-Click Projects to define those placements.

FAQs

Specific to using AWS IoT 1-Click Projects Service API through Jentic.

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

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.