Security requirements changed for POST /api/environments/{project_id}/session_summaries/create_session_summaries_individually/

What changed

Security requirements changed for POST /api/environments/{project_id}/session_summaries/create_session_summaries_individually/ Affected surface: POST /api/environments/{project_id}/session_summaries/create_session_summaries_individually/. Detected at Tue, 28 Apr 2026 23:58:41 UTC UTC.

Diff

{
  "current_value": [
    {
      "PersonalAPIKeyAuth": [
        "session_recording:read"
      ]
    }
  ],
  "path": "POST /api/environments/{project_id}/session_summaries/create_session_summaries_individually/",
  "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.