Recently, my team and me have been trying to integrate Balena’s cloud API into our backend system programmatically to speed up onboarding new users of our system. During the integration process, we’ve noticed that maintaining a “custom” HTTP client for the API consumption often will require quite a lot manual work.
As there currently is none, we’d greatly appreciate an official OpenAPI definition of the Balena Cloud API covering all endpoints, models and error responses. Having a machine-readable spec would let customers auto-generate SDKs in technologies that are not Node.js or Python (which seem to currently offer an SDK package for Balena Cloud API access) - these being C# (.NET), Go, Java, etc.
Naturally, by providing this, the integration time of any customer would be cut by a great amount and it would be a great benefit for both Balena and its customers.