If this were a header issue or payload-related issue, I think the error should have indicated that. But the error I'm getting in response is quite confusing.
Hey. We've tracked this down on our end. It's a bug that only exists in the Rest API. For this model we end up serializing some configuration incorrectly. We think we have a fix and will try and roll it out shortly. I'll update you when that goes out