When Should you make a custom API and How

Ready API

Pros

Ready APIs are great! They allow you to get started immediately with whatever it is you need to do, without having to make it yourself. Someone already did it for you!

Cons

You often have very little control over what you can do with the information, and you can’t add your own functionality to it.

Custom API

Pros

The biggest advantage of a custom API is the ability to make it however you want and remains one of the main reasons for making it manually. It allows you to receive and manipulate or store data however you want and that alone can be a huge thing. You can also make custom responses and error messages. This combined with frontend skills can make something magical and really efficient.

Cons

You need to make it. This is what pushes people away and understandably so. It is intimidating at first, as every new thing tends to be. It is a really strong tool, which is also why it is complicated at times. You need to study new coding languages, concepts, syntax, logic, etc.

What I am Doing

Now that you have a good idea of what the two are and when each one should be used, why am I using both?

How to Start

There are many technologies and methods you can use and it really depends on what exactly you're trying to get out of it.

Conclusion

The main takeaway of this blog is that there is a place for both options and in many cases, a combination of both is the best method. I consistently use both types of APIs and I always find new reasons to use them. It should be a given by now that you should be prepared to use either of the two or both which is why I say learn both! Happy coding!

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store