For the complete documentation index, see llms.txt. This page is also available as Markdown.
User Feedback
User feedback reports allow your application to collect non-crash feedback and bug reports from end users. Unlike crash reports that are generated automatically when an application fails, user feedback reports are submitted intentionally by users to describe issues, request features, or report bugs.
How It Works
When a user feedback report is posted to BugSplat:
The title becomes the stack key (crash group), making it easy to group and track related feedback
The description becomes the exception message, providing additional context
Reports appear alongside crash reports in the BugSplat dashboard with the platform label "User Feedback"
File Formats
User feedback reports can be uploaded as either feedback.xml or feedback.json.
XML
<?xml version="1.0" encoding="utf-8"?><feedbackversion="1"><title>Login button does not respond</title><description>Tapping login on iPhone does nothing.</description></feedback>
Special XML characters in title and description (&, <, >, ", ') must be escaped using standard XML entities.
JSON
Fields
Field
Required
Description
title
No*
Short summary of the feedback (becomes stack key); if omitted, a truncated description is used instead
description
No*
Detailed description of the issue (can be empty)
* At least one of title or description must be provided.
Uploading via Presigned URL
User feedback reports are uploaded using the same presigned URL flow as crash reports. See Crash Post Endpoints for full details on Steps 1-3.
Use crashType=User.Feedback (or crashTypeId=36) when committing the upload in Step 3.
Quick Reference
Step 1:GET /api/getCrashUploadUrl to get a presigned upload URL
Step 2:PUT the zipped feedback.xml (or feedback.json) to the presigned URL
Step 3:POST /api/commitS3CrashUpload with crashType=User.Feedback
Optional fields on commit: user, email, description, appKey, attributes