Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions doc/api.md
Original file line number Diff line number Diff line change
Expand Up @@ -257,6 +257,9 @@ Additionally for commands (which are attributes of type `command`) the following
particular IOTAs documentation for allowed values of this field in each case.
- **contentType**: `content-type` header used when send command by HTTP transport (ignored in other kinds of
transports)
- **headers**: extra customer headers used when send command by HTTP transport (ignored in other kinds of

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should explain that the value of this field is a map which keys are header names and values are jexl expressions? In addition, maybe an example could help.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 14dc6b0

transports)
Check full detail of these fields in [comand-transformations](https://github.com/telefonicaid/iotagent-json/blob/master/docs/usermanual.md#commands-transformations)

Note that, when information coming from devices, this means measures, are not defined neither in the group, nor in the
device, the IoT agent will store that information into the destination entity using the same attribute name than the
Expand Down