Panda Video General Analytics API
Operations for general analytics metrics
Operations for general analytics metrics
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/pandavideo-com:pandavideo-com-general-analytics-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Panda Analytics General Analytics API
description: 'API for analytics data in the Panda platform.
This API allows you to:
- Retrieve real-time analytics data
- Access general analytics metrics
- Get retention analytics
- View ranking data
- Analyze geographic data (city/region)
- Access live streaming analytics
- Get billing and usage data
- Filter analytics by type'
version: 1.0.0
contact:
name: Panda Team
email: support@panda.video
servers:
- url: https://data.pandavideo.com
description: Production server
- url: http://localhost:8001
description: Local development server
tags:
- name: General Analytics
description: Operations for general analytics metrics
paths:
/general:
get:
summary: Get general analytics for account
description: 'Retrieves views, plays and unique metrics for the authenticated user''s account, per day.
**Time window and time zone**
- `start_date` and `end_date` accept `YYYY-MM-DD` or `YYYY-MM-DDTHH:00` (minutes must be `00`).
- The window is `[start, end)`. A date without an hour covers the whole day: `start_date=2026-10-20&end_date=2026-10-20` returns all of October 20.
- `timezone` (IANA, e.g. `America/Sao_Paulo`) defines how the dates are read and how days and hours are labeled in the response. Without `timezone` and without hours in the dates, days and hours are in UTC (same response as before).
- Unique metrics over a window are the sum of the unique metrics of each hour: a viewer who comes back in different hours is counted once per hour.
- Returns `400` for an invalid time zone, a time zone with a non whole-hour UTC offset (e.g. `Asia/Kolkata`), minutes other than `00`, or `end_date` not after `start_date`.
**Most recent data**: with `timezone` (or hours in the dates) the current day is included up to the last closed hour (hourly processing at minute 5 of each hour, UTC). Without `timezone`, data goes up to the previous day, available after the daily processing at 00:30 UTC.'
tags:
- General Analytics
security:
- PandaAuth: []
parameters:
- name: start_date
in: query
required: false
description: 'Start of the window: `YYYY-MM-DD` (start of the day) or `YYYY-MM-DDTHH:00`, in `timezone`.'
schema:
type: string
pattern: ^\d{4}-\d{2}-\d{2}(T\d{2}:00)?$
example: '2026-10-20'
- name: end_date
in: query
required: false
description: 'End of the window, exclusive: `YYYY-MM-DDTHH:00` stops right before that hour; `YYYY-MM-DD` includes the whole day. Read in `timezone`.'
schema:
type: string
pattern: ^\d{4}-\d{2}-\d{2}(T\d{2}:00)?$
example: '2026-10-21'
- name: timezone
in: query
required: false
description: IANA time zone used to read `start_date`/`end_date` and to label days and hours in the response (e.g. `America/Sao_Paulo`, `America/New_York`, `UTC`). When omitted and the dates have no hour, everything is in UTC.
schema:
type: string
example: America/Sao_Paulo
responses:
'200':
description: General analytics data retrieved successfully
content:
application/json:
schema:
$ref: '#/components/schemas/GeneralAnalytics'
examples:
OK:
summary: OK
value:
views_data:
'2026-10-20':
play: 503
view: 2567
unique_play: 301
unique_view: 1290
total:
play: 503
view: 2567
unique_play: 301
unique_view: 1290
timezone: America/Sao_Paulo
'400':
$ref: '#/components/responses/BadRequestError'
'401':
$ref: '#/components/responses/UnauthorizedError'
'500':
$ref: '#/components/responses/InternalServerError'
operationId: getGeneral
x-operation-id-source: derived
/general/hour/videos:
get:
summary: Get hourly metrics for selected videos
description: 'Hourly metrics for a list of videos, identified by `video_external_id`. Same response as `/general/hour`, filtered to the given videos. Use POST for long lists (up to 2000 IDs).
**Time window and time zone**
- `start_date` and `end_date` accept `YYYY-MM-DD` or `YYYY-MM-DDTHH:00` (minutes must be `00`).
- The window is `[start, end)`. A date without an hour covers the whole day: `start_date=2026-10-20&end_date=2026-10-20` returns all of October 20.
- `timezone` (IANA, e.g. `America/Sao_Paulo`) defines how the dates are read and how days and hours are labeled in the response. Without `timezone` and without hours in the dates, days and hours are in UTC (same response as before).
- Unique metrics over a window are the sum of the unique metrics of each hour: a viewer who comes back in different hours is counted once per hour.
- Returns `400` for an invalid time zone, a time zone with a non whole-hour UTC offset (e.g. `Asia/Kolkata`), minutes other than `00`, or `end_date` not after `start_date`.
**Most recent data**: with `timezone` (or hours in the dates) the current day is included up to the last closed hour (hourly processing at minute 5 of each hour, UTC). Without `timezone`, data goes up to the previous day, available after the daily processing at 00:30 UTC.'
operationId: get_general_hour_videos
tags:
- General Analytics
security:
- PandaAuth: []
parameters:
- name: start_date
in: query
required: true
description: 'Start of the window: `YYYY-MM-DD` (start of the day) or `YYYY-MM-DDTHH:00`, in `timezone`.'
schema:
type: string
pattern: ^\d{4}-\d{2}-\d{2}(T\d{2}:00)?$
example: '2026-10-20'
- name: end_date
in: query
required: true
description: 'End of the window, exclusive: `YYYY-MM-DDTHH:00` stops right before that hour; `YYYY-MM-DD` includes the whole day. Read in `timezone`.'
schema:
type: string
pattern: ^\d{4}-\d{2}-\d{2}(T\d{2}:00)?$
example: '2026-10-21'
- name: timezone
in: query
required: false
description: IANA time zone used to read `start_date`/`end_date` and to label days and hours in the response (e.g. `America/Sao_Paulo`, `America/New_York`, `UTC`). When omitted and the dates have no hour, everything is in UTC.
schema:
type: string
example: America/Sao_Paulo
- name: videos
in: query
required: true
description: Comma-separated `video_external_id` list.
schema:
type: string
example: 07c8153a-fb76-43a8-bfe3-15280d9783ae,3b101f05-84aa-4de0-9b64-71f1855388af
responses:
'200':
description: Hourly metrics for the selected videos
content:
application/json:
schema:
type: object
properties:
views_data:
type: object
description: Hourly rows keyed by day (`YYYY-MM-DD`, in `timezone`).
additionalProperties:
type: array
items:
type: object
properties:
id:
type: string
description: Video external ID (`video_external_id`)
hour:
type: integer
description: Hour of the day (0-23), in `timezone`
view:
type: integer
play:
type: integer
unique_view:
type: integer
unique_play:
type: integer
aggregated_data:
type: object
description: Totals per day and 2-hour bucket (`0-2` ... `22-00`), in `timezone`.
additionalProperties:
type: object
additionalProperties:
type: object
properties:
total_view:
type: integer
total_play:
type: integer
total_unique_view:
type: integer
total_unique_play:
type: integer
timezone:
type: string
description: Time zone used for the window and the keys. Only present when `timezone` or hours were sent.
example: America/Sao_Paulo
examples:
OK:
summary: OK
value:
views_data:
'2026-10-20':
- id: 07c8153a-fb76-43a8-bfe3-15280d9783ae
hour: 20
view: 90
play: 12
unique_view: 41
unique_play: 8
aggregated_data:
'2026-10-20':
20-22:
total_view: 90
total_play: 12
total_unique_view: 41
total_unique_play: 8
timezone: America/Sao_Paulo
'400':
description: Invalid videos list, time window or time zone
content:
application/json:
schema:
type: object
properties:
error:
type: string
examples:
missing videos:
value:
error: videos query parameter is required
'401':
$ref: '#/components/responses/UnauthorizedError'
post:
summary: Get hourly metrics for selected videos (POST)
description: 'Hourly metrics for a list of videos, identified by `video_external_id`. Same response as `/general/hour`, filtered to the given videos. Use POST for long lists (up to 2000 IDs).
**Time window and time zone**
- `start_date` and `end_date` accept `YYYY-MM-DD` or `YYYY-MM-DDTHH:00` (minutes must be `00`).
- The window is `[start, end)`. A date without an hour covers the whole day: `start_date=2026-10-20&end_date=2026-10-20` returns all of October 20.
- `timezone` (IANA, e.g. `America/Sao_Paulo`) defines how the dates are read and how days and hours are labeled in the response. Without `timezone` and without hours in the dates, days and hours are in UTC (same response as before).
- Unique metrics over a window are the sum of the unique metrics of each hour: a viewer who comes back in different hours is counted once per hour.
- Returns `400` for an invalid time zone, a time zone with a non whole-hour UTC offset (e.g. `Asia/Kolkata`), minutes other than `00`, or `end_date` not after `start_date`.
**Most recent data**: with `timezone` (or hours in the dates) the current day is included up to the last closed hour (hourly processing at minute 5 of each hour, UTC). Without `timezone`, data goes up to the previous day, available after the daily processing at 00:30 UTC.'
operationId: post_general_hour_videos
tags:
- General Analytics
security:
- PandaAuth: []
parameters: []
responses:
'200':
description: Hourly metrics for the selected videos
content:
application/json:
schema:
type: object
properties:
views_data:
type: object
description: Hourly rows keyed by day (`YYYY-MM-DD`, in `timezone`).
additionalProperties:
type: array
items:
type: object
properties:
id:
type: string
description: Video external ID (`video_external_id`)
hour:
type: integer
description: Hour of the day (0-23), in `timezone`
view:
type: integer
play:
type: integer
unique_view:
type: integer
unique_play:
type: integer
aggregated_data:
type: object
description: Totals per day and 2-hour bucket (`0-2` ... `22-00`), in `timezone`.
additionalProperties:
type: object
additionalProperties:
type: object
properties:
total_view:
type: integer
total_play:
type: integer
total_unique_view:
type: integer
total_unique_play:
type: integer
timezone:
type: string
description: Time zone used for the window and the keys. Only present when `timezone` or hours were sent.
example: America/Sao_Paulo
examples:
OK:
summary: OK
value:
views_data:
'2026-10-20':
- id: 07c8153a-fb76-43a8-bfe3-15280d9783ae
hour: 20
view: 90
play: 12
unique_view: 41
unique_play: 8
aggregated_data:
'2026-10-20':
20-22:
total_view: 90
total_play: 12
total_unique_view: 41
total_unique_play: 8
timezone: America/Sao_Paulo
'400':
description: Invalid videos list, time window or time zone
content:
application/json:
schema:
type: object
properties:
error:
type: string
examples:
missing videos:
value:
error: videos query parameter is required
'401':
$ref: '#/components/responses/UnauthorizedError'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- videos
- start_date
- end_date
properties:
videos:
type: array
maxItems: 2000
items:
type: string
description: '`video_external_id` list (up to 2000).'
start_date:
type: string
pattern: ^\d{4}-\d{2}-\d{2}(T\d{2}:00)?$
example: '2026-10-20'
end_date:
type: string
pattern: ^\d{4}-\d{2}-\d{2}(T\d{2}:00)?$
example: '2026-10-21'
timezone:
type: string
example: America/Sao_Paulo
/general/{videoId}:
get:
summary: Get general analytics for specific video
description: 'Retrieves views, plays and unique metrics for a specific video, per hour.
**Time window and time zone**
- `start_date` and `end_date` accept `YYYY-MM-DD` or `YYYY-MM-DDTHH:00` (minutes must be `00`).
- The window is `[start, end)`. A date without an hour covers the whole day: `start_date=2026-10-20&end_date=2026-10-20` returns all of October 20.
- `timezone` (IANA, e.g. `America/Sao_Paulo`) defines how the dates are read and how days and hours are labeled in the response. Without `timezone` and without hours in the dates, days and hours are in UTC (same response as before).
- Unique metrics over a window are the sum of the unique metrics of each hour: a viewer who comes back in different hours is counted once per hour.
- Returns `400` for an invalid time zone, a time zone with a non whole-hour UTC offset (e.g. `Asia/Kolkata`), minutes other than `00`, or `end_date` not after `start_date`.
**Most recent data**: includes the current day.'
tags:
- General Analytics
security:
- PandaAuth: []
parameters:
- name: videoId
in: path
required: true
description: Unique identifier of the video
schema:
type: string
- name: start_date
in: query
required: false
description: 'Start of the window: `YYYY-MM-DD` (start of the day) or `YYYY-MM-DDTHH:00`, in `timezone`.'
schema:
type: string
pattern: ^\d{4}-\d{2}-\d{2}(T\d{2}:00)?$
example: '2026-10-20'
- name: end_date
in: query
required: false
description: 'End of the window, exclusive: `YYYY-MM-DDTHH:00` stops right before that hour; `YYYY-MM-DD` includes the whole day. Read in `timezone`.'
schema:
type: string
pattern: ^\d{4}-\d{2}-\d{2}(T\d{2}:00)?$
example: '2026-10-21'
- name: timezone
in: query
required: false
description: IANA time zone used to read `start_date`/`end_date` and to label days and hours in the response (e.g. `America/Sao_Paulo`, `America/New_York`, `UTC`). When omitted and the dates have no hour, everything is in UTC.
schema:
type: string
example: America/Sao_Paulo
- name: granularity
in: query
required: false
description: '`total` returns only `total` (no `views_data`).'
schema:
type: string
enum:
- total
responses:
'200':
description: Video analytics data retrieved successfully
content:
application/json:
schema:
$ref: '#/components/schemas/VideoAnalytics'
examples:
OK:
summary: OK
value:
views_data:
2026-10-20 20:00:
play: 12
view: 90
unique_play: 8
unique_view: 41
total:
play: 12
view: 90
unique_play: 8
unique_view: 41
timezone: America/Sao_Paulo
'400':
$ref: '#/components/responses/BadRequestError'
'404':
$ref: '#/components/responses/NotFoundError'
operationId: getGeneralByVideoId
x-operation-id-source: derived
components:
responses:
BadRequestError:
description: Invalid time window or time zone
content:
application/json:
schema:
type: object
properties:
errMsg:
type: string
examples:
invalid timezone:
value:
errMsg: timezone "Foo/Bar" is not a valid IANA timezone (e.g. America/Sao_Paulo)
minutes:
value:
errMsg: start_date must be on the hour (minutes must be 00)
NotFoundError:
description: Not found - Resource does not exist
content:
application/json:
schema:
type: object
properties:
error:
type: string
example: Resource not found
UnauthorizedError:
description: Unauthorized - Invalid or missing authentication
content:
application/json:
schema:
type: object
properties:
error:
type: string
example: Authentication required
InternalServerError:
description: Internal server error
content:
application/json:
schema:
type: object
properties:
error:
type: string
example: Internal server error
schemas:
VideoAnalytics:
type: object
properties:
views_data:
type: object
description: Metrics per hour (`YYYY-MM-DD HH:00`, in `timezone`).
additionalProperties:
$ref: '#/components/schemas/Metrics'
total:
$ref: '#/components/schemas/Metrics'
timezone:
type: string
description: Time zone used for the window and the keys. Only present when `timezone` or hours were sent.
example: America/Sao_Paulo
Metrics:
type: object
properties:
play:
type: integer
example: 12
view:
type: integer
example: 90
unique_play:
type: integer
example: 8
unique_view:
type: integer
example: 41
GeneralAnalytics:
type: object
properties:
views_data:
type: object
description: Metrics per day (`YYYY-MM-DD`, in `timezone`).
additionalProperties:
$ref: '#/components/schemas/Metrics'
total:
$ref: '#/components/schemas/Metrics'
timezone:
type: string
description: Time zone used for the window and the keys. Only present when `timezone` or hours were sent.
example: America/Sao_Paulo
securitySchemes:
PandaAuth:
type: apiKey
in: header
name: Authorization
description: Panda API token (without Bearer prefix)
x-provenance:
method: searched
source: https://docs.pandavideo.com/reference
harvested: '2026-11-20'
tool: harvest-readme-openapi.py
note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
assembled_from:
- https://docs.pandavideo.com/reference/analytics-general.md
- https://docs.pandavideo.com/reference/analytics-retention.md
- https://docs.pandavideo.com/reference/get_city-videoid.md
- https://docs.pandavideo.com/reference/get_city.md
- https://docs.pandavideo.com/reference/get_general-videoid.md
- https://docs.pandavideo.com/reference/get_general_hour_videos.md
- https://docs.pandavideo.com/reference/get_live-liveid.md
- https://docs.pandavideo.com/reference/get_live.md
- https://docs.pandavideo.com/reference/get_ranking-1.md
- https://docs.pandavideo.com/reference/get_ranking_unwatched.md
- https://docs.pandavideo.com/reference/get_region-videoid.md
- https://docs.pandavideo.com/reference/get_region.md
- https://docs.pandavideo.com/reference/get_retention-videoid.md
- https://docs.pandavideo.com/reference/get_type-videoid.md
- https://docs.pandavideo.com/reference/get_type.md
- https://docs.pandavideo.com/reference/get_users.md
- https://docs.pandavideo.com/reference/post_general_hour_videos.md
merge:
pages: 17
deduped: 24
conflicts_kept_first: 0