> ## Documentation Index
> Fetch the complete documentation index at: https://6f524b4-productmetrics.manicule.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://6f524b4-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://6f524b4-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://6f524b4-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Send feedback (/docs/api/account/feedback-send)

<!-- agent-signals: reading_time_min: 3 · est_tokens: 1440 · updated: 2026-11-16 -->
Related: [Create a checkout link](/docs/api/account/billing-create-checkout-link.md), [Create workspace](/docs/api/account/companies-create.md), [Get the Google connect link](/docs/api/account/google-get-connect-link.md), [Invite teammates](/docs/api/account/invitations-send.md), [Complete onboarding](/docs/api/account/onboarding-complete.md), [Get onboarding state](/docs/api/account/onboarding-get-state.md)

> Sends feedback about Product Metrics to the Product Metrics team: what is missing, confusing, wrong or slow, or what worked well.

`POST https://prod-backend.productmetrics.io/api/public/v1/feedback`

**Scope** `read` · **Access** Changes data · **Operation id** `feedback.send`

## Try it

`productmetrics` runs after `productmetrics login`; curl needs `PM_TOKEN` (see [Authentication](/docs/api/overview#authentication)).



**productmetrics CLI:**

```bash
productmetrics feedback send \
  --sentiment positive \
  --message 'Example message.' \
  --context 'Creating the conversion actions for Example Store.' \
  --json
```

**curl:**

```bash
curl -X POST "https://prod-backend.productmetrics.io/api/public/v1/feedback" \
  -H "Authorization: Bearer $PM_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "sentiment": "positive",
    "message": "Example message.",
    "context": "Creating the conversion actions for Example Store."
  }'
```

## Response

API response (200):

```json
{
  "data": {
    "received": true,
    "message": "Example message."
  },
  "request_id": "req_01J7424QHVF2578CP35Q7G14RT"
}
```

**CLI output:** `productmetrics feedback send --json` prints `{ "ok": true, "data": …, "request_id": "…" }` with the same `data`.

## Before you call

Send it when the person gives product feedback, or when you observe something concrete in Product Metrics that worked or failed (an operation, report or number you used, with the request id of a failed call). Do not report your own mistakes, the person's local environment, an unclear prompt, or an error you recovered from. Set actor "human" when passing on the person's own words and "agent" for your own observations; without actor it is recorded as the person's. This is not a support channel: no ticket is opened and nobody replies. For help, the person can email [support@productmetrics.io](mailto:support@productmetrics.io). Leave out personal data (names, email addresses, customer or order details). Any connection may send feedback: it needs only the read scope.

## Body

| Name        | Type   | Required | Description                                                                                                                                                                                                                                                                          |
| ----------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `sentiment` | enum   | Yes      | How the experience felt overall. One of `positive`, `neutral`, `negative`.                                                                                                                                                                                                           |
| `message`   | string | Yes      | What happened: what worked, what failed, or what is missing or confusing. Concrete: name the page, report or tool and what it did. 10 to 2000 characters.                                                                                                                            |
| `context`   | string | Yes      | What you or the user were trying to do. 10 to 2000 characters.                                                                                                                                                                                                                       |
| `feature`   | enum   | No       | The Product Metrics area the feedback is about; other when none fits. One of `google_ads`, `store_insights`, `products`, `segments`, `priorities`, `inventory`, `competitor_prices`, `product_context`, `integrations`, `tracking`, `billing`, `onboarding`, `mcp`, `docs`, `other`. |
| `actor`     | enum   | No       | human: the user's own words. agent: your own observation. One of `human`, `agent`.                                                                                                                                                                                                   |

## Errors

A failure answers with its HTTP status and `{ error: { code, message, details? }, request_id }`. Branch on `code` (stable, lower_snake); show `message` to the person. The CLI prints the same `error` with `"ok": false`.

```json
{
  "error": {
    "code": "insufficient_scope",
    "message": "This operation needs the read scope; connect again and allow it.",
    "details": {
      "required_scope": "read"
    }
  },
  "request_id": "req_01JM9B42CNZ1SBJS3P5GAWP0GA"
}
```

| Status | Code                 | When                                                                                                                      |
| ------ | -------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| 400    | `invalid_request`    | A path, query or body value does not match this page. `details.issues` lists each `location`, `path` and `message`.       |
| 401    | `invalid_token`      | The token is missing, expired or revoked: sign in again (`productmetrics login`). The `WWW-Authenticate` header says why. |
| 403    | `insufficient_scope` | The token lacks the `read` scope (`details.required_scope`): sign in again and allow it.                                  |
| 429    | `rate_limited`       | More than 600 requests a minute for this person: wait the `Retry-After` seconds (60) and retry.                           |

[All Account and onboarding operations](/docs/api/account)
