Feedback Records
List feedback records with filters
Create a new feedback record
Delete feedback records by user ID
Get a feedback record by ID
Delete a feedback record
Update a feedback record
Get similar feedback records
Count feedback records
ModelsExpand Collapse
FeedbackRecordData = object { id, collected_at, created_at, 24 more }
UUIDv7 primary key
When the feedback was collected
When this record was created
Identifier for the question/field
field_type: "text" or "categorical" or "nps" or 6 moreType of field
Type of field
Type of feedback source
Identifier for the logical submission this record belongs to (required).
Tenant/organization identifier. NULL bytes not allowed.
When this record was last updated
emotions: optional array of "joy" or "anger" or "sadness" or 3 moreEmotions inferred from value_text (emotion enrichment); multi-label from a fixed set. Read-only; absent until the record is enriched, and never an empty array.
Emotions inferred from value_text (emotion enrichment); multi-label from a fixed set. Read-only; absent until the record is enriched, and never an empty array.
Stable identifier grouping related fields (for ranking, matrix, grid questions)
Human-readable question text for the group
The actual question text
ISO language code. NULL bytes not allowed.
metadata: optional unknown or array of unknown or string or 2 moreArbitrary context stored with this record, returned with equivalent values (key order is normalized, and so are number exponents — 1e2 reads back as 100). Omitted when the record has no metadata; a record explicitly stored with a JSON null returns null.
An object is the supported shape and the only one the request schemas accept. The wider union is for reading: the column stores whatever JSON was written, so a record created before that convention can return an array or a scalar, and an object-only response schema would make a generated client reject it.
Arbitrary context stored with this record, returned with equivalent values (key order is normalized, and so are number exponents — 1e2 reads back as 100). Omitted when the record has no metadata; a record explicitly stored with a JSON null returns null.
An object is the supported shape and the only one the request schemas accept. The wider union is for reading: the column stores whatever JSON was written, so a record created before that convention can return an array or a scalar, and an object-only response schema would make a generated client reject it.
Arbitrary context stored with this record, returned with equivalent values (key order is normalized, and so are number exponents — 1e2 reads back as 100). Omitted when the record has no metadata; a record explicitly stored with a JSON null returns null.
An object is the supported shape and the only one the request schemas accept. The wider union is for reading: the column stores whatever JSON was written, so a record created before that convention can return an array or a scalar, and an object-only response schema would make a generated client reject it.
Arbitrary context stored with this record, returned with equivalent values (key order is normalized, and so are number exponents — 1e2 reads back as 100). Omitted when the record has no metadata; a record explicitly stored with a JSON null returns null.
An object is the supported shape and the only one the request schemas accept. The wider union is for reading: the column stores whatever JSON was written, so a record created before that convention can return an array or a scalar, and an object-only response schema would make a generated client reject it.
Arbitrary context stored with this record, returned with equivalent values (key order is normalized, and so are number exponents — 1e2 reads back as 100). Omitted when the record has no metadata; a record explicitly stored with a JSON null returns null.
An object is the supported shape and the only one the request schemas accept. The wider union is for reading: the column stores whatever JSON was written, so a record created before that convention can return an array or a scalar, and an object-only response schema would make a generated client reject it.
Arbitrary context stored with this record, returned with equivalent values (key order is normalized, and so are number exponents — 1e2 reads back as 100). Omitted when the record has no metadata; a record explicitly stored with a JSON null returns null.
An object is the supported shape and the only one the request schemas accept. The wider union is for reading: the column stores whatever JSON was written, so a record created before that convention can return an array or a scalar, and an object-only response schema would make a generated client reject it.
Arbitrary context stored with this record, returned with equivalent values (key order is normalized, and so are number exponents — 1e2 reads back as 100). Omitted when the record has no metadata; a record explicitly stored with a JSON null returns null.
An object is the supported shape and the only one the request schemas accept. The wider union is for reading: the column stores whatever JSON was written, so a record created before that convention can return an array or a scalar, and an object-only response schema would make a generated client reject it.
sentiment: optional "very_negative" or "negative" or "neutral" or 3 moreSentiment polarity inferred from value_text (sentiment enrichment). Read-only; absent until the record is enriched.
Sentiment polarity inferred from value_text (sentiment enrichment). Read-only; absent until the record is enriched.
Signed sentiment polarity from -1.0 (very negative) to 1.0 (very positive) (sentiment enrichment). Read-only; absent until the record is enriched.
Reference to survey/form/ticket ID
Human-readable name
BCP-47 target locale that value_text_translated was produced in (language enrichment). Read-only; absent until the record is enriched.
User ID (e.g., anonymous ID or email hash)
Boolean response
Date response
Stable id of the selected option in the source system (e.g. a survey choice id), stored alongside value_text for durable option identity. Opaque to Hub. Absent for free-text/non-choice answers. NULL bytes not allowed.
Numeric response
Text response. NULL bytes not allowed.
value_text translated into the tenant's configured target language (language enrichment). Read-only; absent until the record is enriched.