Get Entity Configuration
Returns a JSON Schema describing the fields available for creating or
updating a Field Model V1 CRUD entity. The entityType path parameter is
the lowercase kebab-case entity slug (event, exposure, quote,
submission, person, or organization).
Policy is separately owned and has its own
Get Policy Configuration
endpoint (/policies/configuration); policy is not accepted here.
The fields schema is a standard JSON Schema (draft 2020-12) that can be
used directly with validation libraries like Ajv or Zod. The required
array is exactly the set of fields you must supply when CREATING the
entity — the platform’s structural requirements minus everything the write
path produces for you (join fields, calculated fields, server-seeded
defaults). Supply all of them and the create cannot be rejected for missing
input; omit any and the create is rejected with a single InvalidEntityShape
400 naming every field it missed. Requiredness does not apply to PATCH,
which merges only the fields you send. For entities that embed exposures
(Quote), the embedded exposure schema is nested under its join field
(e.g. exposures).
Calculated (JEXL-derived) and other server-managed fields — e.g.
quoteNumber, quoteStatus, policyPremium — are included in the schema
(so they are discoverable and overridable) but annotated with
readOnly: true and x-calculated: true so consumers can tell them apart
from ordinary inputs. The write path still accepts these fields; the
calculated expression decides whether a supplied value is honored or
recomputed, so the annotation means “server-managed”, not “rejected on
write”. This annotation is applied uniformly across every entity type.
Required permissions (per entity type):
Event:company.event:exportExposure:company.insured:readQuote:company.quote:readSubmission:company.submission:readPerson:company.fmv1_custom_object:readOrganization:company.fmv1_custom_object:read
Authorizations
API key authentication. Send your raw API key as the Authorization header value with NO scheme prefix — Authorization: YOUR-API-KEY. Do NOT prefix it with Bearer or ApiKey, and do not use an X-API-Key header; those are not accepted.
Path Parameters
Company identifier
Field Model V1 CRUD entity type (lowercase kebab-case URL slug). Policy is
separately owned and has its own configuration endpoint
(/policies/configuration); it is not a valid value here.
event, exposure, quote, submission, person, organization Response
Configuration for the entity's fields
Configuration response for a Field Model V1 entity (Event, Exposure, Quote,
Submission, Person, Organization, or read-only Policy). Returns a JSON Schema
describing the fields available for creating or updating that entity. For
entities that embed exposures (Quote),
the embedded exposure schema is nested under the corresponding join field
(e.g. exposures) rather than returned as a separate top-level key.
Standard JSON Schema (draft 2020-12) describing field definitions
for Field Model V1 entities. Includes a required array listing
fields that must be provided.
