Which action would disrupt API calls when setting up an API user?

Changing the API token would disrupt API calls because the API token acts as a key that authenticates requests made to the API. When the token is altered, any existing sessions or calls that rely on the previous token will no longer be valid, resulting in a failure to authenticate subsequent requests. This means that if an API user attempts to use an old token after it has been changed, the system will reject the request, effectively disrupting the calls that depend on that specific token.

In contrast, updating the user team roles typically does not impact API calls directly, as it concerns user permissions rather than authentication. Modifying feedback request parameters might change the data being requested but does not impede the ability to make API calls. Refreshing access credentials could temporarily require re-authentication but is part of routine security practices and is not typically disruptive like changing the API token.