Flagging
Account-initiated review flagging — create a flag, check status, read history, fetch the reason catalogue.
Account-initiated review flagging — create a flag, check status, read history, fetch the reason catalogue. Drives the partner-admin moderation queue.
Prerequisites
- A bearer token in the
Authorizationheader. Any endpoint that needs no token says so on its own page. - The id of each record the call targets. Every endpoint page lists the ids it needs.
Errors
| Status | Meaning |
|---|---|
401 | The bearer token is missing, expired or invalid |
403 | The token is valid but the record sits outside your account |
422 | The request failed validation — the response names the fields |
500 | Unexpected server error |
Individual endpoints may return more; each page lists its own.
Endpoints
POST — Submit (or re-submit, while still pending) a flag against the review identified by the URL {id}, persisting a ReviewFlag row with status pending, writing an audit log and a per-review history event, and consuming the review_flag plan-feature quota.
GET — Get the current flag on a review, or a none state when the review has never been flagged.
GET — Paginated list of review flags whose review belongs to a store the authenticated user can access, newest flag first.
Updated 11 days ago