New: MCP server monitoring is live. Start free trial
LaunchDarklySchemaBehavioral

Response schema changed for GET /api/v2/flags/{projectKey} (MetricListingRep)

Affected surface
GET /api/v2/flags/{projectKey}
Affected field
MetricListingRep

What changed

Response schema changed for GET /api/v2/flags/{projectKey} (MetricListingRep) Affected surface: GET /api/v2/flags/{projectKey}. Root cause: schema `MetricListingRep`. Detected at Thu, 16 Jul 2026 23:23:47 UTC UTC.

Diff

{
  "path": "GET /api/v2/flags/{projectKey}",
  "removed_fields": [
    "winsorExcludeImputed"
  ],
  "schema_path": "schema MetricListingRep"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

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

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.