> ## 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.

# API 로그 레퍼런스

> API 로그는 계정의 API 키 중 하나를 사용해 Whop API에 보낸 단일 요청의 기록입니다. 로그인한 팀원이 수행한 작업만 기록하는 대시보드 감사 로그의 프로그래밍 방식 대응물입니다.

읽기 요청과 실패한 요청도 기록됩니다.

Api Logs API를 사용하면 통합이 Whop에서 무엇을 하고 있는지 확인할 수 있습니다. 각 요청의 작업, HTTP 메서드와 상태, 결과, 소요 시간을 최신순으로 보여줍니다.

## 엔드포인트

| 엔드포인트 | 요청 |
| - | - |
| [API 로그 목록 조회](https://docs.whop.com/ko/api-reference/api-logs/list-api-logs.md) | GET `/api_logs` |

## 속성

**id** `string` *required*

**api\_key\_id** `string | null`

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

**duration\_ms** `integer | null`

**http\_method** `string | null`

사용 가능한 옵션: `GET`, `POST`, `PUT`, `PATCH`, `DELETE`

**http\_path** `string | null`

**ip\_address** `string | null`

**operation\_name** `string | null`

**resource\_id** `string | null`

**status** `string | null`

사용 가능한 옵션: `success`, `error`

**status\_code** `integer | null`

**user\_agent** `string | null`

```json ApiLog theme={null}
{
	"id": "evt_xxxxxxxxxxxxxx_1",
	"api_key_id": "apik_xxxxxxxxxxxxxx",
	"operation_name": "api/v1/products#create",
	"http_method": "POST",
	"http_path": "/api/v1/products",
	"resource_id": "prod_xxxxxxxxxxxxxx",
	"status": "success",
	"status_code": 200,
	"duration_ms": 112,
	"ip_address": "87.106.27.99",
	"user_agent": "whop-sdk-node/1.4.0",
	"created_at": "2026-09-15T14:30:00.000Z"
}
```
