List Review Response Drafts Route
The Responses tab’s drafts for one brand, scoped to one platform.
Registered AFTER the /reviews/{review_id}/draft-response POST and the
/reviews/drafts/{draft_id} PATCHes but that ordering is incidental —
no other GET on this router takes a path segment after /reviews, so
drafts cannot be swallowed as a {review_id}.
Authorization: _get_brand_or_404 proves the caller owns brand_id;
the service then joins every row through that brand’s OWN advertiser
identity, so a competitor-sourced review’s draft is unreachable here even
if one somehow existed. Platform scoping is a predicate on the review’s
source, not a client-side filter — see
list_review_response_drafts’s docstring for why each of its three
predicates is load-bearing.
No entitlement METER: listing drafts generates nothing and calls no provider, and metering a read would charge a user for opening a tab. It does carry the Responses-tab capability LOCK — a different question (“is this tab on your plan”), Free on every plan today (design §0.5).
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Query Parameters
trustpilot, google 1 <= x <= 100x >= 0Response
Successful Response
The Responses tab's page of drafts for one brand on one platform.
Envelope mirrors BrandReviewsResponse (total/limit/offset/has_more) so
the workspace pages drafts with the same vocabulary it already pages
reviews with. platform echoes the filter that produced the page —
absent means "every platform", which the tab never asks for but the route
supports.