V3 Feedback Records

Delete a user's feedback records

Changed on

Permanently deletes every record in the dataset whose user_id matches — the erasure operation for GDPR Article 17 requests. Derived embeddings are removed with the records. Idempotent: repeating the call answers deleted_count: 0.

tenant_id is required: the gateway scopes erasure to one dataset. (The underlying store can erase a user across every dataset when tenant_id is omitted; that form is not reachable through this API.) Records written without a user_id cannot be reached this way — delete them individually.

Deletion is unrecoverable, so it requires an API key with manage permission on a workspace the dataset is assigned to, and the dataset must be assigned to exactly one workspace: on a shared dataset no workspace permission can say whose records these are, so API-key mutations are refused with 403.

delete/api/v3/feedbackRecords

Request

  • Base URL
    https://app.formbricks.com
  • URL
    https://app.formbricks.com/api/v3/feedbackRecords
  • Auth
    API key in header x-api-key

Query parameters

user_idstring required

The end-user identifier whose records to delete.

tenant_idstring cuid2 required

The feedback dataset to operate on (the dataset id, as shown by the MCP list_feedback_datasets tool). Required by the gateway on this operation: a missing or malformed value answers 400 before the request reaches the feedback store, and a dataset the API key's workspace is not assigned to answers 403. The two POST operations take the same value in the request body instead, and the single-record operations derive it from the record.

Response

Records deleted

deleted_countinteger required

Number of records deleted. 0 when the user had no remaining records — the operation is idempotent.

messagestring required

Human-readable status message.

Changes