The biggest risk I see with using your API vs implementing a native API is the native API's are unlikely to shutdown in the next few years. It seems very risky from my perspective to use a third-party API which may go down leaving me to switch to native API when its library is no longer updated, totally defeating it's intended purpose.
Do you plan to open source the code if your company shuts down?
(from asimuvPR when Brightwork.io tried to do the same thing, but ultimately ended up pivoting)
1) What APIs has your team built before that qualifies them to build this?
2) How will you manage changes, bugs, and obscure documentation issues in the APIs that will be made available through you?
..
4) What language will the API be written in?
5) Regarding API access security: How will you handle access to multiple APIs for the same client when each API requires a different set of tokens?
Do you plan to open source the code if your company shuts down?
(from asimuvPR when Brightwork.io tried to do the same thing, but ultimately ended up pivoting)
1) What APIs has your team built before that qualifies them to build this?
2) How will you manage changes, bugs, and obscure documentation issues in the APIs that will be made available through you?
..
4) What language will the API be written in?
5) Regarding API access security: How will you handle access to multiple APIs for the same client when each API requires a different set of tokens?