Chart Reporter

What happens to MT5 reporting when I rotate my API key?

By Chart Reporter Reviewed 2 min read

The short answer

Regenerating the Chart Reporter API key replaces the old reporting key. Every MT5 terminal using that account must be updated. Rotation can interrupt reporting until those inputs are corrected, and it does not repair or replace an MCP OAuth connection.

List the terminals that depend on the key

Before rotating, identify every desktop or VPS terminal reporting to the same Chart Reporter account. A forgotten second installation is a common source of confusing behaviour: one terminal resumes while another continues sending requests with the replaced key.

Choose a time when you can update those terminals and inspect their status. The task is not complete when you copy the new value from the settings page. It is complete when each intended reporter uses it and contact is verified. Keep the replacement in a suitable private credential store rather than a shared note or article draft.

Verify one terminal at a time

Enter the replacement in the reporter EA inputs, leave the EA attached and check the terminal logs for authentication errors. Then inspect last-seen status in the dashboard. Repeat for the other reporting environments so you can associate each observation with the terminal you just changed.

If a terminal remains quiet, first check for an old key or an unsaved input. Generating another replacement immediately can invalidate the value you just installed elsewhere and create a moving target. Work through connection, allow-list and account checks before repeating the rotation.

Keep reporting and assistant access separate

The EA key authenticates reporting requests. MCP uses a separate authorisation flow for an assistant to read your journal. Rotating the EA key does not mean the assistant's access has been revoked, and reconnecting an assistant does not repair an EA using an obsolete key.

Record the rotation time if you later investigate a gap. Resuming contact does not guarantee reconstruction of every historical detail during the interruption. Avoid sharing either key or bearer token with support; the visible status, terminal version and error message are enough to begin diagnosis without exposing access credentials.

Sources and further reading

Related guides