Improved
v2 - 2026-09-22 - Entity types are workspace-specific
about 18 hours ago by ReadMe GitHub Action
- Changed
EntityTypefrom a fixed enum to an open string. The types available to you depend on your workspace configuration; use List entity configurations as the authoritative list and thetypeof each returned configuration as the filter value. New entity types become available without a specification change. - List entities
type[]values that your workspace does not have now return400 request.invalidwith adetailnaming the types that are available. The error code is unchanged; only the message changed. - Retrieve entity configuration A type your workspace does not have now returns
400 request.invalidlisting the available types instead of404 entityType.notFound. Unknown types returnrequest.invalidinstead ofvalidation.request.parameter.schema.enum. - Create entity An unavailable
data.typereturns400 request.invalidwith the available types indetailinstead ofvalidation.request.body.schema.enum. - Search entities, List relationships and List field values validate their type filters against the same workspace list.
- Clients generated from the OpenAPI specification no longer get an
EntityTypeenum; the field is astring. Values on the wire are unchanged.
