Security requirements changed for POST /crm/v4/associations/{fromObjectType}/{toObjectType}/batch/archive

What changed

Security requirements changed for POST /crm/v4/associations/{fromObjectType}/{toObjectType}/batch/archive Affected surface: POST /crm/v4/associations/{fromObjectType}/{toObjectType}/batch/archive. Detected at Thu, 16 Apr 2026 14:54:44 UTC UTC.

Diff

{
  "current_value": [
    {
      "oauth2": [
        "crm-public-object-api-access"
      ]
    }
  ],
  "path": "POST /crm/v4/associations/{fromObjectType}/{toObjectType}/batch/archive",
  "previous_value": [
    {
      "app_cookie": [
        "crm-public-object-api-access"
      ]
    },
    {
      "hapikey": null
    },
    {
      "internal_cookie": [
        "crm-public-object-api-access"
      ]
    },
    {
      "oauth2": [
        "crm-public-object-api-access"
      ]
    },
    {
      "shhkey": null
    }
  ]
}

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.

Recommended action

Re-check your auth setup against the provider's current docs. Auth changes typically require config updates, not code changes.