Video intelligence

Parameters

Query parameters

Examples

Make the request

curl "https://www.monocrawl.com/v1/panorama/video-intel?url=https%3A%2F%2Fwww.tiktok.com%2F%40nasa%2Fvideo%2F7665075736742530317" \
  -H "x-api-key: mn_your_key_here"

const key = process.env.MONOCRAWL_API_KEY;
if (!key) throw new Error('Set MONOCRAWL_API_KEY on your server.');
const res = await fetch(
  "https://www.monocrawl.com/v1/panorama/video-intel?url=https%3A%2F%2Fwww.tiktok.com%2F%40nasa%2Fvideo%2F7665075736742530317",
  { headers: { "x-api-key": key } },
);
const body = await res.json();

if (!body.success) {
  // one error shape for every endpoint — see /docs/errors
  throw new Error(`${body.error.type}: ${body.error.message}`);
}

console.log(body.data, "credits left:", body.credits_remaining);

import os
import requests

res = requests.get(
    "https://www.monocrawl.com/v1/panorama/video-intel?url=https%3A%2F%2Fwww.tiktok.com%2F%40nasa%2Fvideo%2F7665075736742530317",
    headers={"x-api-key": os.environ["MONOCRAWL_API_KEY"]},
    timeout=60,
)
body = res.json()

if not body["success"]:
    # one error shape for every endpoint — see /docs/errors
    raise RuntimeError(f"{body['error']['type']}: {body['error']['message']}")

print(body["data"], "credits left:", body["credits_remaining"])

Response

Response fields and example

This example is illustrative, not a captured live response. Variable-cost operations may settle a charge different from the list price below. A successful response puts the platform payload in data and reports the exact credits used, remaining balance, request id and cache status beside it.

{
  "success": true,
  "platform": "panorama",
  "endpoint": "/v1/panorama/video-intel",
  "data": {
    "resolved": {
      "platform": "youtube",
      "endpoint": "video",
      "url": "https://www.youtube.com/watch?v=example1234"
    },
    "video": {
      "id": "example1234",
      "views": 1000,
      "likes": 10,
      "comments_count": 5
    },
    "transcript": null,
    "author": null,
    "top_comments": [],
    "engagement": {
      "plays": 1000,
      "interactions": 15,
      "engagement_rate": 0.015,
      "counts": {
        "likes": 10,
        "comments": 5,
        "shares": null,
        "views": 1000
      },
      "count_sources": {
        "likes": "likes",
        "comments": "comments_count",
        "shares": null,
        "views": "views"
      },
      "counters_reported": 2
    }
  },
  "credits_used": 8,
  "credits_remaining": 99,
  "request_id": "req_…",
  "cached": false
}

The example uses fictional values and shows a documented subset of data. The fields below are optional across supported sources; nullable fields can also be absent. Preserve unknown values and accept additional fields.

Download the data JSON Schema. Validate response.data, not the whole envelope. A valid shape does not establish that every field or source record was returned.

Illustrative counters, not a live video claim. Every component comes from the returned normalized video; missing counters remain null and legitimate zeros remain zero.

Transcript, comments and author lookups can fail independently. An explicit YouTube channel ID supports the author lookup even if the video has no handle. All requested legs share the original workflow budget.

Failures use the typed error envelope. A confirmed uncharged or refunded failure reports zero; a pending reconciliation can report an unknown charge. Read credits_used and error.details.billing_status, and keep request_id for recovery. Response contract · Error reference

Related

More Panorama reference

• All Panorama operations →
• Browse the complete endpoint directory →
• OpenAPI JSON →