Update kit data (legacy)

post

https://example.com/v1/kit/{kitType}/{kitId}

Deprecated: use PATCH /kit/{kitType}/{kitId} to update an existing kit, or POST /kit/{kitType} to create one. This route remains supported for backward compatibility; using kitId 'new' creates a kit.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

kitType

string

required

Name of the kit type

kitId

string

required

ID of the kit or a publicID (or entity ID) of an entity. If a publicID is provided the system will attempt to find a kit instance by the connection between the active entity and the entity with the provided publicID and an associated kit instance. The legacy value 'new' creates a kit; use POST /kit/{kitType} instead.

Query Params

connectionRole

string

enum

Allowed:

locale

string

Language locale of the user updating the profile

slimResponse

boolean

Only return the connection portion of the response. Don't return the answers.

updateChangeDateForInterface

boolean

Set to false to cause the profile change to not update interface change dates. This will prevent the change from causing the connection to show up on the change list.

transformation

string

Name of transformation template to apply to kit.

strictValidation

boolean

Opt into canonical answer-format and eligibility preflight with true. False skips this preflight only; permissions, kit access and row-deletion authorization always apply. Omission currently preserves legacy behavior; the server may later default to strict validation, with false remaining an explicit opt-out. This is not a dry run: accepted requests still write data.

Body Params

JSON document of answer key/values

Map of exact answer keys to write values. Values may be scalars, arrays, objects, or null where the question supports clearing. Question-specific types, permissions, and constraints still apply. GET representations are not necessarily valid write values. For a file upload use {fileName, fileContentsBase64} with raw padded base64. For an existing repeating-group row include its id; omitting id creates a new row.

Responses

403

Kit mutations require current VIEW and WRITE permission for the active entity and kit type; denial rejects before transformations, uploads or persistence. Effective row-deletion permission is checked before uploads and persistence, independently of observe mode. Enforce-mode preflight may reject unsupported deletion syntax earlier.

Language

Credentials

Bearer

JWT

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

201JSON document of updated kit data. Document properties are answer keys.