Core workflows

Takedown analytics

Benchmark removal performance across platforms and partners

Outtake’s takedown analytics endpoints expose aggregate performance data so you can understand pace, resolution rates, and SLA adherence across the ecosystem. Use them to share program KPIs, identify bottlenecks, or trigger escalation workflows.

Endpoints

  • GET /takedowns/summary — overall metrics for a defined window and optional filters.
  • GET /takedowns/summary/groups — grouped metrics broken out by registrar, host, platform, country, or content type.

Query parameters

NameTypeRequiredDescription
fromISO-8601 timestampYesInclusive start of the reporting window (UTC).
toISO-8601 timestampYesInclusive end of the reporting window (UTC).
platformenumNoFilter to cases involving a specific platform (e.g. youtube, amazon, telegram).
registrarstringNoFilter to cases handled by a specific registrar.
hoststringNoFilter to cases associated with a specific host.
statusenumNoLimit to workflow states such as active, resolved, or ignored.
group_byenumOnly for grouped endpointBreakdown dimension: registrar, host, platform, country, or content_type.
limitintegerOptional for grouped endpointMaximum number of groups to return (default in API spec).
cursorstringOptional for grouped endpointContinue pagination with the cursor from a prior response.

Summary metrics

$curl --request GET "https://app.outtake.ai/api/v1/takedowns/summary?from=2024-04-01T00:00:00Z&to=2024-04-30T23:59:59Z&platform=youtube" \
>  --header "Authorization: Bearer YOUR_API_KEY"

A successful response looks like:

1{
2  "data": {
3    "window": {
4      "from": "2024-04-01T00:00:00Z",
5      "to": "2024-04-30T23:59:59Z"
6    },
7    "metrics": {
8      "cases_total": 128,
9      "resolved": 102,
10      "resolve_rate": 0.79,
11      "ttr_median_s": 86400,
12      "ttr_p90_s": 259200,
13      "pct_under_sla": 0.68
14    }
15  }
16}
  • cases_total: Count of takedown requests in scope.
  • resolved: Number of cases closed within the window.
  • resolve_rate: Fraction of total cases that resolved.
  • ttr_median_s / ttr_p90_s: Median and 90th percentile time-to-resolution in seconds.
  • pct_under_sla: Percentage of cases resolved within your configured SLA target.

Group comparisons

$curl --request GET "https://app.outtake.ai/api/v1/takedowns/summary/groups?from=2024-04-01T00:00:00Z&to=2024-04-30T23:59:59Z&group_by=platform&limit=5" \
>  --header "Authorization: Bearer YOUR_API_KEY"

Grouped responses include metrics for the overall population, plus a groups array with per-dimension stats and pagination info.

  • groups[].key: Dimension value (e.g. youtube).
  • groups[].resolve_rate: Completion ratio for that slice.
  • ttr_median_s, ttr_p90_s, pct_under_sla: Latency and SLA benchmarks per group.
  • page.has_more and page.cursor: Use these to continue fetching additional groups.

Operational tips

  • Align the from/to window with your reporting cadence (daily, weekly, or monthly). For rolling metrics, issue queries on a schedule and store snapshots.
  • Compare the grouped output to identify underperforming registrars or hosts, then drill into individual cases using your workflow tooling.
  • Automate alerts when resolve_rate or pct_under_sla drops below thresholds so teams can respond before KPIs slip.
  • Share the summary metrics with stakeholders alongside contextual narratives from Collections and Search results to tell a complete story.

For full schema details and error codes, review the takedown analytics section in the API reference.