Get Policy Configuration
Returns a JSON Schema describing the fields available for a Field Model V1
Policy. Policy is separately owned and has its own dedicated configuration
endpoint rather than riding the parametric
entities/{entityType}/configuration route (whose entityType covers only
the six CRUD entity types).
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 lists fields that must be provided.
Calculated (JEXL-derived) and other server-managed fields — e.g.
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 annotation means
“server-managed”, not “rejected on write”.
Required permission: company.policy: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
Response
Configuration for the policy'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.