Hi ,
As you have correctly pointed out it appears to be to do with your user-agent.
According to Meraki’s guidelines, the User-Agent string should follow this structure:
ApplicationName/Version VendorName
Rules:
ApplicationName: Single word, no spaces or special characters
Version: Optional but recommended
VendorName: Your organization’s name (also without spaces or special characters)
Examples:
It looks like the SDK is falling back to the internal default because a custom User-Agent string wasn’t provided, either globally or during initialisation.
You can see the fallback behavior here in the SDK:
https://github.com/meraki/dashboard-api-python/blob/a026860357c997689c79295c9cac6040cbc13808/meraki/...
If you’d like to ask the developers for more detail or suggest improvement, feel free to raise an issue on the SDK repo — they’re usually quite responsive.
However in the meantime, if you are not happy to amend your python code directly adding the user-agent, then configure it globally for the SDK here.
https://github.com/meraki/dashboard-api-python/blob/main/meraki/config.py
# Example 1: if your application is named 'Mambo', version number is 5.0, and your vendor/company name is Vega, then
# you would use, at minimum: 'Mambo Vega'. Optionally: 'Mambo/5.0 Vega'.
# Example 2: if your application is named 'Sunshine Rainbows', and company name is 'hunter2 for Life', and if you
# don't want to report version number, then you would use, at minimum: 'SunshineRainbows hunter2ForLife'
# The choice is yours as long as you follow the format. You should **not** include other information in this string.
# If you are an official ecosystem partner, this is required.
# For more guidance, please refer to https://developer.cisco.com/meraki/api-v1/user-agents-overview/
MERAKI_PYTHON_SDK_CALLER = "SunshineRainbows"
Hope this helps,
Jon