# List review queue

`GET /api/v1/review-queue`

The store's moderation queue: reviews held undecided, reviews already rejected, and the flags saying why each was held. This is the ONLY place on this API where a review that is not publicly visible appears. The two read_reviews lists serve approved rows only, in the SQL itself, so a held review is absent from them rather than merely unsorted, and no query parameter there could ever reach one. THESE ARE WORDS THE MERCHANT HAS NOT PUBLISHED, attached to a shopper's chosen display name, alongside a machine's judgement about them the shopper has never seen. Treat the body of a held review as unpublished content: do not syndicate it, do not show it to other customers, and do not assume rejecting it was a mistake. THERE IS NO DEFAULT FILTER. Omitting ?status= returns every status, which is what makes this usable for mirroring moderation state; pass ?status=pending for the queue proper. Only pending, approved and rejected are accepted, and anything else is a 400 rather than an empty page, so you cannot mistake a typo for an empty queue. IT BUYS DISCLOSURE, NOT AUTHORITY. Approving and rejecting is write_reviews, a different grant that this one does not imply and that does not imply this one; a tool that both shows the queue and clears it asks for both. Nothing here deletes a review, because that delete has no restore in any code path. NO MEDIA AND NO PRODUCT TITLE. The only media reader this platform has filters on approved reviews, so a held review's attachments are unreachable rather than empty, and product_id is flat because filling a nested reference would mean a join that silently drops a held review whose product was deleted, leaving it queued forever and invisible. Resolve the product through the products family. updated_at MEANS "LAST CHANGED", not "last moderated": a shopper editing their own review stamps it too.

## Query parameters

- `limit` (integer) — Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it.
- `after` (string) — The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page.

## Responses

- `200` — Success
- `400` — The request was refused before any state changed. `code` is one of:

`invalid_body`, a write body this route will not take. `reason` partitions it
and `field` names the key when one key is at fault.
`invalid_query`, a query parameter, including limit and after.
`invalid_text`, a NUL byte or bytes that are not valid UTF-8 anywhere in the
path, the query or the body. Strip control characters before sending.
`idempotency_key_required`, a write sent without the Idempotency-Key header.
`invalid_request`, an Idempotency-Key longer than 255 bytes.

Routes add their own codes for rules only they know. Switch with a default arm.
- `401` — No credential, or one this API does not accept. `code` is always
`unauthorized`.

THE BODY IS DELIBERATELY UNINFORMATIVE. An expired key, a revoked key, a
publishable key, a key belonging to another merchant and a key that never
existed are all refused with the same bytes, so this response cannot be used to
probe which keys exist. Check the key's state in the dashboard rather than
inferring it here.

Send the key as `Authorization: Bearer <key>` or as `X-API-Key: <key>`. It is
never accepted in a query string.
- `403` — The key lacks the read_review_moderation scope. `code` is `insufficient_scope` and the message names the scope to ask the merchant for.
- `429` — Too many requests. `code` is `rate_limited`.

Two limits apply independently: one on the credential and the route family,
one on the client address. The headers describe whichever has less left, so
honouring Retry-After always clears the window that bound.
- `default` — Any status this operation does not list, in the same envelope.

A 5xx means the request may or may not have applied. Retry it with the SAME
Idempotency-Key: that is the only way to find out without risking a duplicate,
and it is what the key is for.

A few 4xx conditions arrive here rather than as a listed status because they
depend on the merchant's plan or on a module being wired: 402 when a quota or a
plan limit is reached, and 503 when a capability the route needs is not
configured on this deployment. Both carry a `code` naming which.

## Example

```bash
curl --request GET \
  --url 'https://api.mercemur.com/api/v1/review-queue' \
  --header 'Authorization: Bearer <token>'
```