What's new in Customer Journeys?

Connect and learn more!
VBCS not supporting oneOf keyword in OpenAPI3? — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

VBCS not supporting oneOf keyword in OpenAPI3?

Received Response


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:

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!