@Adrian4 Yes, you can. Action batch is designed for this.   https://developer.cisco.com/meraki/api-v1/action-batches-overview/#action-batches     ... View more

@meilenstein  Can you confirm that the device has been added to a network already?  If yes, you should find the network ID in the result of getOrganizationInventoryDevice.  It's expected the dashboard.devices.getDevice endpoint to return 404 error if the device just sits in the inventory but not in a network.  ... View more

It still looks like a wrong/non-existing SN to me. To narrow down this, first, ensure you have the right network permission(which I assume you already have as you can get the organization list). Then try the below curl command to rule out any library issues.    curl -L --request GET \ --url https://api.meraki.com/api/v1/devices/[YOUR SERIAL NUMBER] \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --header 'X-Cisco-Meraki-API-Key: [YOUR API KEY]' ... View more

@RaphaelL If you have switches in your network, may be worth exploring the 'Switch Port Management Privileges' described in the below documentation.   Be aware that the packet capture settings will apply to the entire network.   https://documentation.meraki.com/General_Administration/Managing_Dashboard_Access/Managing_Dashboard_Administrators_and_Permissions#Switch_Port_Management_Privileges   Here is my quick test: - Create a port management privilege called 'packet-capture' and select an existing switchport tag. - Assign the admin with the access privilege 'packet-capture' under the organization > administrators, just like how you assign privilege to other admins. - The administrator will have very similar visibility and control to a normal 'read-only' network admin but with additional #1 packet capture enabled for the whole network, # 2 write permission to specific switchports configured in port management privilege based on the tag you choose.   Hope this is helpful. ... View more

Hi @sfaeder    Yes, there is a new endpoint 'client search by MAC' to solve your problem.   {{baseUrl}}/organizations/:organizationId/clients/search?mac=xx:xx:xx:xx:xx:xx   Check this announcement (page 29 of the attached doc).  https://community.meraki.com/t5/Developers-APIs/Dashboard-API-Fall-2021-Feature-Announcements-What-s-new/m-p/132578#M5224  ... View more

There is a concurrency limit of 10 concurrent requests per IP. It sounds like you are not the only one who is calling the same Meraki organization probably with a automation script.    Try to use the below endpoints to investigate.   Use 'getOrganizationApiRequestsOverview' to get an overview of API summary during a given timespan. Here is an example.   { "responseCodeCounts": { "200": 50000, "201": 4000, "204": 1000, "400": 3500, "404": 1500, "429": 10000 } }   Use 'getOrganizationApiRequests' to analyze details on what are those API calls, who is calling them from which IP.  Below is an example of the output. You might need to create a script to analyze the output as there are tens of thousands of items in case of API being misused.   [ { "adminId": "212406", "method": "GET", "host": "api.meraki.com", "path": "/api/v0/organizations/33349/apiRequests", "queryString": "timespan=604800", "userAgent": "PostmanRuntime/7.6.0", "ts": "2019-02-20T17:31:23Z", "responseCode": 200, "sourceIp": "123.123.123.1" } ]   Once you identify the suspect admin ID, use 'getOrganizationAdmins' to get the email identity.     ... View more