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

Response schema changed for GET /v1/campaigns/{campaignId} (CampaignResponse)

Affected surface
GET /v1/campaigns/{campaignId}
Affected field
CampaignResponse

What changed

Response schema changed for GET /v1/campaigns/{campaignId} (CampaignResponse) Affected surface: GET /v1/campaigns/{campaignId}. Root cause: schema `CampaignResponse`. Detected at Wed, 03 Jun 2026 01:52:15 UTC UTC.

Diff

{
  "path": "GET /v1/campaigns/{campaignId}",
  "removed_fields": [
    "campaignId",
    "success"
  ],
  "schema_path": "schema CampaignResponse"
}

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.

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.