Export Entities
Export the FULL filtered result set of one entity type as a spreadsheet-style
table — the bulk counterpart of List Entities.
Unlike the paginated list, the export is unpaginated: it returns every record
matching the same filterText / filters, as flat records keyed by each
column’s field referenceId.
The response is a JSON envelope — { entityType, rowCount, fields, data } —
where fields describes the exported columns (referenceId, type, label)
and data is the array of row records. CSV / spreadsheet materialization is a
client concern (render data against fields); the endpoint itself returns
structured JSON.
By default EVERY configured field of the type is exported (plus the system
id / createdAt / updatedAt columns). Pass fields to restrict or reorder
the columns.
Accepts both authentication modes: an API key (Authorization: <key>) or an
Auth0 user Bearer token.
Required permission: company.{entity}:list — the exact key varies by
type (Policy uses company.policy:export). See
Permissions.
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 entity type (lowercase kebab-case URL slug). One of the six
CRUD entity types: event, exposure, quote, submission, person,
organization. policy is NOT valid here — Policy has no generic CRUD (its
writes go through the policy transaction endpoints), though it does have a
read-only /configuration schema.
event, exposure, quote, submission, person, organization Query Parameters
Search across quote number, description, and other text fields
JSON-encoded array of field filters applied server-side against the
entity's fieldModelV1Data. Use this to look an entity up by a business key
(e.g. a document ID or any configured field value) instead of paging the whole
collection and matching client-side. Complements filterText, which only
searches the configured display field.
Each filter is { fieldReferenceId, fieldType, operator, value } and supports
type-specific operators. Supported field types: text, number, boolean,
date, currency, optionSet, address, join, textList, numberList,
optionSetList, addressList. This is the same filter shape the
List Policies endpoint accepts.
List-cardinality types support operators: listIncludes (textList, numberList,
addressList), listIn, listAll, listExcludes (optionSetList).
The join type supports the in operator.
See the Configuration API for available field reference IDs.
Field to sort by. Accepts createdAt, updatedAt, or any configured field
referenceId for the entity type (sorting is config-driven). Default createdAt.
Sort direction (default desc)
asc, desc JSON-encoded array of explicit export columns, each
{ referenceId, type, label } where type is one of field-model-v1,
financial, or system. Omit to export the type's full default column
set (system columns + every configured field).
Point-in-time lens (YYYY-MM-DD). For Policy it resolves each policy to
the segment in effect on this date; for Event it bounds the financial
export columns. Ignored for entities with neither segments nor financials.
Response
The exported rows as a JSON envelope
The canonical entity type that was exported (e.g. Exposure).
Total number of exported records.
The exported column descriptors, in column order.
The exported rows — one flat record per entity, keyed by each column's field referenceId, with formatted scalar cell values.
