VeroXM Docs

Fields

Fields are the individual, typed properties that make up a collection. Every field has a name, a type, and a set of type-specific options and validations.

Field name

A field's name is the key used to read and write its value through the Content API and in the dashboard's editor - for example a title field on a text collection. Field names should stay stable once an integration depends on them, for the same reason a collection's slug should.

Validations

Depending on the field type, you can require a value, cap length (for text fields, a Min/Max/Between/None character-count rule), constrain a number's range, or mark a field as unique within its collection. Validation runs both when an editor saves content in the dashboard and when a token writes through the Content API.

Draftable fields

Text, Long Text, and Email fields are draftable: their content can be sent to VeroXM's AI drafting, summarizing, and translation tools. Structured field types (Number, Boolean, Relation, and the rest) are not, since they hold values rather than free-form prose.

Field order is display order

The order fields are added in a collection is the order they appear in the dashboard's content editor. Reordering fields is purely cosmetic and never changes stored data or API responses, which are always keyed by field name.