Video outlier analysis API

Compare a video's performance with its creator context instead of ranking every post by raw views.

What to build with it

  1. Provide the platform and exact video URL.
  2. Poll the returned job ID until the analysis has finished.
  3. Review the baseline, comparable posts and available sample before using the result to shortlist creators.

Provider reference: Virlo documentation. Authentication uses a provider-issued Bearer token, stored on your server.

Endpoints and inputs

2 documented operations. Query and path fields are listed separately from JSON request-body fields.

Before you integrate

  • An outlier is relative to a baseline. It is not a guarantee of future performance or proof that a creative technique caused the result.

Check the provider's current price, allowed use and retention terms before sending requests. An optional field can be absent; the schema alone does not establish its completeness or accuracy.

Give this task to your coding agent

video-outlier-api agent prompt
Help me implement video outlier analysis api using the documented Virlo API.

Reference: https://allthemapis.com/social-media-apis/video-outlier-api
Provider documentation: https://dev.virlo.ai/docs/satellite/video-outlier
Base URL: https://api.virlo.ai
Starting operation: POST /v1/satellite/video-outlier

Read the current provider docs and confirm the required inputs before writing code. Load VIRLO_API_KEY from a server-side environment variable and use Bearer authentication. Do not put the key in client code, logs, analytics, or the chat.

Ask me for any missing video URL, creator handle, research intent, or job ID. Do not invent a result. Ask for approval before starting billable lookups, recurring jobs, or destructive changes. For jobs, keep the returned ID and poll with the documented delay instead of starting the job twice. Handle pagination, rate limits, partial results, and missing fields explicitly.

Build the smallest integration for this task:
1. Provide the platform and exact video URL.
2. Poll the returned job ID until the analysis has finished.
3. Review the baseline, comparable posts and available sample before using the result to shortlist creators.

Return the code, the environment variables I need, and a short explanation of what was actually retrieved versus inferred. Do not execute paid requests until I approve.

Sources and review dates

Virlo's public documentation and OpenAPI schema reviewed October 27, 2026. Endpoint paths and field names below refer to that provider's API. This is an integration reference, not a measured performance ranking.

Corrections: email faizank@docsalot.dev with an official source.