We have the need to be able to specify an alternate "Content-Type" when sending a POST transaction via automation, but per the ticket I submitted it appears the system doesn't support it. Specifically, currently we can't connect to Ellucian Ethos via SmartSuite because "application/json" is not a valid Content-Type on the receiving end. On the Ellucian side, the Content-Type needed varies based on the endpoint. For example, one of the endpoints we're currently trying to connect to wants me to specify "application/vnd.hedtech.integration.person-matching-requests-initiations-prospects.v1.0.0+json" as the Content-Type.

We are confident it's not an issue with Ellucian Ethos specifically because there are other non-POST requests we're making to Ethos via SmartSuite HTTPS calls that work successfully on a regular basis, even with a "non-standard" Content-Type specified in the header.