Discussions

First, thank you for the incredible work behind Control D — it’s a refreshing, powerful platform that gives MSPs like us meaningful control over DNS in a way that’s both technical and elegant.

Direct from Barry AI chatbot in the Control D platform:
You cannot create or view provisioning codes using the public Control D API. Provisioning code management is not exposed through current API endpoints, so this must all be handled from the web dashboard. For automating device provisioning or similar tasks, the API supports some device operations, but not provisioning code creation or retrieval.

We’d love to see API support added for creating and retrieving provisioning codes for sub-organizations. As MSPs, provisioning codes are our preferred method for onboarding devices at scale, especially when using RMM tools. Being able to automate this process via API would save substantial time and reduce human error.

Imagine configuring 500 client organizations:
Right now, we need to log into each one manually, create a provisioning code, copy it, and paste it into the corresponding RMM settings. Then we repeat the process 499 more times. Our organization recently went through this manually for a much smaller number of clients, and it took some time to do manually.

Adding API endpoints to handle:

Create provisioning code

List/retrieve provisioning codes for a sub-org

…would unlock powerful automation opportunities and make the platform even more scalable and MSP-friendly.

This feature would directly enable deeper integrations with RMMs, PSA tools, and deployment workflows, and would greatly improve the experience for all users managing multiple environments.

Thanks again for the thoughtful tools you’re building!