This guide will take you through the steps to design an API, build it, and deploy it to production. The process will take about 20 to 40 minutes to complete all steps. The project is to build a straightforward API to retrieve product data. You will be provided with the API specification, instructions for what tools to use, relevant scripts and all steps to get the API live.

Apigee is Google Cloud’s API management platform that enables organizations to build, operate, manage and monetize their APIs. Customers from industries around the world trust Apigee to build and scale their API programs. While some organizations operate with mature API-first strategies, others might still be working on a modernization strategy. Even within an organization, different teams often end up with diverse use cases and choices for API management.

With the global increase in digital adoption, our customers must build better digital experiences for their own customers to stay relevant. There are, however, many underlying components that need to be stitched together and maintained before an organization can start building digital experiences. This process is complex and time consuming, and there are very few organizations that have the capabilities to do so.

It’s no secret: we’re fans of API first companies like Twilio. With more than ten million customers using their platform, it seems we’re not alone. Longtime the darling of developers, Twilio’s approachable platform makes it easy to send voice, video, and SMS messages across nearly any context. Today, we’re diving into how Twilio still offers the best in customer engagement.

Many API developers and companies struggle to find ways to easily set up systems to monetize their APIs. Some are simple but not customizable, some are complex and require massive engineering effort to actually get it all running. To make things easier, Moesif created a feature a few months ago called Billing Meters which gives massive customizability but with a minimal amount of code and engineering effort.

Kong Gateway is built on Nginx/OpenResty because it has a unique master/worker architecture, forks out many worker processes, and can utilize every CPU core efficiently. It is the powerhouse within Kong. But one master / multi workers architecture has an annoying defect. Each worker is an isolated process, so it is hard to share something with each other, and in Kong Gateway, there’s a lot of information to communicate between workers, like rebuilding router/health check/cluster sync, etc.

APIs are a key aspect of our digital world and allow us to engage in digital experiences on our phones and computers every day. Every time you use an app such as Facebook or Instagram, check the weather or send an instant message, you’re using an API. So what are APIs? API stands for Application Programming Interface, which enables communication between two applications.

Sometimes you may want to limit the amount of analytics data coming into Moesif. This could be because you want to exclude specific traffic, such as internal or health check traffic, or you may want to reduce unnecessary data to control cost. Dynamic Sampling, available to customers on our Enterprise plan, was built to do just this. Dynamic Sampling lets you control which API calls are logged to Moesif based on customer or API behavior.

We are happy to announce the release of Kong Mesh 1.9 and Kuma 1.8! This release is packed with features and improvements such as observability for builtin Gateway, a complete rewrite of the CNI and projected service account tokens support. In order to take advantage of the latest and greatest in service mesh, we strongly suggest upgrading to Kong Mesh 1.9.

It’s always great to build something that makes money. The most successful businesses often find the easiest and most efficient ways to make money, while keeping costs and support to a minimum. After all, the best businesses and products are simply the ones that know how to build revenue. Many companies now look to monetizing their APIs as part of their overall monetization strategy. API monetization isn’t always easy though.

We expect software to work. Slow mobile apps and buggy website functionality are unacceptable, given that two-thirds of us do our banking from a mobile app and a quarter of the workforce logs in from their home office. Low-quality, poorly designed software can undermine operational efficiency, create security vulnerabilities, and contribute to customer attrition.

Since Apple started using SwiftUI in its operating systems, it has been experiencing a noticeable evolution, from redesigns of apps to deep system integrations. The team behind SwiftUI has taken into account the feedback they got on Twitter and other social networking sites, resulting in some fantastic APIs to work and play with this year! Here’s a quote from the session on “What’s new in SwiftUI”: So, let’s dive into everything that SwiftUI 4.0 has to offer you!

Next.js is an open source React web development framework built on top of Node.js. The Next.js framework is known for: With the help of the NextAuth.js library, I will explain how to authenticate a user in a Next.js application with WSO2 Identity Server. NextAuth is an open source authentication solution for Next.js applications. More information about NextAuth.js is available here.

One morning, you realize you have a great idea for an API. You discuss it with your team, then start building out the business case and technical requirements. Where do you go from there? You could write out the business requirements for the API and then code it. Or you could describe your API in a specification language, like OpenAPI, and use that definition to improve your team's understanding of the API and do some early testing. But are either of these the best solution?

The rapid growth in the development and use of APIs shows no sign of slowing down, and the central role APIs play in digital business across industries continues to surge right along with that growth. One recent survey of IT leaders found that 98% consider APIs mission critical, with 81% currently working with microservices and 18% planning to do so soon. The exponential growth in APIs has been such that most software in use today either uses an API or is one.

WSO2 API Controller 4.1.0 was released with WSO2 API Manager 4.1, which supports performing CI/CD tasks for APIs/API Products and Applications alongside WSO2 API Manager.

WSO2 Identity Server is an API-driven open source IAM product designed to help you build effective CIAM solutions. It is based on open standards such as SAML, OAuth, and OIDC with the deployment options of on-premise, cloud, and hybrid. It supports complex IAM requirements given its high extensibility. WSO2 Identity Server manages more than 1 billion identities worldwide.

DevOps personnel can migrate API Products using WSO2 API Controller, adding more value to the CI/CD process in collaboration with WSO2 API Manager. This blog highlights the use cases of migrating API Products and also specifies different flag usages using WSO2 API Controller 4.1.0. Let’s begin.

The pace of the industry today is pressuring software developers to build, test, and release software more frequently than ever. To achieve this pace, teams have built two core processes into their workflow: Continuous Integration and Continuous Deployment. Continuous Integration and Continuous Deployment (CI/CD) is a subset of the DevOps workflow that automates application code management and its safe, predictable shipping. In this article, we’ll take a deep dive into CI/CD.

An API is a unique product. There is no presentable UI or outcome a developer can show and market similar to a regular product in the marketplace. The only way to perceive its usefulness is to spend time testing and understanding the value it brings. Given these unique conditions, monetizing an exposed API requires a different approach compared to monetizing other products. This post discusses how to build a pricing strategy for your APIs and which aspects you should consider.

As more companies are undergoing digital transformation (resulting in a huge explosion of APIs and microservices), it’s of paramount importance to get all the necessary data points and feedback to provide the best experience for both users and developers. Kong Gateway is a lightweight API gateway that is built to be open and versatile. Regardless of the technology stack involved, Kong supports these monitoring or logging requirements through its extensive ecosystem of plugins.

Being able to group a set of users or companies based on their behaviors or traits can be extremely useful. In Moesif, we have a feature called Saved Cohorts which allows you to do exactly this. Saved Cohorts can help businesses power marketing campaigns and other sales initiatives, help engineers and customer success teams manage ongoing issues, and a host of other use cases.

Learn how the Fivetran REST API allows you to programmatically manage users, groups and connectors to scale data workflows and improve your overall security posture.

As engineers and architects, we automatically build resilience into platforms as far as possible. But what about the unknown failures? What about the unknown behavior of your platform? The philosopher, Socrates, once said “You don’t know what you don’t know”. What if I could tell you there is a way to turn these unknowns into knowns – a way to understand how your platform will behave to specific failure events…

We live in a digital economy where Application Programming Interfaces (APIs) are foundational elements for businesses to operate and grow. As rightly outlined by Gartner, APIs interconnect individual systems that contain data about people, businesses and things, enable transactions, and create new products/services and business models. The popularity of APIs has grown significantly in the last decade or so, but the history of APIs stretches back much further.

In our last blog post, we traced the evolution of APIs in the cloud age. The cloud age introduced the idea of an “API economy” — or the business practice of organizations exposing their digital services or information through the controlled use of APIs. While the API economy looks attractive today, we believe it will become even stronger in the future.

FIDO is a term that’s commonly heard of in the passwordless-authentication space. In this blog post, we’ll discuss how passwordless-authentication mechanisms first emerged, and also learn how FIDO authentication works.

In this article, we are going to explore why the Stripe developer experience is so passionately supported by thousands of developers globally. One of Stripe’s missions is to increase the GDP of the internet, and over the last decade, they’ve successfully executed 250 million API requests per day and over 91 billion requests per year through their APIs.

APIs can have a huge impact on your business, creating value and delivering new income streams. But they don’t always do so in the way you might have had envisioned at the outset. Which means, when it comes to API monetization, it can pay to be prepared for the unexpected.

Say you’re running a web service that requires input. In turn, the web service delivers it to another backend service. If the backend service isn’t available for an extended time, do you have a fail-proof system in place? This is where the circuit breaker design pattern comes in.

Most people in the industrialized world are connected to the internet in one way or another. They may not access the internet directly, but their PI and PII are captured through various interactions with other people and government/private entities.

How can you innovate quickly with APIs? Most companies are already implementing them, and some have success stories to share.

An API gateway is a server that sits between your backend services and your users. It provides an abstraction layer that helps you manage the communication between clients and your services. API gateways are a single point of entry into a microservices application and they work like a reverse proxy: They receive API calls from clients, route them to the right microservices in the backend, and return aggregated responses to clients.

APIs are everywhere! In this article, you'll learn how to consume external APIs in Laravel using Guzzle.

In March 2022, FIDO Alliance and the W3C WebAuthn working group proposed a new version of the WebAuthn specification where they claim to resolve common usability issues with FIDO while ensuring a high level of security. This has started to gain significant attention in the identity domain during the past couple of months especially with the joint announcement from Google, Apple and Microsoft on their extended support for the FIDO passwordless standard.