Security requirements changed for GET /api/projects/{project_id}/integrations/{id}/channels/

What changed

Security requirements changed for GET /api/projects/{project_id}/integrations/{id}/channels/ Affected surface: GET /api/projects/{project_id}/integrations/{id}/channels/. Detected at Fri, 01 May 2026 00:36:55 UTC UTC.

Diff

{
  "current_value": [
    {
      "PersonalAPIKeyAuth": [
        "integration:read"
      ]
    }
  ],
  "path": "GET /api/projects/{project_id}/integrations/{id}/channels/",
  "previous_value": 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.