---
title: "Create a new feedback record"
method: POST
path: "/v1/feedback-records"
tags: ["Feedback Records"]
---

# Create a new feedback record

`POST /v1/feedback-records`

Creates a new feedback record data point

## Request body

- CreateFeedbackRecordInputBody
  - `collected_at` string, date-time — When the feedback was collected (defaults to now). Must be between 1970-01-01 and 2080-12-31.
  - `field_id` string, required — Identifier for the question/field. NULL bytes not allowed.
  - `field_label` string, nullable — The actual question text
  - `field_group_id` string — Stable identifier grouping related fields (for ranking, matrix, grid questions). NULL bytes not allowed.
  - `field_group_label` string, nullable — Human-readable question text for the group
  - `field_type` 'text' | 'categorical' | 'nps' | 'csat' | 'ces' | 'rating' | 'number' | 'boolean' | 'date', required — Field type: text (enrichable), categorical, nps, csat, ces, rating, number, boolean, date
  - `language` string — ISO language code. NULL bytes not allowed.
  - `metadata` object — User agent, device, location, referrer, tags, etc. NULL bytes (\x00 or \u0000) are not allowed in JSON keys or values.
  - `source_id` string, nullable — Reference to survey/form/ticket ID
  - `source_name` string, nullable — Human-readable name
  - `source_type` string, required — Type of feedback source (e.g., survey, review, feedback_form). NULL bytes not allowed.
  - `submission_id` string, required — Identifier for the logical submission this record belongs to (tenant-scoped). Required. Enables grouping multi-field submissions and idempotent ingestion. Unique per (tenant_id, submission_id, field_id). If a record has no logical submission, use e.g. field_id.
  - `tenant_id` string, required — Tenant/organization identifier for multi-tenancy. Required.
  - `user_id` string — User ID (e.g., anonymous ID or email hash)
  - `value_boolean` boolean — For yes/no questions
  - `value_date` string, date-time — For date responses. Must be between 1970-01-01 and 2080-12-31.
  - `value_number` number, double — For ratings, NPS scores, numeric responses. Must be between -1e15 and +1e15.
  - `value_text` string, nullable — For open-ended text responses. Omit or null if not applicable. NULL bytes not allowed when present.

## Response `201`

Created

- FeedbackRecordData
  - `collected_at` string, date-time, required — When the feedback was collected
  - `created_at` string, date-time, required — When this record was created
  - `field_id` string, required — Identifier for the question/field
  - `field_label` string — The actual question text
  - `field_group_id` string — Stable identifier grouping related fields (for ranking, matrix, grid questions)
  - `field_group_label` string — Human-readable question text for the group
  - `field_type` 'text' | 'categorical' | 'nps' | 'csat' | 'ces' | 'rating' | 'number' | 'boolean' | 'date', required — Type of field
  - `id` string, uuid, required — UUIDv7 primary key
  - `language` string — ISO language code. NULL bytes not allowed.
  - `metadata` object — Additional context
  - `source_id` string — Reference to survey/form/ticket ID
  - `source_name` string — Human-readable name
  - `source_type` string, required — Type of feedback source
  - `submission_id` string, required — Identifier for the logical submission this record belongs to (required).
  - `tenant_id` string, required — Tenant/organization identifier. NULL bytes not allowed.
  - `updated_at` string, date-time, required — When this record was last updated
  - `user_id` string — User ID (e.g., anonymous ID or email hash)
  - `value_boolean` boolean — Boolean response
  - `value_date` string, date-time — Date response
  - `value_number` number, double — Numeric response
  - `value_text` string — Text response. NULL bytes not allowed.

## Other responses

- `400` — Bad Request (e.g. validation error)
- `409` — Conflict. Either a duplicate tenant_id/submission_id/field_id (code `conflict`, terminal), or a tenant data purge is in progress for this tenant (code `tenant_write_conflict`, retryable – retry after the purge completes).
- `default` — Error

## Changes

- **2026-06-16** `d2fa5d9f2e98` — 3 warning
  - added the new `tenant_write_conflict` enum value to the `code` response property for the response status `400`
  - added the new `tenant_write_conflict` enum value to the `code` response property for the response status `409`
  - added the new `tenant_write_conflict` enum value to the `code` response property for the response status `default`
- **2026-06-03** `6907a0a9de00` — 3 breaking, 3 warning, 18 info
  - the `instance` response's property type/format changed from `string`/`uri` to `string`/`` for status `400`
  - the `instance` response's property type/format changed from `string`/`uri` to `string`/`` for status `409`
  - the `instance` response's property type/format changed from `string`/`uri` to `string`/`` for status `default`
  - removed the optional property `errors` from the response with the `400` status
  - …20 more
- **2026-04-30** `2fe8dc460c4d` — 3 info
  - the `type` response's property default value `about:blank` was removed for the status `400`
  - the `type` response's property default value `about:blank` was removed for the status `409`
  - the `type` response's property default value `about:blank` was removed for the status `default`
- …earlier changes not shown

[Full history](https://skmtc.dev/formbricks/apis/formbricks-hub-api/changes/v1/feedback-records/post.md)

---

[API](https://skmtc.dev/formbricks/apis/formbricks-hub-api.md) · [All operations](https://skmtc.dev/formbricks/apis/formbricks-hub-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/formbricks/formbricks-hub-api/revisions/d2fa5d9f2e98/schema)