In API keys, select Rotate for the intended key and read the confirmation. The current credential stops working immediately when the rotation is completed.
Prepare to update the server-side configuration that uses the key. Save the replacement when it is revealed, deploy it through your normal secret-management process, and verify that the connector authenticates with the new value.
Existing records are retained. Rotation changes authorization for future requests; it does not undo previous imports or remove the company’s data.
If requests fail afterward, check that the server uses the replacement key for the correct company and environment. Do not paste either the old or new secret into support messages. Use the integration ID, key name, and safe error instead. Revoke is a separate action for stopping access without replacing the credential, so choose the control that matches whether the integration should continue or be retired.
Was this article helpful?
Tell us whether this answered the question you came with.