There are a few steps that our RnD took to ensure future compatibility:
Even when v2 of our API comes out, v1 will still work until the release of v3. This means that you will have time to apply any changes, if they will be needed.
For now, API is not replacing any major commands (like UBUS GPIO commands) as a lot of users are still using them.
UCI commands, which can also be used to change configuration, will still remain in place.
However, I’d suggest migrating to the API, as it will be universal across all families of devices, which will ensure compatibility within the entire fleet. It will also provide possibility to configure the devices remotely using the same API calls (although authentication will be needed).
Hope this resolves any concerns, and if any other advice regarding API is needed, feel free to ask, or check out the tutorials or examples prepared by our RnD team.