If the type generation seems to be working properly for this request content type, the content serialization won't as we don't have a serializer for it. Adding a serializer should be trivial using the natively available libraries on the platform to build the body so encoding is handled for us.

More reading

originally reported
AB#9787