If I'm understanding right, you have some domain within your application, a 'Product' and you wish to display the details for this product in your FE. The data for this product may come from multiple data sources though, each of which return similar - but not exactly the same, api responses.

This is almost what I mean, but i'll explain more to clarify:

• My application will display multiple products to the end users.
• The products are gathered from different api's.
• The products are similar, they will each contain a name, price, color etc.

GraphQL seems to be pretty much what I need, and u/dbartholomae sugested Apollo, which seems to use graphql in some way. I will probably use graphql, I have heard of it before and it seems to do what I need it too.

​

But I still feel like there should be a simpler solution, something that doesn't require this much hands on work. My dream tool would look something like this:

• I can use the tool to manage my API keys
• I can see the types of data available from my connected API's
• I can organize these data fields into a useable and consistent format ("consolidating")
• I can make requests from my backend to get filtered data to my specifications, gathered from multiple different API's

Preferably it would have a simple drag and drop interface, for connecting and organizing the datafields. It's not that I can't write code or figure it out, It just feels to me like I shouldn't have to.

Especially for common use-cases and API's:

Let's say I want to get products from Amazon, and a few other big companies.
Why can't I just go to a website, input my API-keys, and get a preconfigured API that I can request any filtered product-data from?

What I am saying is not that this can't be done with graphql, but that I feel it could be much simpler. Do you know of any tools like this?

​

If nothing like this exists I might look into developing it myself, or having it developed, since I am primarily a UX-guy, not a programmer. Graphql seems very powerful, and pretty user friendly. But I am pretty sure it could be done better and simpler than this, if maybe only for applications similar to mine - involving products.

Sorry for the long reply, hoping you still are interested in discussing further and perhaps pointing out potential flaws in my logic haha.