Event Feedback: Backend API & Data Model

The backend contract for event feedback: endpoints, the complete validation pipeline in feedbackHelpers.js, submission storage, and the DynamoDB schema.

Endpoints

Related admin write path (saves feedback config on the event):

• PATCH /events/{id}/{year} — updates attendeeFeedbackQuestions, partnerFeedbackQuestions, enabled flags

All handlers are in services/events/handler.js.

formType

Accepted values: "attendee" or "partner". Any other value returns 400.

Internally, parseFormType() from feedbackHelpers.js maps this to the correct event fields:

Question Types

Defined as FEEDBACK_QUESTION_TYPES in feedbackHelpers.js:

feedbackHelpers.js — Normalization Pipeline

File: services/events/feedbackHelpers.js (~350 lines)

When an admin creates or updates feedback questions (via POST /events/ or PATCH /events/{id}/{year}), the handler runs each question array through this pipeline:

normalizeFeedbackQuestions(questions, prefix)

For each question:

1. Type validation — must be in FEEDBACK_QUESTION_TYPES set, returns 406 otherwise
2. Label validation — must exist and be ≤500 characters
3. UUID assignment — if no questionId, assigns uuid.v4(). Deduplicates IDs (returns 406 on duplicate)
4. Selectable type validation (MULTIPLE_CHOICE, CHECKBOXES):
   • Must have a choices array with ≥2 items
   • Each choice is trimmed, empty choices are filtered out
   • Duplicate choices are rejected
5. Scale validation (LINEAR_SCALE):
   • scaleMin and scaleMax must be integers
   • scaleMin < scaleMax
   • Both must be 0–20 range
   • scaleMinLabel and scaleMaxLabel are trimmed, max 120 characters each
6. Max count — enforces ≤50 questions per form

ensureDefaultOverallRatingQuestion(questions)

Called on both create and update. Strips any existing question with questionId === "overall-rating" and prepends:

{
  "questionId": "overall-rating",
  "type": "LINEAR_SCALE",
  "label": "How would you rate this event overall?",
  "required": true,
  "scaleMin": 1,
  "scaleMax": 10,
  "scaleMinLabel": "Poor",
  "scaleMaxLabel": "Excellent"
}

This question is locked — admins cannot remove or modify it.

feedbackHelpers.js — Validation Pipeline

When a user submits feedback via POST /events/{id}/{year}/feedback/{formType}:

validateFeedbackPayload(questions, payload)

1. Respondent validation:

   • respondentName — optional, ≤120 characters
   • respondentEmail — optional, must match email regex

2. validateResponseObjectShape(responses) — responses must be a plain object

3. validateNoUnknownQuestionIds(questions, responses) — every key in responses must match a questionId in the question config. Unknown keys return 400.

4. Per-question validation — for each question in the config:

   • If required: true and the response is missing/empty → 400
   • Type-specific validation:

Submit Payload

{
  "respondentName": "Jane Doe",
  "respondentEmail": "jane@example.com",
  "responses": {
    "overall-rating": 9,
    "q-networking": "Great networking opportunities",
    "q-format": ["Panels", "Workshops"]
  }
}

Response on success:

{
  "message": "Feedback submitted successfully.",
  "id": "<submission-uuid>"
}

getFeedbackForm Response

Returns a subset of the event record tailored for the public form:

{
  "id": "blueprint",
  "year": 2026,
  "ename": "Blueprint 2026",
  "description": "Product and design conference",
  "imageUrl": "https://...",
  "endDate": "2026-01-25T18:00:00.000Z",
  "isCompleted": true,
  "formType": "attendee",
  "enabled": true,
  "questions": [
    {
      "questionId": "overall-rating",
      "type": "LINEAR_SCALE",
      "label": "How would you rate this event overall?",
      "required": true,
      "scaleMin": 1,
      "scaleMax": 10,
      "scaleMinLabel": "Poor",
      "scaleMaxLabel": "Excellent"
    }
  ]
}

Submission Storage — biztechEventFeedback

GSIs

Table billing: PAY_PER_REQUEST (on-demand).

Error Responses

Key Files

Related Pages

• Event Feedback Overview — top-level feedback architecture
• Admin Builder — how admins configure feedback questions
• Public Forms — the attendee-facing form experience
• Events Service — all 10 event endpoints
• Event Data Model — feedback fields on the event record