Security requirements changed for GET /api/projects/{project_id}/groups_types/{group_type_index}/metrics/{id}/

What changed

Security requirements changed for GET /api/projects/{project_id}/groups_types/{group_type_index}/metrics/{id}/ Affected surface: GET /api/projects/{project_id}/groups_types/{group_type_index}/metrics/{id}/. Detected at Tue, 28 Apr 2026 23:58:41 UTC UTC.

Diff

{
  "current_value": [
    {
      "PersonalAPIKeyAuth": [
        "usage_metric:read"
      ]
    }
  ],
  "path": "GET /api/projects/{project_id}/groups_types/{group_type_index}/metrics/{id}/",
  "previous_value": [
    {
      "PersonalAPIKeyAuth": [
        "group:read"
      ]
    }
  ]
}

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.