[WC1] Invalid date-time format for PepInactivityPeriod.termEndDate

Question

The OpenAPI specification for the World-Check One screening API defines the schema PepInactivityPeriod since version 3.1.0 with a property termEndDate of type string with format date-time. According to the OpenAPI specification (https://swagger.io/docs/specification/v3_0/data-models/data-types/#string-formats), date-time means RFC 3339 (https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) compliant. Notably, this spec makes all components of the date-time mandatory (date-time = full-date "T" full-time).

We have observed that the screening API returns a truncated value in that property (e.g. "termEndDate": "2021-12"), which is not compliant, and unfortunately breaks our JSON deserialization.

Would it be possible to fix either the value (to be RFC 3339 compliant), or update the spec to reflect what is actually being sent? Thanks!

Regards,

Marc

marc_etter · Answer

Thanks, we will do so in the meantime. For the record, we also noticed the same issue on the following other fields:

* Field.dateTimeValue
* SecondaryFieldResult.submittedDateTimeValue
* SecondaryFieldResult.matchedDateTimeValue

The two SecondaryFieldResult values specifically in the case of date-of-birth (which obviously doesn't carry a time component)

Stefano.LSEG · Answer

@marc_etter

Thank you for reporting this. We have reviewed the behaviour and confirmed that this field may return dates with varying levels of precision, including year-only or year-month values. The current API schema does not accurately represent this behaviour, and we are reviewing updates to the API documentation/specification. In the meantime, clients should treat this field as a variable-precision date rather than a strict date-time value.

Stefano.LSEG · Answer

Hello @marc_etter,

I will reach out to the product team for confirmation/clarification on this.

EXPLORE OUR SITES