Statistics

Notice

This document is a machine-translated draft and is currently undergoing review. Some content may be inaccurate or differ from the original Korean version. For the most precise information, refer to the Korean documentation.

Go to Statistics API v3 Reference→

Feature scope by version

• v1 not supported: v1 does not support statistics-related features.
• Common authentication: APIs of all versions use the common authentication method via a query string parameter (?access_token=). For the common specification on error determination criteria, refer to the Core Changes section of the API v3 migration guide.

---

Get overall content view ranking

• Previous (v1/v2): Not supported
• Changed (v3): GET /statistics/content-rank

Exception structure for top-level response key

Unlike most v3 APIs, this endpoint uses result_data as the top-level key. If a common API response parser is applied to your client application, data may be lost, so exception handling must be implemented.

Request parameters and response structure details

Request query parameters

Parameter	Data type	Required	Description
start_date	String	Required	Start date of the query range (YYYYMMDD)
end_date	String	Required	End date of the query range (YYYYMMDD)
keyword	String	Optional	Filter by search keyword
start_index	Integer	Optional	Starting number of the result list
limit	Integer	Optional	Maximum number of output data items (0: query all data)

Response structure specification

{
  "result_data": [
    {
      "avg_play_rate": 85.5,
      "avg_uplay_rate": 80.2,
      "category_id": 10,
      "channel_key": "channel_key_string",
      "content_id": 1,
      "title": "top1_content_title",
      "upload_time": "2025-12-22 01:28:39",
      "upload_key": "upload_key_string",
      "duration": 3600,
      "count": 500,
      "play_count": 450
    }
  ]
}

---

Get content view ranking within a channel

• Previous (v1/v2): Not supported
• Changed (v3): GET /channels/{channel_key}/statistics/content-rank

Exception structure for top-level response key

Unlike most v3 APIs, this endpoint uses result_data as the top-level key. If a common API response parser is applied to your client application, data may be lost, so exception handling must be implemented.

Request parameters and response structure details

Request parameters

• Path parameter: The channel_key (required) that specifies the target channel must be included in the URL.
• Query parameters: Uses the exact same parameter spec (start_date, end_date, keyword, start_index, limit) as the Get overall content view ranking API.

Response structure specification

The response spec is exactly the same as that of Get overall content view ranking.

---

Get daily statistics

• Previous (v1): Not supported
• Previous (v2): GET /vod/statistics/summary-daily
• Changed (v3): GET /statistics/summary-daily

Changes

The /vod prefix has been removed from the endpoint path. The request query parameters and response structure remain the same as the v2 specification.

Request parameters and response structure details

Request query parameters

Parameter	Data type	Required	Description
start_date	String	Required	Start date of the query range (YYYYMMDD)
end_date	String	Required	End date of the query range (YYYYMMDD)

Response structure specification

{
  "data": [
    {
      "startdate": "20231001",
      "enddate": "20231031",
      "total_transfer": 1024000,
      "max_traffic": 5000,
      "total_storage": 2048000,
      "max_storage": 2100000,
      "total_transcoding_size": 512000,
      "total_transcoding_count": 150,
      "total_visitor": 3500,
      "daily_data": [
        {
          "datetime": "20231001",
          "transfer": 30000,
          "traffic": 150,
          "storage": 2000000,
          "transcoding_size": 15000,
          "transcoding_count": 5,
          "visitor": 120
        }
      ]
    }
  ]
}