New: MCP server monitoring is live. Start free trial
Customer.ioSchemaAdditive

New fields added in GET /v1/campaigns/{campaign_id}/actions/{action_id}/metrics response 200: [res start end language_variants metric]

Affected surface
GET /v1/campaigns/{campaign_id}/actions/{action_id}/metrics

What changed

New fields added in GET /v1/campaigns/{campaign_id}/actions/{action_id}/metrics response 200: [res start end language_variants metric] Affected surface: GET /v1/campaigns/{campaign_id}/actions/{action_id}/metrics. Root cause: endpoint `GET /v1/campaigns/{campaign_id}/actions/{action_id}/metrics`. Detected at Mon, 24 Aug 2026 22:41:08 UTC UTC.

Diff

{
  "added_fields": [
    "res",
    "start",
    "end",
    "language_variants",
    "metric"
  ],
  "path": "GET /v1/campaigns/{campaign_id}/actions/{action_id}/metrics",
  "schema_path": "GET /v1/campaigns/{campaign_id}/actions/{action_id}/metrics response 200"
}

Likely impact

This is an additive change. Existing integrations are unaffected; this is mostly useful if you want to take advantage of the new surface.

Diff your serializers against the new schema. The diff above shows what moved.

Related changes

Other endpoints affected by the same root cause.

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.