Reel Insights

Previous value: -"True ⇒ return per-metric totals only (period, points, total, first/last boundary) and NO per-point rows. Use it for wide windows or many metrics: it is the cheapest way to stay inside the result budget when a daily series would otherwise be truncated."New value: +"True ⇒ return per-metric summaries only and NO per-point rows. Each summary states its `kind` (flow, gauge, unique, unknown) and its `aggregation`, and carries `value` only when one scalar is safe: known flows over disjoint day/month buckets are summed, gauges such as page_follows take the latest value (plus `change`), week/days_28 rolling windows and lifetime counters take the latest window, and unique-audience or unknown day/month series and breakdown maps get aggregation \"none\" rather than a guess. Use it for wide windows or many metrics when the daily rows would otherwise be truncated."

Previous value: -"Lower the per-point row cap for this call (1-250; the default and the ceiling are both 250 — this argument can only shrink it). Rows past the cap are dropped and the result reports how many; prefer aggregate:true over a tiny cap when you only need totals."New value: +"Lower the per-point row cap for this call (1-250; the default and the ceiling are both 250 — this argument can only shrink it). Rows past the cap are dropped and the result reports how many; prefer aggregate:true over a tiny cap when you only need per-metric summaries."

Previous value: -"Graph insights metric names to read, e.g. [\"page_media_view\",\"page_follows\"] (1-20 per call; trimmed and lower-cased). Names are Graph-version dependent and Meta renamed most of them in the 2024-09, 2025-11 and 2026-06 waves: pre-wave names such as \"page_impressions\" or \"page_fans\" are dropped before the request and answered with their replacement instead of an error. Graph fails the WHOLE call when one surviving name is invalid, so isolate a suspect name by requesting it alone."New value: +"Graph insights metric names to read, e.g. [\"page_media_view\",\"page_follows\"] (1-20 per call; trimmed and lower-cased). Names are Graph-version dependent and Meta renamed most of them in the 2024-09, 2025-11 and 2026-06 waves: pre-wave names such as \"page_impressions\" or \"page_fans\" are dropped before the request and answered with their replacement instead of an error. Graph fails the WHOLE call when one surviving name is invalid: when Graph says which entry it rejected, that name is dropped, the rest are re-read and it is reported in rejectedMetrics; otherwise isolate a suspect name by requesting it alone. Page metrics (page_*) are read on the Page, post metrics (post_*) on a post or Reel."

Added value: +"^[^,]+$"

Added value: +{
+  "additionalProperties": false,
+  "description": "Write the FULL series to a local file in FB_EXPORT_DIR instead of returning rows. The row cap does not apply to the file; the inline result is the aggregate-mode summary (no rows, max_rows and aggregate are ignored) plus `export: {path, format, rows, bytes, sha256}`. Use it for long daily series that would otherwise be truncated.",
+  "properties": {
+    "file_name": {
+      "description": "Optional bare file name (1-80 of A-Z a-z 0-9 . _ -, no path, no leading dot). The extension is added when missing. Omitted ⇒ <scope>-<objectId>-<since>-<until>-<timestamp>. An existing file is never overwritten; a numeric suffix is added instead.",
+      "pattern": "^[A-Za-z0-9_-][A-Za-z0-9._-]{0,79}$",
+      "type": "string"
+    },
+    "format": {
+      "description": "File format: \"csv\" (one row per data point, spreadsheet-ready) or \"json\" (the summaries plus every row).",
+      "enum": [
+        "csv",
+        "json"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "format"
+  ],
+  "type": "object"
+}

Previous value: -"Start of the window as a calendar date \"YYYY-MM-DD\" (inclusive, Page timezone). Omitted ⇒ Graph's own default window. The since..until span may not exceed 90 days per call (checked before the request); read longer histories in slices."New value: +"Inclusive start boundary as a calendar date \"YYYY-MM-DD\". The range is [since, until); Page period=day boundaries are Pacific Time (America/Los_Angeles), post and Reel boundaries UTC. Omitted ⇒ Graph's own default window. The since..until boundary span may not exceed 90 days per call (checked before the request); read longer histories in slices."

Previous value: -"End of the window as a calendar date \"YYYY-MM-DD\". Each returned `date` is the END of the period the value covers, so a window reaching today ends in a partial, still-being-computed bucket. Omitted ⇒ today."New value: +"EXCLUSIVE end boundary as a calendar date \"YYYY-MM-DD\": for Page period=day, until=2026-08-30 includes the 2026-08-29 Pacific day but not 2026-08-30, and since = until is refused as an empty window. Each returned `date` is Graph's exclusive end boundary of its period, so a window reaching today ends in a partial, still-being-computed bucket. Omitted ⇒ today (Pacific Time for a Page, UTC otherwise)."

Previous value: -"The Reel to read, as its VIDEO id — the `videoId` returned by facebook_create_reel (also echoed by facebook_get_video_status). A \"{page-id}_{post-id}\" value is a post, not a video, and does not resolve on the /video_insights edge. The Reel must belong to the resolved Page, whose token authorizes the read."New value: +"The Reel to read, as its VIDEO id — the item `id` from facebook_list_reels, or the `videoId` returned by facebook_create_reel (also echoed by facebook_get_video_status). A \"{page-id}_{post-id}\" value is a post, not a video, and does not resolve on the /video_insights edge. The Reel must belong to the resolved Page, whose token authorizes the read."