Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Usage note!

Use this only in the case were attachment is needed, since the payload is different than regular application/json types.


iHub can send attachments to external endpoints. This is done. by sending Content-Type: multipart/form-data.

Content-Type: multipart/form-data

The body will be included in the payload:

Content-Disposition: form-data; name="file" filename="filename.xyz"
(content of filename.xyz) (can repeat)

Content-Disposition: form-data; name="body"
{the_body_section_of_the_config_page} 

There are three options available

  1. Do not include attachments - This is the standard way of just sending normal JSON data.
  2. Latest - any added attachment during the issue event will be added. Attachments older than 5seconds after the event occurs will not be added.
  3. All - Include all attachments in the payload multipart data
  4. Incoming - When this integration is part of an incoming rule. Read more on incoming: Incoming REST Calls
  • No labels