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

Fields removed in schema ads_cards_response.yaml: [GetPaymentCredentialsResponse]

Affected surface
schema ads_cards_response.yaml
Affected field
ads_cards_response.yaml

What changed

Fields removed in schema ads_cards_response.yaml: [GetPaymentCredentialsResponse] Affected surface: schema ads_cards_response.yaml. Root cause: schema `ads_cards_response.yaml`. Detected at Fri, 05 Jun 2026 00:43:10 UTC UTC.

Diff

{
  "path": "schema ads_cards_response.yaml",
  "removed_fields": [
    "GetPaymentCredentialsResponse"
  ],
  "schema_path": "schema ads_cards_response.yaml"
}

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.