> ## Documentation Index
> Fetch the complete documentation index at: https://personal-ce79cb71.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Support Query API — Submit a BugViper Help Request

> Submit a BugViper support request via POST /api/v1/support/query. Provide your name, email, category, and message — no authentication required.

The support endpoint lets you programmatically submit a support request to the BugViper team. It requires no authentication — you can call it from any context, including unauthenticated flows where a user cannot yet sign in. Fill in the required fields and BugViper will route your query to the right team based on the category and priority you provide.

***

## POST /api/v1/support/query

Submits a new support query to the BugViper team.

**Authentication required:** No (public endpoint)

### Request Body

<ParamField body="name" type="string" required>
  Your full name.
</ParamField>

<ParamField body="email" type="string" required>
  Your email address. BugViper will use this address to follow up on your query.
</ParamField>

<ParamField body="subject" type="string" required>
  A brief subject line summarizing your request (e.g., `"Review not posting inline comments"`).
</ParamField>

<ParamField body="category" type="string" required>
  The category that best describes your request. Must be one of:

  * `bug_report` — Something is broken or not working as expected
  * `feature_request` — You'd like to suggest a new feature or improvement
  * `general_inquiry` — A general question about BugViper
  * `billing` — A question or issue related to your plan or payment
  * `other` — Anything that doesn't fit the above categories
</ParamField>

<ParamField body="priority" type="string" required>
  The urgency of your request. Must be one of `low`, `medium`, or `high`.
</ParamField>

<ParamField body="message" type="string" required>
  A detailed description of your issue or request. Include any relevant context such as repository names, PR numbers, error messages, or steps to reproduce.
</ParamField>

### Example

```bash theme={null}
curl -X POST https://your-domain.com/api/v1/support/query \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Jane Smith",
    "email": "jane@example.com",
    "subject": "Review not posting comments",
    "category": "bug_report",
    "priority": "high",
    "message": "BugViper reviewed my PR but did not post any inline comments."
  }'
```

### Response

Returns a confirmation object acknowledging receipt of your query.

<ResponseField name="queryId" type="string">
  A unique identifier assigned to your support query. Keep this for reference if you need to follow up.
</ResponseField>

<ResponseField name="status" type="string">
  Always `"received"` on a successful submission, confirming that your query has been accepted and will be reviewed by the BugViper team.
</ResponseField>

<Tip>
  If you're reporting a bug, include as much detail as possible in the `message` field — the repository name, the PR number, the exact bot command you used, and any error messages visible in the PR comments. This helps the BugViper team reproduce and resolve the issue faster.
</Tip>