---
title: "Send a support message to the Grove team"
method: POST
path: "/v1/support/contact"
tags: ["support"]
---

# Send a support message to the Grove team

`POST /v1/support/contact`

Send a support message directly to the Grove team from authenticated clients.

**Purpose:**
This endpoint enables CLI tools, SDKs, and extensions to submit support requests
without requiring users to configure local email clients or navigate to a web form.

**Authentication:**
Requires a valid JWT token in the `Authorization: Bearer <token>` header.
The account ID is automatically extracted from the token for context.

**Delivery:**
- Email delivery is fire-and-forget (non-blocking)
- Returns immediately with a ticket ID for tracking
- If email is disabled, returns status "disabled" so clients can fallback to alternative methods

**Client Metadata:**
The optional `metadata` field should include diagnostic information like:
- CLI/SDK version
- Operating system and version
- API endpoint being used
- Any relevant error codes or states

This helps the support team provide faster, more accurate assistance.

## Headers

- `authorization` string, nullable
- `user-agent` string, nullable
- `host` string, nullable

## Request body

- SupportContactRequest — Request model for POST /v1/support/contact. Auth required (Authorization: Bearer <JWT>).
  - `message` string, required — Message to the Grove team
  - `subject` string, nullable — Optional subject line override
  - `reply_to` string, nullable — Optional contact info for replies (email, URL, handle, etc.)
  - `metadata` object, nullable — Optional client metadata for debugging (e.g., CLI version, OS, API URL)

## Response `200`

Request accepted (check status field for actual delivery state)

- SupportContactResponse — Response model for POST /v1/support/contact.
  - `ticket_id` string, required — Support ticket identifier (include this when following up)
  - `status` string, required — Delivery status (queued when forwarded; disabled when support messaging is not configured)

## Other responses

- `401` — Authentication failed (invalid or missing JWT token)
- `422` — Validation Error

---

[API](https://skmtc.net/grove/apis/grove-api.md) · [All operations](https://skmtc.net/grove/apis/grove-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/grove/grove-api/revisions/f286b48a8105/schema)