It would be a waste of time to test the entire functionality of this method, assuming that the referenced functions are already tested.
Only unit-test the value added by a function.
The value is that it successfully delegates some task to another API.
Things like the exact timeout value are probably not that important:
the function would work just as well if the timeout were changed to 10001.
Note that a single test exercising this function may be totally sufficient because it contains no branching.
A more pedantic approach would be to test with a successful result, unsuccessful result, and service that times out.
But here a simple, isolated unit test isn't really possible because of the hard dependency on SomeAPIWrapperClient. Depending on what precisely you want to test, you might want to make that dependency injectable.
It may be even sensible to not unit-test this function at all, if it will be covered by integration tests. This is likely the preferable approach, and is what I would probably do.
It is also excusable to not test very simple code, if you are confident that it will work as expected. However, dynamic languages like JavaScript make it too easy to accidentally pass a wrong parameter, so that may be undesirable.