MicroApp Data Operations

Use these pages for the canonical REST API reference for datatable row access.

• row metadata and relationships is the source of truth for system fields, embeddingRowID, linked-table structures, and shared row semantics

• microappdata covers list/query/read-many operations

• microappdata/row covers read-one operations

• insertmicroapprow, insertmicroapprows, updatemicroapprow, and removemicroapprow cover write operations

Write-operation rules that apply across these endpoints

• rowData keys are matched against field labels, and label matching is case-sensitive.

• Unknown keys in rowData are ignored rather than creating new fields or changing arbitrary metadata.

• System metadata such as _id, submitted, clientSubmitted, parentResourceID, and topLevelParentID is not writable through rowData.

• The supported top-level metadata overrides are endpoint-specific and documented on each page. Today those are limited to things like embeddingRowID, userID, viewers, teamViewers, and ignoreActionRules.

• Some accepted parameters are permission-gated. For example, changing userID or moving a row to a different parent via embeddingRowID is only applied when the caller has the required access; otherwise the request may succeed without changing that metadata.