Help detect when their supplied query inputs are invalid

[pudo]

supplying birthDate when schema is LegalEntity ignores birthDate and logs a warning on the API side, which the user never see.

Supplying something that doesn't validate as a date doesn't log server side and is also just ignored.

At least since explanations, it's noted as if it wasn't supplied, which is a strong hint.

Is rejecting the request outright too harsh?

Maybe we could then just make the explanations even more concrete, e.g. Date supplied was invalid? For the property that isn't relevant, it's harder to know what to say, but perhaps also more ok to reject the request since it isn't a validation question as much as a schema question.

[pudo]

One thing we already do is to return the parsed output of the query as it was understood by us in the responses as query. I've been telling users to look at the delta between that and what they passed in as an indication of which content we were (and weren't able to parse).

[jbothma]

• could document "parsed query" in response under best practices
• could have a "strict" mode that rejects query if something can't be parsed, e.g. country not mapped to a code, date doesn't parse