[xtiansimon]

What’s the landscape of solutions here—is this made for a specific context of APIs, like connecting all of “your company’s” email and messaging APIs? Or, is it something like—if it has an API, we will connect to it…?

Asking because I have a client who is using a Sales POS that has an API, and we’re trying to integrate it with another service’s API that does Accounts Payable. Company2 has not implemented all features of Company1’s API and Company2 says, “that feature is not supported”.

Of course, the Company1 product is already configured and running. Company2’s _minimum implementation_ of Company1’s API de facto restricts how Company1’s product can be configured. Who would have imagined that?!

So I’m asking myself, is there even a market for a third-party to connect these two platforms? And how would that work if these two parties are not working together, why would either work with yet another third-party? What’s the landscape here; what do I look for? Are there generic API middlemen? Or do they only provide integration within certain contexts or industries or channels. How is the market divided up?

[arash-khazaei]

> is this made for a specific context of APIs, like connecting all of “your company’s” email and messaging APIs?

Correct - our product is for connecting your internal systems.

If I understood the problem correctly, your client can choose not to rely on the "minimum implementation" Company 2 has built to connect to Company 1. Instead if it is possible, your client could use our platform to directly build a better integration between Company 2 and Company 1. Of course, we would need to understand the specifics, but in general our product can be used to build whatever business logic is necessary to connect systems within an organization/company.

Happy to chat more specifics if you reach out to founders at getstrada.com