Name the API tool, not the endpoint colour
When a portal redesign renames a console control, every engagement report that keyed on the old label goes quiet.
Teams often treat API-tool event names as disposable labels. A designer renames a playground panel, an engineer ships a new key manager, and suddenly open_explorer and tap_try_it both exist for the same moment. Reports that once looked clean become archaeological digs.
Prefer verbs that describe the tool intent—open_playground, create_sandbox_key, copy_client_snippet. Keep platform out of the event name; put it in a property so docs web and mobile stay comparable. Write allowed properties on the same day you create the event.
In API Tool Engagement Inventory engagements we spend the first day on inventory alone, because until synonyms are visible every later fix guesses at the wrong root.