Overview
Client-mode REST API connector for IFS Cloud OData v4 projections (Shop Orders, Equipment, Work Orders).BASE_ADDRESS defaults to https://YOUR_IFS_HOST/main/ifsapplications/projection/v1. Auth: OAuth 2.0 (IFS IAM) Bearer. Pass secrets only at runtime via MQTT JSON placeholders or Hub GET SECRET — never commit real credentials.
Auth
OAuth 2.0 (IFS IAM) Bearer. Prefer Hub secrets /GET SECRET. Never hard-code tokens into the .lot.
Basic Syntax
MQTT topics
Request topics underintegrations/ifs-cloud/request/...; responses on integrations/ifs-cloud/response/....
Template reference
Generated from the shipped broker templateifs-cloud (-routeCode IFS_CLOUD). It lists every event the template defines.
Auth
OAuth 2.0 (IFS IAM) Bearer Auth headers used by the template:Authorization: Bearer {value.json.access_token}.
Template parameters
BASE_ADDRESS default: https://YOUR_IFS_HOST/main/ifsapplications/projection/v1.
Events
Deploy
Get the template card (JSON withtemplate and metadata) from the broker, then deploy the connector:
BASE_ADDRESS already filled in:
-addRoute (do not include ADD METADATA).
Usage example
CallListshoporders by publishing a JSON payload to its request topic, and read the reply on the response topic:

