...
The external system POST data to iHUBs URL, which is stated in on the Incoming page.
URL ends with /rest/restfulintegrator/1.0/incoming
| Status | ||||||
|---|---|---|---|---|---|---|
|
...
Here is an example.
On your Firewall open up <baseurl>/rest/restfulintegrator/1.0/incoming/014aed18-c4d2-4166-9745-39648cce64e9 (we have used https://www.uuidgenerator.net/ to generate the UUID)
...
Response from Incoming REST end-point
...
Standard response:
Standard response is always: HTTP 200 OK
This response is recommended in production envs.
Echoed Response:
From the Incoming settings page it's possible to enable debug response mode.
Select the "Respond with POST data and triggered action(s) to "ON" to enable debug mode.
The response will then echo the post body, URL and triggered integrations. This is recommended for dev mode when setting things up.
Incoming requests with files (multipart data)
iHub supports incoming files. This is very useful for cases where you do not want to open up Jira for the world to use the JIRA rest API to add attachments.
URL for incoming files is: rest/restfulintegrator/1.0/incoming/files
This can, of course, be combined with a UUID to secure firewall openings ie: rest/restfulintegrator/1.0/incoming/files/014aed18-c4d2-4166-9745-39648cce64e9
Using incoming files in iHub actions
Using the incoming files in an action is simple, just enable "Incoming files" under the Attachments sections in the "Actions" page.
The integration action request will now be sent as a multipart/form-data request with the incoming files in the request.