Feedback Endpoint

The /v3/feedback endpoint lets client applications forward user feedback directly to AquaCloud. It accepts structured payloads and relays them to the configured Slack webhook. Authentication is identical to other v3 routes: include Authorization: Bearer <token> and, for non-premium tiers, add the x-client-secret header.

Request body

Field	Type	Required	Description
message	string (1–4000 chars)	Yes	Feedback text supplied by the end user.
severity	enum (info, idea, bug, question)	No (default info)	Categorises the submission for triage.
name	string	No	Reporter name.
email	email	No	Contact email for follow-up.
page	string	No	Page or route where the feedback originated.
context	object	No	Additional metadata (browser info, device data, etc.).
created_at	ISO datetime	No	Auto-populated when omitted.

Response

On success the API acknowledges receipt and schedules delivery to Slack:

{
  "id": "0c6ba6e8ad6d46ab8e4a1f0b5b7b4f5c",
  "status": "accepted",
  "message": "Feedback received"
}

If the Slack webhook is not configured the response still returns status: accepted; the API logs a warning for operators. Transport errors return a JSON body with status: error and an explanatory message.

Example request

curl -X POST https://api.aquacloud.ai/v3/feedback \
  -H "Authorization: Bearer $TOKEN" \
  -H "x-client-secret: $CLIENT_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Love the new mortality dashboard!",
    "severity": "idea",
    "name": "Jane Analyst",
    "email": "jane@example.com",
    "page": "/dashboards/mortality",
    "context": {"browser": "Chrome 123", "locale": "nb-NO"}
  }'

Use the endpoint whenever you need to surface in-app feedback without leaving the AquaCloud environment.