GET /feedback: Your feedback | distribution.tech

Overview

The feedback your brand sent, newest first, with its status (new, triaged, shipped, wont_fix); details and context only on the reports this key sent. Check it before sending so the same issue is not reported twice. limit is 1 to 50, 20 by default. Any valid key; no scope needed. MCP tool: feedback_list.

Endpoint: GET https://app.distribution.tech/api/v1/feedback
Scope: any valid key
Changes data: No, a read
MCP tool: feedback_list

Parameters

Parameters of GET /feedback
Name	In	Type	Required	Description
`limit`	query	integer	No

Request with curl

Set DISTRIBUTION_API_KEY to a key from Developers with the any valid key scope, and each path variable to an id from an earlier answer. The body carries the required fields.

curl

curl "https://app.distribution.tech/api/v1/feedback" \
  -H "Authorization: Bearer $DISTRIBUTION_API_KEY"

Response

200 OK. The body has these fields:

Response fields of GET /feedback
Name	Type	Required	Description
`feedback`	array of object	Yes

200 response body, every field with its type

{
  "feedback": [
    {
      "id": "<uuid>",
      "source": "mcp",
      "kind": "bug",
      "title": "<string>",
      "details": "<string>",
      "context": {
        "tool": "<string>",
        "request_id": "<string>",
        "url": "<string>",
        "error_code": "<string>",
        "status": 100
      },
      "status": "new",
      "created_at": "<date-time>"
    }
  ]
}

Errors

Error statuses of GET /feedback
Status	When
`400`	A parameter is not valid: details.problems names each field and what it accepts.
`401`	No API key, an unknown one, or a revoked one.
`429`	Too many requests for this key in the current minute (60); Retry-After and RateLimit-Reset say when to try again. On POST /campaigns and on POST /plans/current/lines when it starts a plan: the brand's 3 new campaigns in 24 hours are used (details.reason daily_campaign_limit); details.resets_at and Retry-After say when the limit reopens, a rolling 24 hours from the first of them, not a calendar day; archiving or deleting a campaign does not give its slot back. On GET /creators and GET /creators/{id}: a creator read limit is used (details.reason per_minute, daily_lists, daily_reveals, daily_seen or locked). daily_seen is your workspace's one pool of 300 creator views a day (300 different creators shown or opened since midnight UTC), shared by the app and every API key of the brand: details.scope workspace and details.limit 300; a creator already seen today, in the app or through any key, still opens and costs nothing. daily_lists is the day's list calls (each GET /creators page or creators_search is one; details.limit, 60): it is counted apart from creator views, resets at midnight UTC, and Retry-After says when. daily_reveals is the day's creator profiles opened (details.limit, 60). The other reasons are this key's own limit (details.scope key) or the brand's ceiling over all its keys (details.scope api).
`500`	internal: the request failed on our side. Try again.
`503`	unavailable: the service or this part of it is not reachable right now. Try again shortly.

POST /feedback: Send feedback

Get access

Keys are created in Developers once your brand is approved. Connect an agent to ask for access, then read the agent guide for the full flow.