AWS IoT SiteWise

Name: AWS IoT SiteWise API
Brand: AWS IoT SiteWise
Availability: InStock

★ Only Publicly Available SpecIOTSensor Datahmac73 EndpointsREST

For Agents

Model industrial assets, ingest sensor telemetry, and query historical and aggregated property values from factory, energy, and utility equipment.

Quickstart

Get started with AWS IoT SiteWise 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:
"read latest industrial sensor reading from aws iot sitewise"

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

Capabilities

What an agent can do with AWS IoT SiteWise API.

Model industrial equipment as asset hierarchies via /asset-models and /assets endpoints

Stream property values in batch through /properties/batch/putAssetPropertyValue

Query aggregated, historical, and latest property values across asset fleets

Provision and configure SiteWise Edge gateways for on-premises OPC-UA collection

GET STARTED

Start building with AWS IoT SiteWise API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for AWS IoT SiteWise, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS IoT SiteWise, keeping it validated and agent-ready. AWS IoT SiteWise is a managed service that collects, organises, and analyses data from industrial equipment at scale. It models physical assets such as wind turbines, production lines, and chemical reactors as digital twins, ingests time-series property values from MQTT or OPC-UA gateways, and exposes the data through 73 endpoints covering assets, asset models, properties, gateways, portals, and dashboards. The service runs aggregations on the fly and supports SiteWise Monitor portals so operators can browse live and historical metrics without standing up custom dashboards.

Use Cases

Patterns agents use AWS IoT SiteWise API for, with concrete tasks.

★ Industrial Asset Modelling

Represent physical equipment such as turbines, conveyors, and compressors as structured digital assets with typed properties, hierarchies, and computed metrics. AWS IoT SiteWise stores asset models that describe the schema of equipment classes, then instantiates assets that inherit those models. Engineers can roll up child asset metrics to parent assets, enabling fleet-wide and site-wide views without custom data pipelines.

Create an asset model named WindTurbine with properties for RotorSpeed, PowerOutput, and BladePitch, then instantiate three assets bound to that model

Sensor Data Ingestion at Scale

Collect time-series telemetry from thousands of sensors using SiteWise Edge gateways, MQTT publishers, or direct API writes. The /properties/batch/putAssetPropertyValue endpoint accepts up to 10 entries per call with multiple value timestamps each, suitable for high-frequency industrial workloads. Data flows into time-series storage with built-in retention, and computed properties evaluate transforms and metrics as new values arrive.

Push a batch of 50 timestamped pressure readings from sensor S-204 into the BoilerPressure property of asset asset-9f3b

Operator Dashboards and Portals

Provide manufacturing and energy operators with live visibility into plant performance through SiteWise Monitor portals. Portals organise projects and dashboards backed by SSO, and dashboards reference asset properties directly so they update as new telemetry arrives. The /portals, /projects, and /dashboards endpoints let teams provision the entire visibility layer from infrastructure-as-code rather than the console.

Provision a SiteWise Monitor portal named 'Plant 7 Operations' with a project containing one dashboard wired to the BoilerPressure and SteamFlow properties

Historical Trend and Aggregate Analysis

Investigate equipment behaviour by querying aggregated metrics over arbitrary time windows. The /properties/batch/aggregates and /properties/batch/history endpoints return min, max, average, sum, and standard deviation across one or many assets at minute, hour, or day resolution. Reliability engineers use these queries to spot drift, schedule maintenance, and feed analytics notebooks without exporting raw data.

Fetch the hourly average of property prop-rotor-speed for asset asset-9f3b across the last 24 hours

AI Agent Industrial Operations

AI agents call AWS IoT SiteWise through Jentic to read live and historical equipment data, instantiate assets when new gear is commissioned, and surface anomalies to maintenance staff. Through Jentic, an agent searches for the right SiteWise operation by intent, loads the schema, and submits the call with credentials kept in the Jentic vault. This avoids the multi-day overhead of building bespoke SigV4 request signing into agent runtimes.

Search Jentic for 'get latest sensor reading from industrial asset', load the BatchGetAssetPropertyValue schema, and execute it for asset asset-9f3b property prop-temp

Key Endpoints

73 endpoints — jentic publishes the only available openapi specification for aws iot sitewise, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/asset-models

Create an asset model

POST

/assets

Create an asset from a model

POST

/properties/batch/putAssetPropertyValue

Ingest batched property values

POST

/properties/batch/latest

Read the latest values for many properties

POST

/properties/batch/history

Query historical property values

POST

/properties/batch/aggregates

Query aggregated metrics over time windows

POST

/portals

Create a SiteWise Monitor portal

POST

/asset-models

Create an asset model

POST

/assets

Create an asset from a model

POST

/properties/batch/putAssetPropertyValue

Ingest batched property values

POST

/properties/batch/latest

Read the latest values for many properties

POST

/properties/batch/history

Query historical property values

Why though Jentic?

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

Credential isolation

AWS access keys and session tokens for IoT SiteWise are stored encrypted in the Jentic vault. Agents receive scoped tokens at execution time and SigV4 signing is performed inside Jentic, so raw AWS secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent such as 'read latest industrial sensor value' or 'create iot asset model' and Jentic returns the matching IoT SiteWise operation along with its input schema, so the agent calls the correct endpoint without parsing AWS docs.

Time to first call

Direct AWS IoT SiteWise integration: 2-4 days to set up SigV4 signing, IAM roles, and error handling. Through Jentic: under 1 hour — search, load the schema, execute the call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS IoT Events

Detect and respond to events from IoT sensor data

Choose IoT Events when you need rule-based event detection on top of SiteWise telemetry, for example raising an alert when a turbine exceeds an operating threshold

Complementary

AWS IoT Core Data

Publish and subscribe to MQTT topics for connected devices

Use IoT Core Data when devices speak MQTT directly and you need messaging primitives rather than the asset-modelled view SiteWise provides

Complementary

AWS IoT Greengrass

Run edge compute on industrial gateways

Pick Greengrass when you need to deploy custom code or Lambda functions to the same edge gateways that SiteWise Edge runs on

Alternative

Amazon Kinesis Analytics

Streaming SQL analytics over time-series data

Choose Kinesis Analytics when you want SQL streaming queries over generic time-series rather than asset-modelled industrial telemetry

FAQs

Specific to using AWS IoT SiteWise API through Jentic.

Why is there no official OpenAPI spec for AWS IoT SiteWise?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS IoT SiteWise 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 SiteWise API use?

AWS IoT SiteWise uses AWS Signature Version 4 (SigV4) HMAC request signing. Each request must be signed with an access key, secret key, and optional session token scoped to the IoT SiteWise IAM permissions. Through Jentic, these credentials are stored encrypted in the vault and applied at execution time, so the agent never sees raw secrets.

Can I ingest time-series sensor data with the AWS IoT SiteWise API?

Yes. Use POST /properties/batch/putAssetPropertyValue to submit up to 10 entries per call, where each entry can carry multiple timestamped values. For higher throughput, deploy a SiteWise Edge gateway and configure OPC-UA or MQTT data sources, which write into the same property records via the gateway endpoints.

How do I model a piece of industrial equipment with AWS IoT SiteWise through Jentic?

Search Jentic for 'create iot sitewise asset model', load the schema for POST /asset-models, and submit the model definition with measurement, transform, and metric properties. Then call POST /assets to instantiate the asset bound to that model. Jentic handles SigV4 signing for both calls.

What are the rate limits for the AWS IoT SiteWise API?

Rate limits vary by operation and AWS Region. Asset property data writes default to 10 entries per request and ingestion quotas scale per region; read operations such as BatchGetAssetPropertyValue have separate transactions-per-second limits documented in the AWS service quotas console. Check your account's IoT SiteWise quotas before high-volume runs.

Can the AWS IoT SiteWise API run aggregations across many assets at once?

Yes. POST /properties/batch/aggregates accepts entries that span multiple asset IDs and property IDs and returns aggregate values such as average, sum, minimum, maximum, count, and standard deviation across the window you specify.

Does AWS IoT SiteWise support on-premises data collection?

Yes. SiteWise Edge gateways run on AWS IoT Greengrass and connect to OPC-UA servers and other industrial protocols at the plant. Use the /20200301/gateways endpoints to register gateways, then attach data source configurations to push values into the cloud.