Key points to consider for custom REST connectors

When using the automatic approach to create the connector:

• The guidelines followed to derive the content-type and accept header are as follows:
  • "application/json" is the default selection when found in the list.
  • Else, the first one from the list is selected.
    • if the first one is found as "*/*", then the next one is selected if present.
    • if only "*/*" is found, then the default is set to "application/octet-stream".
  • The response content-type header value is set as the request accept header.
    • No interactions are created for the deprecated operations.
    • For the OpenAPI version 3 specification, operations with "application/x-www-form-urlencoded" & "multipart/mixed" are not supported.
    • "multipart/form-data" is not supported.
    • You cannot create or edit any operation using the New Operation option in the Custom Operations page.