The Meraki Dashboard API key is associated with the dashboard administrator account which generates it, and it inherits the same permissions as that account. The API does not provide a direct way to identify the user who generated a specific API key. This is likely for security reasons, as API keys provide authentication to all organizations with the API enabled.
If you need to manage API keys for different users, it’s recommended to have each user generate their own API key from their profile. This way, you can keep track of which key belongs to which user. Please note that SAML dashboard administrators cannot view or generate API keys.
Cisco Meraki Dashboard API - Cisco Meraki
I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.
Please, if this post was useful, leave your kudos and mark it as solved.