API reference

Pre-moderation reviews

POST /v1/reviews and GET /v1/reviews/{reviewId} — have content checked before you publish it.

A review request asks moderators to check content before you publish it (pre-moderation), e.g. profile photos, listings or usernames. The dashboard calls these queues Approvals. Do not confuse them with store reviews, the ratings of your app in the app stores.

Setup

  • Create the review types (codes) per app in the dashboard: tab Moderation, approval types. A type has a code, a name, guidelines for moderators, a target time (default 60 minutes, which sets dueAt), whether the outcome restricted is allowed, and the policies a rejection can be based on.
  • Requires a plan with reviews. Copies of approved content are deleted after 30 days by default.

POST /v1/reviews

Shell
curl -sS -X POST "$LIMENIA_BASE_URL/v1/reviews" \
  -H "Authorization: Bearer $LIMENIA_API_KEY" -H "Content-Type: application/json" \
  -H "Idempotency-Key: review-upload_881" \
  -d '{"type":"profile_photo","externalReviewId":"upload_881","subject":{"externalUserId":"u_112"},"content":{"externalContentId":"photo_881","contentType":"image","media":[{"url":"https://storage.example.com/signed/photo_881.jpg?sig=…"}]}}'

Response 201 Created: { "reviewId": "01K6T2…", "status": "pending", "dueAt": "2026-10-03T10:00:00Z" }. Until the result, show the content only to its author (“being reviewed”).

Field Required Meaning
type yes Code of an active review type of the app, ^[a-z0-9_]{2,40}$
content yes Same format and limits as for reports
subject recommended The author, from your login, same format as in reports, including identifiers (see Identifiers). Without it the decision belongs to no user.
externalReviewId no Your ID, 1 to 128 characters; comes back in review.decided
  • Every request is reviewed on its own (no bundling). A revised version may keep the externalContentId; each request gets its own copy.
  • Media are downloaded as for reports. If you send every upload for review, mind the rate limit (10/s) and queue spikes.
  • Your app must handle approved, rejected and, if the type allows it, restricted, regardless of the supported actions.

Errors: 400 validation_failed, review_type_unknown (type unknown or inactive, field /type); 401; 402 subscription_required (do not publish unreviewed; submit again later); 403 feature_not_in_plan, tenant_not_active; 409 idempotency_key_reused; 429.

GET /v1/reviews/{reviewId}

Status of a review request; the fallback if review.decided was missed (e.g. for requests long past dueAt).

JSON
{
  "id": "01K6T2…",
  "externalReviewId": "upload_881",
  "type": "profile_photo",
  "status": "decided",
  "submittedAt": "2026-10-03T09:00:00Z",
  "outcome": "rejected",
  "decidedAt": "2026-10-03T09:12:00.098765Z",
  "decisionId": "01K6T3…"
}

status: pending, in_review, decided. outcome (approved, restricted, rejected) and decidedAt only when decided; decisionId only with restricted and rejected. The statement of reasons comes with decision.created. A review is decided once; a later complaint does not change this response. Errors: 401, 404, 429.

Outcomes

Results arrive as review.decided (see Webhook events). Publish only then:

outcome What your app does
approved Publish. No decision.created and no statement of reasons follow.
restricted Publish with a restriction (e.g. adults only, blurred). The decision with restrict_content follows as decision.created; show its statement of reasons to the author.
rejected Do not publish. The decision with reject_submission follows as decision.created; show its statement of reasons. The author can complain.

Decisions on review requests never change the account of the author.