Retrieve a specific thing
Returns the thing identified by the thingId path parameter. The response includes details about the thing,
including the policyId, attributes, definition and features.
Optionally, you can use the field selectors (see parameter fields) to only get specific fields,
which you are interested in.
Example:
Use the field selector _policy to retrieve the content of the policy.
Parameters
thingIdstringrequiredpathThe ID of a thing needs to follow the namespaced entity ID notation (see Ditto documentation on namespaced entity IDs).
fieldsstringqueryContains a comma-separated list of fields to be included in the returned JSON. attributes can be selected in the same manner.
Selectable fields
thingIdpolicyIddefinitionattributesSupports selecting arbitrary sub-fields by using a comma-separated list:
several attribute paths can be passed as a comma-separated list of JSON pointers (RFC-6901)
For example:
?fields=attributes/modelwould select onlymodelattribute value (if present)?fields=attributes/model,attributes/locationwould select onlymodelandlocationattribute values (if present)
Supports selecting arbitrary sub-fields of objects by wrapping sub-fields inside parentheses
( ):a comma-separated list of sub-fields (a sub-field is a JSON pointer (RFC-6901) separated with
/) to selectsub-selectors can be used to request only specific sub-fields by placing expressions in parentheses
( )after a selected subfieldFor example:
?fields=attributes(model,location)would select onlymodelandlocationattribute values (if present)?fields=attributes(coffeemaker/serialno)would select theserialnovalue inside thecoffeemakerobject?fields=attributes/address/postal(city,street)would select thecityandstreetvalues inside thepostalobject inside theaddressobject
featuresSupports selecting arbitrary fields in features similar to
attributes(see also features documentation for more details)_namespaceSpecifically selects the namespace also contained in the
thingId_revisionSpecifically selects the revision of the thing. The revision is a counter, which is incremented on each modification of a thing.
_createdSpecifically selects the created timestamp of the thing in ISO-8601 UTC format. The timestamp is set on creation of a thing.
_modifiedSpecifically selects the modified timestamp of the thing in ISO-8601 UTC format. The timestamp is set on each modification of a thing.
_metadataSpecifically selects the Metadata of the thing. The content is a JSON object having the Thing's JSON structure with the difference that the JSON leaves of the Thing are JSON objects containing the metadata.
_policySpecifically selects the content of the policy associated to the thing. (By default, only the policyId is returned.)
Examples
?fields=thingId,attributes,features?fields=attributes(model,manufacturer),features
If-MatchstringheaderThe If-Match header, which has to conform to RFC-7232 (Conditional Requests). Common usages are:
- optimistic locking by specifying the
ETagfrom a previous GET response, e.g.If-Match: "rev:4711" - retrieving or modifying a resource only if it already exists, e.g.
If-Match: *
If-None-MatchstringheaderThe If-None-Match header, which has to conform to RFC-7232 (Conditional Requests). A common usage scenario is to modify a resource only if it does not yet exist, thus to create it, by specifying If-None-Match: *.
get-metadatastringheaderThe get-metadata header, which retrieves Metadata of the Thing.
timeoutstringqueryDefines how long the backend should wait for completion of the request, e.g. applied when waiting for requested
acknowledgements via the requested-acks param. Can be specified without unit (then seconds are assumed) or
together with s, ms or m unit. Example: 42s, 1m.
The default (if omitted) and maximum timeout is 60s. A value of 0 applies fire and forget semantics for
the command resulting in setting response-required=false.
conditionstringqueryDefines that the request should only be processed if the given condition is met. The condition can be specified using RQL syntax.
Examples
E.g. if the temperature is not 23.9 update it to 23.9:
PUT /api/2/things/{thingId}/features/temperature/properties/value?condition=ne(features/temperature/properties/value,23.9)body: 23.9
Further example conditions:
?condition=eq(features/temperature/properties/unit,"Celsius")?condition=ge(features/temperature/properties/lastModified,"2021-08-22T19:45:00Z")?condition=gt(_modified,"2021-08-05T12:17:00Z")?condition=exists(features/temperature/properties/value)?condition=empty(features/temperature/properties/value)?condition=and(gt(features/temperature/properties/value,18.5),lt(features/temperature/properties/value,25.2))?condition=or(gt(features/temperature/properties/value,18.5),not(exists(features/temperature/properties/value))
channelstringtwinlivequeryDefines to which channel to route the command: twin (digital twin) or live (the device).
- If setting the channel parameter is omitted, the
twinchannel is set by default and the command is routed to the persisted representation of a thing in Eclipse Ditto. - When using the
livechannel, the command/message is sent towards the device.
The option live is not available when a new thing should be created, only for updating an
existing thing.
live-channel-conditionstringqueryDefines that the request should fetch thing data via live channel if the given condition is met. The condition can be specified using RQL syntax.
Examples
?live-channel-condition=lt(_modified,"2021-12-24T12:23:42Z")?live-channel-condition=ge(features/ConnectionStatus/properties/status/readyUntil,time:now)
live-channel-timeout-strategyanyfailuse-twinqueryDefines a strategy how to handle timeouts of a live response to a request sent via channel=live or with a matching live-channel-condition.
Response
The request successfully returned the specific thing.
The (sub-)resource has not been modified. This happens when you specified a If-None-Match header which matches the current ETag of the (sub-)resource.
The request could not be completed. Possible reasons:
- the
thingIddoes not conform to the namespaced entity ID notation (see Ditto documentation on namespaced entity IDs) - at least one of the defined query parameters is invalid
The request could not be completed due to missing authentication.
The request could not be completed. The thing with the given ID was not found.
A precondition for reading or writing the (sub-)resource failed. This will happen for write requests, if you specified an If-Match or If-None-Match header, which fails the precondition check against the current ETag of the (sub-)resource. For read requests, this error may only happen for a failing If-Match header. In case of a failing If-None-Match header for a read request, status 304 will be returned instead.
Authorization
OpenIDConnectopenIdConnectOpenID Connect Discovery URL. The placeholder is replaced by Swagger UI when configured.
NginxBasichttp (basic)Eclipse Ditto sandbox demo user (demo1 ... demo9) + password (demo)
Bearerhttp (bearer)A JSON Web Token issued by a supported OAuth 2.0 Identity Provider.