VBCS not supporting oneOf keyword in OpenAPI3?
Summary:
Unable to choose from multiple request bodies, using the oneOf keyword in OpenAPI specification imported in VBCS.
Content (please ensure you mask any confidential information):
We’re currently integrating our VBCS webapp with an external REST API that has an OpenAPI3 specification. For certain endpoints, the POST operation supports 2 options for the request body; either a single object, or an array of these objects. As far we know, OpenAPI supports these variations through the oneOf keyword, like shown here: https://spec.openapis.org/oas/v3.1.0#schema-object
The relevant part of the external REST API’s OpenAPI3 specification looks like this:
0