# Feedback

Reference for POST /v1/feedback, POST /v1/bug-reports and the public POST /v1/api-requests. Report problems, send feedback and ask for APIs that are missing.

Reports reach the team directly and never cost anything. Never put an API key or other secrets in a message.

## POST /v1/feedback

`POST https://api.primaryapi.com/v1/feedback`

Auth: Any API key (full, run or view), or a dashboard session

| Field | Type | Required | Description |
|---|---|---|---|
| `kind` | string | yes | `bug`, `feedback` or `api_request`. |
| `message` | string | yes | 3–4,000 characters, in plain words. |
| `requestId` | string | no | The `req_…` id of the call concerned. |
| `sku` | string | no | The API concerned. |

```bash
curl -sS -X POST "https://api.primaryapi.com/v1/feedback" \
  -H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"kind":"feedback","message":"The followers count for private profiles would help even when posts are hidden.","sku":"instagram.profile"}'
```

**201 Created**: a receipt, `{ "id": "fbk_…", "kind": "feedback", "received": true, "createdAt": "…" }`.

## POST /v1/bug-reports

`POST https://api.primaryapi.com/v1/bug-reports`

Auth: Any API key (full, run or view), or a dashboard session

The same body as `/v1/feedback`, always stored as a bug (`kind` may be left out). Include the `requestId` so we can look at exactly what happened:

```json
{ "message": "output.data.score is a string, the schema says number.", "requestId": "req_01JBXK6Y2N9V8T4R3Q2P1M0A7Z", "sku": "email.verify" }
```

## POST /v1/api-requests

`POST https://api.primaryapi.com/v1/api-requests`

Auth: None (rate limited per IP address)

Ask for an API that is not in the catalog yet. No account needed.

| Field | Type | Required | Description |
|---|---|---|---|
| `sku` | string | one of `sku` or `name` | The SKU you would expect, for example `tiktok.comments`. |
| `name` | string | one of `sku` or `name` | The API in words, for example "TikTok video comments". |
| `message` | string | yes | 3–4,000 characters: what data you need and what for. |
| `email` | string | no | Where we can tell you when it ships. |

```bash
curl -sS -X POST "https://api.primaryapi.com/v1/api-requests" \
  -H "Content-Type: application/json" \
  -d '{"name":"Threads post replies","message":"Replies with author, text, likes and timestamp for a post URL. About 50k calls a month.","email":"dev@example.com"}'
```

**201 Created**: a receipt as above. Errors: `400 invalid_input` (neither `sku` nor `name`, or a message that is too short), `429 rate_limited` when one network sends too many requests.

Agents connected to the [MCP server](/docs/mcp-server) can do the same with the `report_bug` and `send_feedback` tools.
