Amazon IoT Core · Schema
DescribeThingResponse
The output from the DescribeThing operation.
Device ManagementIoTMQTTMessage Routing
Properties
| Name | Type | Description |
|---|---|---|
| defaultClientId | object | |
| thingName | object | |
| thingId | object | |
| thingArn | object | |
| thingTypeName | object | |
| attributes | object | |
| version | object | |
| billingGroupName | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/amazon-iot-core/refs/heads/main/json-schema/iot-core-describe-thing-response-schema.json",
"title": "DescribeThingResponse",
"description": "The output from the DescribeThing operation.",
"type": "object",
"properties": {
"defaultClientId": {
"allOf": [
{
"$ref": "#/components/schemas/ClientId"
},
{
"description": "<p>The default MQTT client ID. For a typical device, the thing name is also used as the default MQTT client ID. Although we don\u2019t require a mapping between a thing's registry name and its use of MQTT client IDs, certificates, or shadow state, we recommend that you choose a thing name and use it as the MQTT client ID for the registry and the Device Shadow service.</p> <p>This lets you better organize your IoT fleet without removing the flexibility of the underlying device certificate model or shadows.</p>"
}
]
},
"thingName": {
"allOf": [
{
"$ref": "#/components/schemas/ThingName"
},
{
"description": "The name of the thing."
}
]
},
"thingId": {
"allOf": [
{
"$ref": "#/components/schemas/ThingId"
},
{
"description": "The ID of the thing to describe."
}
]
},
"thingArn": {
"allOf": [
{
"$ref": "#/components/schemas/ThingArn"
},
{
"description": "The ARN of the thing to describe."
}
]
},
"thingTypeName": {
"allOf": [
{
"$ref": "#/components/schemas/ThingTypeName"
},
{
"description": "The thing type name."
}
]
},
"attributes": {
"allOf": [
{
"$ref": "#/components/schemas/Attributes"
},
{
"description": "The thing attributes."
}
]
},
"version": {
"allOf": [
{
"$ref": "#/components/schemas/Version"
},
{
"description": "<p>The current version of the thing record in the registry.</p> <note> <p>To avoid unintentional changes to the information in the registry, you can pass the version information in the <code>expectedVersion</code> parameter of the <code>UpdateThing</code> and <code>DeleteThing</code> calls.</p> </note>"
}
]
},
"billingGroupName": {
"allOf": [
{
"$ref": "#/components/schemas/BillingGroupName"
},
{
"description": "The name of the billing group the thing belongs to."
}
]
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/iot-core-describe-thing-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.