Feature Request - Leverage NMM MSP level (hidden) API requests using client id/secret/scope -→ access token instead of browser cookie

Hi,

I would like to see that it's possible to use the hidden API requests on MSP level using client id/secret/scope -→ access token instead of using a browser cookie.

A clear example is assigning an Azure Runbook to an account. There is no public API endpoint for that. Looking at the details of the request when using the portal interface you can see that the following endpoint (example) is used for this specific action:
 

Uri: https://web-admin-portal-xxxxxxxxxxxxx.azurewebsites.net/api/v1/msp/scriptedActions/56/assignments

Method: POST

Request (JSON): {"assignAll":false,"accountIds":[25]}

For automation purposes and predictability of configuring the automation, being able to use a client id/secret/scope -→ access token would be great.

Instead of this, another option would be to enable more options in the public API, like the example above.

Please let me know if you want me to elaborate on this request.

Thank you for your consideration.

Regards,

Ivan de Mes