Skip to content

Submit Document Feedback

POST
/global-context/documents/{doc_id}/feedback

Thumbs up or down on a document.

usage_id attaches the feedback to a specific USE of the document rather than to the document itself, which is what makes “this answer was wrong” distinguishable from “this document is wrong”.

Authorizations

Parameters

Path Parameters

doc_id
required

Document id.

string

Document id.

Header Parameters

X-Target-Org-Id
Any of:
string

Request Body required

Mirrors campaign_builder.routers.global_context.FeedbackRequest.

feedback_type is a Literal where the app takes str and rejects anything but up/down from inside the handler.

object
feedback_type
required

Thumbs up or thumbs down on the document.

string
Allowed values: up down
usage_id
Any of:
string

Responses

201

Successful Response

object
data
required

An open envelope for one settings block, document or brand artefact.

OPEN on purpose. These surfaces are configuration and generated content, and both grow: a new toggle on a settings block or a new field on a generated document must reach a caller on the day it ships, not on the day somebody remembers to widen a mirror. A closed response model here would silently DROP the new key, which reads to the caller as “the product does not have that setting”.

The request side is the opposite and is mirrored exactly - see the module docstring for why the asymmetry is deliberate.

object
key
additional properties
any
pagination
Any of:
object
has_next
required

Whether there are more pages

boolean
limit
required

Items per page

integer
next_cursor
Any of:
string
page
required

Current page number (1-indexed)

integer
total
required

Total number of items

integer

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string