PRODUCTION SCENARIO
An intake service assembles its request body by hand and posts it to the Messages API, with no SDK helper anywhere in the path. Its structured-output schema sets minimum 0 and maximum 120 on age, minLength 5 on postal_code, and leaves additionalProperties unset on the top-level object. The API rejects the request with a 400. Both bounds still have to be enforced somewhere before the record is written.
Which revision makes the schema valid without losing the bounds?
Answering here is anonymous. Nothing is saved unless you sign in.
Show answer and explanation
Answer: Strip the bounds, add additionalProperties false, and range-check them in code afterwards
Numeric constraints such as minimum and maximum and string constraints such as minLength are outside the supported subset, and every object needs additionalProperties false, so an unsupported keyword is what draws the 400 and the bounds have to move into application code. An SDK helper performs that exact transformation and then validates the response against the original schema, which is the answer whenever a supported SDK builds the request; this service builds the body itself. Setting additionalProperties false is the entire fix when that is the only unsupported thing present. A pattern would cover postal_code, since simple regexes are supported, but the bounds on age stay in the schema and the request still fails.