Skip to main content
POST
Create Entity

Authorizations

Authorization
string
header
required

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.

Headers

Idempotency-Key
string<uuid>

Optional caller-authored UUID that makes retries of this create safe. Reuse the key only for the same entity type and request body. A retry returns the original live entity ID; a key assigned to an unavailable entity returns 409. UUID spelling is normalized to lowercase, so uppercase and lowercase spellings replay the same create.

Idempotency-Owner
string

Optional opaque owner token for a keyed create. This header requires Idempotency-Key. It grants no access or ownership by itself: on a replay, idempotencyOwnerMatched is true only when the value exactly matches the token recorded by the original successful create.

Required string length: 1 - 255

Path Parameters

companyId
string<uuid>
required

Company identifier

entityType
enum<string>
required

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.

Available options:
event,
exposure,
quote,
submission,
person,
organization

Body

application/json

Flat JSON object with field referenceIds as keys

Response

Entity created successfully

id
string<uuid>

The ID of the created entity

created
boolean

True when this request inserted the entity; false for an idempotent replay

idempotencyOwnerMatched
boolean

True for a fresh create or when the replay's Idempotency-Owner matches the original create