We’re enforcing field validation rules on the Management API

For a long time, the character limits and item-count limits you configure on component fields (like max_length on a text field, or maximum items on a bloks field) were only checked in the Visual Editor. The API itself would accept content that exceeded those limits.

We’re changing that. Starting today, content saved through the Management API will be validated against the rules in your component schemas.

What’s changing

Text-type fields text, textarea, markdown, richtext) with a configured max_length will reject content exceeding the limit.

bloks fields with a configured maximum will reject content with more nested items than allowed.

Failed saves return 422 Unprocessable Entity with a message including both the configured limit and the current value.

What’s not changing

Regex pattern validation continues to run only in the Visual Editor. Enforcing JavaScript regex patterns on the Ruby backend isn’t straightforward, and we want to get that right before rolling it out.

Content already stored in your space is not re-validated. Validation only runs on new saves and updates.

Rollout timeline

1. Today: Enforcement is enabled for all newly created spaces.

2. 8 June: Enforcement will be enabled for all existing spaces.

The window gives you time to review integrations that write to the Management API and make sure the content they generate complies with the limits you’ve configured. If you find limits that are too strict for your data, you can adjust them in the component schema at any time.