How to organize c++ component testing with SmartBear tools?

What we have:

1. a component, written with c++ with some API;

2. component is compiled for ios devices as Framework and for Android devices as 'dynamic library';

 

Is it possible to organize component API automated testing with some of SmartBear tools? For now we created a demo apps on android/ios with simple UI. And then with TestComplete (we have a license) we run automated tests on those demo apps: clicking on UI, checking results and etc.

 

Such approach is not so good: if we create new API call, then we need to create new UI element for that, we need to update tests, in order to check that new button.

We would want to use some tool, for API testing. Something like this:

tool for calling component API (for example SoapUI) -> [something, what could bind SoapUI calls with component API. For example, some sort of web service, which would send messages to the native app, and native app translate them to API calls] -> component

 

Can somebody comment on this?