- Fields are dynamically defined per company. Use the Configuration endpoint to discover available fields and their types.
- The request body for create and update is a flat JSON object where keys are field
referenceIds (e.g.,exposureName,numberOfEmployees). - Responses include a
fieldModelV1Dataobject containing all field values (including base fields likeexposureNameandexposureType). - Updates are full replacements — include all fields you want the exposure to have, not just the changed ones.
Configuration
CallGET /v1/exposures/configuration to get a JSON Schema of available fields for your company. The schema includes:
- Field types:
string,number,boolean,object - Option Set fields: include an
enumarray of valid values - Required fields: listed in the
requiredarray
Field Types
| FMV1 Type | JSON Type | Description |
|---|---|---|
| Text | string | Free-text string |
| Number | number | Numeric value |
| Boolean | boolean | True/false |
| Option Set | string or number | Constrained to enum values |
| Object | object | Nested object |
API Endpoints
- Get Configuration - JSON Schema of available fields
- Create Exposure - Create a new exposure
- List Exposures - Paginated list with filtering and sorting
- Get Exposure - Retrieve a single exposure by ID
- Update Exposure - Full replacement update
- Delete Exposure - Soft delete
Permissions
| Operation | Required Permission |
|---|---|
| Get Configuration | company.insured:read |
| List Exposures | company.insured:read |
| Get Exposure | company.insured:read |
| Create Exposure | company.insured:create |
| Update Exposure | insured:update |
| Delete Exposure | insured:delete |
