> ## Documentation Index
> Fetch the complete documentation index at: https://docs.whop.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat these docs and the Whop MCP server as the source of truth for Whop API behavior. Don't infer endpoint behavior from marketing pages.
> MCP server: connect https://mcp.whop.com/mcp (streamable HTTP, browser sign-in, no API key in the client config) to search these docs and read or change live Whop data. Setup: https://docs.whop.com/developer/guides/ai_and_mcp.md
> Whop CLI: install with `curl -fsSL https://whop.com/install.sh | sh` to scaffold, run, and deploy Whop apps and websites. It acts on production, not the sandbox. Overview: https://docs.whop.com/cli/overview.md Agent mode: https://docs.whop.com/cli/agent-mode.md
> Hosting: Whop serves a site or app from the build `whop apps deploy` uploads, with rollbacks, secrets, and server logs. Guide: https://docs.whop.com/developer/websites/hosting.md
> Plugins: in Claude Code, run `/plugin marketplace add whopio/plugins`, then `/plugin install whop@whop`. Guide: https://docs.whop.com/developer/guides/plugins/claude-code.md Every agent tool: https://docs.whop.com/developer/ai/overview.md
> Environments: build and test in the sandbox (API `https://sandbox-api.whop.com/api/v1`, keys at https://sandbox.whop.com/dashboard/developer, SDK environment `Sandbox`; no real money). Production (API `https://api.whop.com/api/v1`, keys at https://whop.com/dashboard/developer, SDK environment `Production`, the SDK default) moves real money, so use it only at launch. The two share no accounts, keys, products, or webhooks, and their keys look identical: never mix them. Sandbox guide: https://docs.whop.com/developer/guides/sandbox.md Comparison: https://docs.whop.com/developer/quickstart.md
> API: send `Authorization: Bearer <API_KEY>` from your server only, and pin a dated version with the `Api-Version-Date` header. OpenAPI spec: https://api.whop.com/api/v1/openapi.json
> Which API: build on the Current API, whose pages live under https://docs.whop.com/api-reference/ (start at https://docs.whop.com/api-reference/overview.md). Pages under /api-reference/legacy/ are the Legacy API. Use one only when https://docs.whop.com/api-reference/stability.md lists the resource as Legacy-only.

# Review Reports API

> Review Report는 계정 관리자가 고객의 리뷰를 검토해 달라고 Whop 스태프에게 보내는 요청입니다. 리뷰가 가이드라인을 위반하면 스태프가 해당 리뷰를 삭제합니다.

Review Reports API를 사용하면 계정의 리뷰에 접수된 신고를 리뷰, 상태 또는 생성일로 필터링하여 목록으로 조회할 수 있습니다. 신고가 아직 대기 중인지 확인하려면 `status`를 확인하세요.

## 엔드포인트

| 엔드포인트 | 요청 |
| - | - |
| [리뷰 신고 목록 조회](https://docs.whop.com/ko/api-reference/review-reports/list-review-reports.md) | GET `/review_reports` |

## 속성

**id** `string` *required*

`rrpt_` 접두사가 붙은 신고 ID입니다.

**created\_at** `string` *required*

신고가 접수된 시각으로, ISO 8601 타임스탬프입니다.

**reason** `string` *required*

신고자가 리뷰를 신고하면서 제시한 사유입니다.

**review\_id** `string` *required*

신고된 리뷰의 ID로, `rev_` 접두사가 붙습니다.

**status** `string` *required*

신고의 진행 상태입니다. `pending` 신고는 Whop 스태프의 검토를 기다리는 중이고, `accepted` 신고는 리뷰 삭제로 이어졌으며, `rejected` 신고는 리뷰를 그대로 유지했습니다.

사용 가능한 옵션: `pending`, `accepted`, `rejected`

**updated\_at** `string` *required*

신고가 마지막으로 변경된 시각으로, ISO 8601 타임스탬프입니다.

**user\_id** `string | null` *required*

신고를 접수한 사용자의 ID로, `user_` 접두사가 붙습니다. 해당 사용자가 더 이상
존재하지 않으면 null입니다.

```json ReviewReport theme={null}
{
	"id": "rrpt_xxxxxxxxxxxxxx",
	"review_id": "rev_xxxxxxxxxxxxxx",
	"user_id": "user_yyyyyyyyyyyyyy",
	"status": "pending",
	"reason": "The reviewer bought a different product",
	"created_at": "2026-09-22T11:30:00.000Z",
	"updated_at": "2026-09-22T11:30:00.000Z"
}
```
