We are excited to announce two big updates from RapidAPI today. First, raising our Series B, led by M12 — Microsoft’s Venture Fund — to help us continue to grow the RapidAPI community. Second, launching RapidAPI for Teams — a new capability allowing development teams to share and collaborate on internal APIs and services.
Four years ago, we launched RapidAPI to help developers around the world leverage APIs and build transformative software. Since then, millions of developers have been using our platform, tools, and resources to connect to APIs and create transformative applications in any field: from transportation to education.
Today’s updates will help us both accelerate our mission and expand the value we provide to developers — including allowing developers to share and collaborate on internal APIs and microservices!
#1: Raising our Series B from M12
We have recently raised a $25M Series B for RapidAPI, led by M12 — Microsoft’s Venture Fund. M12 was joined by DNS Capital as well as our existing investors — Andreessen Horowitz, Grove Ventures and Green Bay Capital — all of which have been phenomenal partners to us.
Over the past several years Microsoft further established itself as a powerhouse in the developer space, launching tools like Visual Studio Code and TypeScript which we use (and love) at RapidAPI, and acquiring GitHub — the largest developer ecosystem in the world. With its position, we see Microsoft and the M12 team as an extraordinary partner for growing RapidAPI.
An impact this partnership has already made on our business is the introduction of Azure APIs to our Marketplace, including Computer Vision, Text Translation and News Search — amongst others. Beyond that, we still intend to offer full support for all over cloud providers (we are in-fact native to AWS) and work with all platforms.
#2: Launching RapidAPI for Teams
Today we are also launching RapidAPI for Teams — a new capability for engineering organizations to share and collaborate on internal APIs and microservices using the RapidAPI platform.
RapidAPI for Teams centers around 3 key capabilities:
- Share internal API documentation and testing with your team
- Discover internal APIs within your team, test them and consume them from within RapidAPI.com
- Consume external APIs with a single team billing account — manage all subscriptions on RapidAPI
As teams transition to using microservices (and service mesh) in their architecture more APIs get created in the company — making it increasingly difficult to tell:
- What APIs do we have?
- Do we have an API to do this already?
- Do the multiple APIs we have produce consistent results?
- What is the current APIs usage?
- How does this API work / where are the docs?
This leads to one of two things: either a lot of time wasted on meetings trying to find out what APIs exist and how they work, or duplication of code caused by people not knowing that the service already exists. This problem is even more acute in fast-growing teams where new team members can hardly know what microservices exist and whom to ask questions about them.
With RapidAPI for teams, you can invite your colleagues into a joint space in RapidAPI and privately share internal APIs within the organization. This lets developers easily explore what APIs are available and test them from the browser (the same way you can test public APIs within the RapidAPI marketplace) — making it easier for developers to work fast.
On top of the ability to share internal APIs, once your team is set up, you can also connect to and consume public APIs together and share subscriptions across the company. This lets teams more easily monitor overall API usage, performance, and spending.
At RapidAPI, our mission is to empower developers to create better software by leveraging the power of APIs. RapidAPI for Teams helps extend this mission, and we are looking forward to seeing what innovative products and services the community will create next with the help of APIs! Try creating an organization on RapidAPI for Teams today, and please feel free to contact us at firstname.lastname@example.org with any questions.