Overview
Client-mode REST API connector for Infor CloudSuite M3/CSI via ION API Gateway.BASE_ADDRESS defaults to https://mingle-ionapi.YOUR_REGION.inforcloudsuite.com/YOUR_TENANT. Auth: OAuth 2.0 Bearer (.ionapi service account or auth code). Pass secrets only at runtime via MQTT JSON placeholders or Hub GET SECRET — never commit real credentials.
Auth
OAuth 2.0 Bearer (.ionapi service account or auth code). Prefer Hub secrets /GET SECRET. Never hard-code tokens into the .lot.
Basic Syntax
MQTT topics
Request topics underintegrations/infor-cloudsuite-via-ion-api-gateway/request/...; responses on integrations/infor-cloudsuite-via-ion-api-gateway/response/....
Template reference
Generated from the shipped broker templateinfor-cloudsuite-via-ion-api-gateway (-routeCode INFOR_CLOUDSUITE_VIA_ION_API_GATEWAY). It lists every event the template defines.
Auth
OAuth 2.0 Bearer (.ionapi service account or auth code) Auth headers used by the template:Authorization: Bearer {value.json.access_token}.
Template parameters
BASE_ADDRESS default: https://mingle-ionapi.YOUR_REGION.inforcloudsuite.com/YOUR_TENANT.
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
CallM3Lstoperations by publishing a JSON payload to its request topic, and read the reply on the response topic:

