canonical: https://jentic.com/apis/analytics-metrics.jwplayer.com/jwplayer-analytics-metrics

# Analytics Metrics Jwplayer JW Player Analytics Metrics

JW Player Analytics Metrics is a video-analytics API exposed at analytics-metrics.jwplayer.com. The two GET endpoints return account-level and top-videos engagement metrics for a date window, scoped by an account token in the path. Authentication is via the x-api-key header. Typical consumers are publishers and OTT operators that already use the JW Player video platform and need programmatic access to playback metrics rather than the JW dashboard.

## For AI agents

Lets agents pull account-level and top-videos engagement metrics for a JW Player account between two dates, authenticated by the x-api-key header.

## Scope

Does not handle video upload, encoding, or playback control - use for JW Player account totals and top-videos analytics only.

## Capabilities

- Pull account-level video engagement metrics for a JW Player account between two dates
- Retrieve the top videos by engagement for a JW Player account in a date window
- Scope analytics calls by accounttoken so an agency can fetch metrics across multiple JW Player accounts
- Drive a publisher dashboard with daily account totals and top-content lists
- Roll up top-video performance over arbitrary date windows for editorial planning

## Use cases

### Publisher Editorial Dashboard

Online publishers using JW Player can build an in-house dashboard that pulls account totals and top-videos lists for the prior 24 hours, week, and month. The two-endpoint surface is enough to render the headline charts most editorial teams care about - total plays, top stories - without paying for a third-party BI integration. Most teams stand it up in a day.

Example prompt: Call GET `/v2/accounts/{accounttoken}/topvideos/start_date/2026-05-01/end_date/2026-05-07` and return the top 10 videos by engagement

### Agency Client Reporting

Video agencies managing multiple publishers' JW Player accounts can iterate over each accounttoken and pull the account totals plus the top videos for the reporting period. The integration replaces manual exports from the JW dashboard and feeds a templated client report with consistent metrics across accounts.

Example prompt: For each accounttoken in a client list, call GET `/v2/accounts/{accounttoken}/start_date/2026-05-01/end_date/2026-05-31` and write the account total to a CSV row

### Content Planning by Top Videos

Editorial and content teams can use the topvideos endpoint to identify which formats, talent, or topics drive engagement on JW Player. The agent pulls the top-N list weekly and surfaces titles or tags that consistently outperform, so commissioning decisions are grounded in JW playback data rather than vibes.

Example prompt: Call GET `/v2/accounts/{accounttoken}/topvideos/start_date/2026-04-01/end_date/2026-04-30` and return the title and engagement metric for the top five videos

### AI Agent Video Performance Lookups

Editorial copilots and exec briefing agents can query JW Player analytics through Jentic without storing the x-api-key in the agent context. The agent searches Jentic for an analytics intent, loads the operation schema, and Jentic injects the key at execution time. Useful for agents that summarise weekly publishing performance for an editor.

Example prompt: Search Jentic for 'get JW Player account totals', execute the operation with accounttoken='abc123' and the prior week's date range, and return the total plays figure

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v2/accounts/{accounttoken}/start_date/{start_date}/end_date/{end_date}` | Account-level engagement metrics for a date range |
| GET | `/v2/accounts/{accounttoken}/topvideos/start_date/{start_date}/end_date/{end_date}` | Top videos for an account by engagement |

## Key resources

- **Account Totals** — Account-level engagement metrics over a date window
- **Top Videos** — Top videos for an account by engagement over a date window

## Why Jentic

- **Setup:** Wiring the JW Player Analytics Metrics API by hand means managing the x-api-key header and threading the account token and date range through each path yourself. Through Jentic you install once, import JW Player Analytics Metrics from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** JW Player Analytics puts the account token in the URL path (`/accounts/{accounttoken}/...`), so a rule can pin your agent to one account: it can read totals and top videos for that account and nothing else. Because both operations are read-only reports, you scope the agent to the reads it needs.
- **Credential handling:** Your JW Player Analytics x-api-key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get account totals for a date range' or 'list top videos', and Jentic returns the matching JW Player Analytics operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mux** — Video infrastructure and quality-of-experience analytics for streaming platforms
- **Vimeo** — Hosted video platform with its own engagement and stats endpoints
- **Abstract API** — Time-zone and date utilities to normalise date ranges before analytics calls

## FAQ

### What authentication does the JW Player Analytics Metrics API use?

The API uses an API key sent in the x-api-key header on every request. There is no OAuth flow or signed-request scheme. Through Jentic, the x-api-key is stored encrypted in the vault and injected at execution time, so the agent never sees the raw key.

### Can I get top videos for a JW Player account through this API?

Yes. GET `/v2/accounts/{accounttoken}/topvideos/start_date/{start_date}/end_date/{end_date}` returns the top videos for the requested date window, scoped by accounttoken. The response includes the engagement metric the JW dashboard surfaces under the top-content view.

### What are the rate limits for the JW Player Analytics Metrics API?

The spec does not document rate limits. JW Player applies them per account, and agencies pulling metrics across many accounttokens have hit per-account caps in practice. Throttle to one request per second per account and back off on HTTP 429.

### How do I pull account totals through Jentic?

Search Jentic for 'get JW Player account totals'. Jentic returns the operation backed by GET `/v2/accounts/{accounttoken}/start_date/{start_date}/end_date/{end_date}`, you load the schema (accounttoken plus a start and end date), and execute. Jentic injects the x-api-key from the vault. Run it through Jentic One, the self-hosted execution layer.

### Does the Analytics Metrics API expose video upload or playback control?

No. This API is read-only and metrics-only. JW Player ships a separate management and delivery API for uploading, encoding, and serving video - those operations are not in this spec. Use this API only for reporting on JW Player engagement data.

### Are the start and end date format strict?

Yes. Both endpoints take start_date and end_date as path parameters and JW Player expects ISO-style YYYY-MM-DD values. Sending a non-standard format returns an HTTP 400. Stick to YYYY-MM-DD across both parameters.

### Can I limit what my agent is allowed to do with the JW Player Analytics Metrics API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and both JW Player Analytics operations are read-only reports, so you can scope the agent to only reading account totals and top videos and nothing more. Since the account token sits in the URL path, you can also pin the agent to a single accounttoken so it fetches metrics for that one account and no other. This keeps a briefing or reporting agent restricted to exactly the two GET endpoints it needs.