I wanted to clarify something in the WC1 API v3 OpenAPI spec.
Our team is generating our Java models for our integration with WC1 API from that OpenAPI spec.
In the image below, you will see the "Field" definition, which has set the format of the "dateTimeValue" to "date-time".
When we create a screening case, with the World-Check secondary field "SFCT_2", i.e. DATE_OF_BIRTH, the WC1 API expects a date in the format "1990-11-20". However, as the OpenAPI spec sets the format as "date-time", it generates models which expect a time element to be included, resulting in "1990-11-20T00:00:00Z" instead. When this gets sent to WC1 API, it is rejected as an invalid value.However, when we switch the format to "date", the generated model creates the correct format to send to WC1 API, and all is great.
Our assumption is that it is the OpenAPI spec that should have the format set to "date" in this case, instead of "date-time", rather than the expectation that WC1 API should accept full date-times for dateTimeValue-based custom/secondary fields.
Is this assumption correct? Have we done anything wrong integrating on our side?
Note: it's possible this question applies to other entities or WC1 API spec versions, but we haven't verified beyond this entity and version
