Schema reference changed in GET /accounts/{account_id}/intel/sinkholes response 200: "intel-sinkholes_get_sinkholes_response" → "intel-sinkholes_sinkhole_coll…

What changed

Schema reference changed in GET /accounts/{account_id}/intel/sinkholes response 200: "intel-sinkholes_get_sinkholes_response" → "intel-sinkholes_sinkhole_collection_response" Affected surface: GET /accounts/{account_id}/intel/sinkholes. Root cause: endpoint `GET /accounts/{account_id}/intel/sinkholes`. Detected at Fri, 05 Jun 2026 23:33:13 UTC UTC.

Diff

{
  "current_value": "intel-sinkholes_sinkhole_collection_response",
  "path": "GET /accounts/{account_id}/intel/sinkholes",
  "previous_value": "intel-sinkholes_get_sinkholes_response",
  "schema_path": "GET /accounts/{account_id}/intel/sinkholes 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.

Recommended action

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