Pros and cons of consuming APIs through RapidAPI

Need help APIs
1

Hi,

This is a thread created to compare consuming APIs through RapidAPI.com vs connecting to the APIs directly.

If you have used it, please share some pros/cons. Which option is better in your opinion? Why?

Thanks

2

image
image625×600 95 KB

3 Likes
3

As someone who has to do graphic design in his day job, i really like the pretty colours. As someone who is trying to learn more about APIs I don’t understand what I’m looking at.

Can a kind soul explain what that all means?

1 Like
4

He’s saying the more things you require for a functioning system, the more failure points you have.

3 Likes
5

Is this specific to using RapidAPI or the API Connector?

6

Whatever the eff RapidAPI is, it’s just extra cruft is the point, @ihsanzainal84.

2 Likes
7

Ahh i get it now! Thanks fellas!

1 Like
8

I think their value prop for developers is to unify APIs so that there is less overhead in learning a new API, rest vs graphql, managing keys, etc. I think the value prop is greater for companies that build a business based off of APIs, as they provide a marketplace for APIs to get discovered.

Respectfully to the earlier post re failure points, it is very very very unlikely that Rapidapi’s downtime will be in the top 100 concerns that a small scale developer would (or should) have.

1 Like
9

Until it happens.