Inbound integrations receive data from external systems and map that to Actions it also controls to what URL you can send data.
POST Info
iHub listens for HTTP POST that are sent to;
- Content-Type: application/json
https://testsup.rixter.se/rest/restfulintegrator/1.0/incoming
- Content-Type: multipart/form-data
https://testsup.rixter.se/rest/restfulintegrator/1.0/incoming/files
For multipart data use query params to send data to the action. Query params will be converted to json input for the action.
It is allowed to specify a specific path param after the /incoming/ and /incoming/files/ which can be used for setting up specific integration URLs.
Example. HTTP POST to https://testsup.rixter.se/rest/restfulintegrator/1.0/incoming/mysystem could have a rule which has a URL condition that requires that URL to trigger a iHub action.
Use Rules to define when and how the incoming data shall be processed