Install Jentic One Beta

Connect the JW Player Analytics Metrics to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the JW Player Analytics Metrics, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fanalytics-metrics.jwplayer.com%2Fjwplayer-analytics-metrics" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fanalytics-metrics.jwplayer.com%2Fjwplayer-analytics-metrics" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with JW Player Analytics Metrics API.

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

GET STARTED

Start building with JW Player Analytics Metrics API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use JW Player Analytics Metrics API for, with concrete tasks.

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

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.

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.

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.

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

2 endpoints — jw player analytics metrics is a video-analytics api exposed at analytics-metrics.

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}

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using JW Player Analytics Metrics API through Jentic.

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.

Analytics Metrics Jwplayer JW Player Analytics Metrics

Name: JW Player Analytics Metrics API
Brand: JW Player Analytics Metrics
Availability: InStock

Community OpenAPI document · agent-readyAnalyticsProduct AnalyticsapiKey2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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

Use for: I need to pull JW Player account engagement for the last 30 days, Get the top-performing videos on a JW Player account this week, Retrieve the analytics totals for a specific JW Player accounttoken, Find the top 10 videos for a date range

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

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.

Jentic One on Github View OpenAPI Document