GET /general/{video_id}

Returns per‑video view / play counts within a date range. Used by the A/B Testing UI to render the Plays Rate chart for each variant in a comparison — but the endpoint itself is generic and works for any video.

📘

Different host: data.pandavideo.com

Analytics endpoints (this one and A/B Test Retention) live on https://data.pandavideo.com, not on api-v2.pandavideo.com.br. Keep this distinct when configuring environments.

📘

Authorization

Requires a valid API Key in the Authorization header. Send the key directly — no Bearer prefix.

HTTP Method & Path

GET /general/{video_id}?type=video&start_date=<YYYY-MM-DD>&end_date=<YYYY-MM-DD>

Base URL: https://data.pandavideo.com

Path Parameters

Query Parameters

Response

Success Response (200)

{
  "total": {
    "view": 1240,
    "unique_view": 980,
    "unique_play": 720,
    "play": 1310
  },
  "views_data": {
    "2025-01-15": { "play": 100, "unique_view": 80, "view": 110 },
    "2025-01-16": { "play": 130, "unique_view": 105, "view": 140 }
  }
}

Response Schema

📘

Plays Rate computation. The dashboard derives the variant's plays‑rate as unique_play / unique_view over the same window. Apply the same ratio per views_data entry for a daily series.

Error Responses

• 400 — invalid start_date / end_date / type.
• 401 — missing/invalid API Key.
• 404 — video not found.
• 500 — internal error.

Example Usage

cURL

curl --request GET \
  --url 'https://data.pandavideo.com/general/f1f2f3f4-aaaa-bbbb-cccc-d1d2d3d4d5d6?type=video&start_date=2025-01-15&end_date=2025-01-22' \
  --header 'Authorization: <your-api-key>'

Recipes