I'm new to creating APIs and I'm wondering if it's acceptable to incorporate multiple existing APIs—like Google Maps or OpenAI—into my own API. Is it better to build everything from scratch, or is using other APIs a common practice? I want to make sure I'm learning while I do this.
9 Answers
Are you really considering making an entire mapping API from the ground up? That seems pretty crazy! You’d need a ton of data for that.
Using APIs saves a lot of time, no need to redo what’s already out there!
If you have the time and want to learn, go ahead and build it yourself. If you’re in a rush, though, using existing libraries is a great option.
It really depends on what your API is meant for. If you’re just creating a wrapper around Google Maps, what’s the unique value for users to choose your API over Google?
Definitely, don’t reinvent the wheel! It’s totally normal for a lot of apps to pull from various APIs. Using libraries and existing API services is a great way to build your own without starting from scratch.
That makes sense! Initially, I thought that relying on other APIs might prevent me from really learning how to code. Plus, I worried about any potential changes or updates to those APIs affecting my app.
You can use APIs for fun, but just know that services like Google and OpenAI can get expensive for commercial projects.
It depends on your use case. Just be cautious about what data you're sharing when using third-party APIs. If your API just merges a bunch of existing APIs, keep in mind that bigger players may decide to copy your idea if it’s profitable.
It’s pretty common to create wrappers around existing APIs to make them easier to use. Just make sure to give credit where it’s due in your readme.
Most of programming is built on top of existing APIs, so it's really normal to use them!
Yeah, it’s natural to have those concerns! But borrowing code is part of programming. It’s all about how you creatively put it together!