In the world of application development, Application Programming Interfaces (APIs) enables the communication and exchange of data between software. Testing your API is essential to the proper integration and delivery of quality software and product. Unlike UI testing, API automation testing is designed to withstand the short release cycles and frequent changes that occur while using best practices for software development and IT operations. API testing is more important than ever.

Mocking APIs is an increasingly popular trend, with more and more developers seeing the advantages of mocking dependencies rather than spinning up actual duplicates of resources. On a high-level, a mock API means that you have a service that returns static data, which in turn is based on a real API.

Offering customers a variety of ways to pay for your product allows for flexibility and ease. In general, there are two ways for customers to pay for usage: Post-paid and pre-paid. Pre-paid is sometimes also referred to as PAYG, or Pay-As-You-Go. Post-paid usage can sometimes lead customers to have billing surprises if they are not tracking their usage closely. This can cause headaches for these users and can also cause issues for the service provider.

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.

WSO2 Identity Server provides many identity management workflows and password management workflows out of the box, e.g., self-registration, user invitations, password recovery, etc. However, it is not unusual to come across a situation where the workflow capabilities provided out of the box in the product, is not sufficient to fulfill your business requirement.

Photo by Micah Williams on Unsplash This article discusses a new feature which will be released for the public distribution of WSO2 Identity Server 5.12.0. This feature was developed to overcome the following scenario: You can refer to the following diagram for a deeper understanding of the above flow. This scenario can be experienced by anyone. As such, we introduced a new way to handle this scenario (as shown below) for the notification based password recovery flow.

Kong Gateway integrates with Hazelcast to implement advanced policies for rate limiting besides the fundamental options provided by the Kong plugins, including distributed compute, security, zero downtime, and cloud agnostic.

You would think in the Internet age, primary sources for a widely discussed event — one that’s helped define cloud computing and today’s cascading digital transformation of enterprises — would be easy to track down. The original footprint must be somewhere. But that’s not so in the case of the arresting “API Mandate,” perhaps better thought of now as the API Mandate or API-First Mandate.

Resources Sample File: MicrosoftGraphTemplate.lsoz (65.8 KB) (download) API Reference: More information on the specifics of authentication can be found in the Microsoft Graph API reference documentation. Microsoft offers a RESTful web service named Microsoft Graph API. This tutorial shows you how to integrate with the Microsoft Graph API and Linx, a low-code development tool.

Using a low-code platform as the back-end for a single page application (SPA) is a nice combination — the SPA can be hosted anywhere, the API is quick and easy to develop, and they can evolve independently of each other e.g. if you need a native app just develop the UI and use the same API.

SOAP, being a mature technology, has an extensive and often differently interpreted standard set. This makes it an excellent tool for corporate users to manipulate data into their precise requirements and technology stack. However, for public consumption, this causes issues that sometimes are difficult or impossible to solve without changing code. A good example here is that SOAP is allowed to define the same type in some standard interpretations in different XSD files.

If you’re a SaaS company, it is impossible not to tackle the topic of integration. Whether you’re a small software business or a large, established tech enterprise with several SaaS products, every commercial conversation is highly likely to involve the question “Will I be able to sync data from your application with my CRM / ERP / Finance / Marketing” – you name it.

Photo by Tima Miroshnichenko from Pexels

Are you someone who already has a legacy system in place and wants to migrate to a modern authentication system with Identity and Access Management (IAM) features? The first thing you need to consider is how you can use the existing legacy user store with this new system. Keep in mind that if the legacy user store uses an old security mechanism to store your data, we would recommend that you migrate to the WSO2 JDBC user store format or Active Directory (AD).

Jason Cumberland, CPO and co-founder of API and data monetization platform HyperCurrent, contributed to this post. In our last article on how to get started with API monetization, we laid out how to build your API monetization strategy and avoid common pitfalls that occur when trying to get to your first minimum viable product release.

With over 50,000 active organizations and 250 million workflows, CircleCI is one of the most popular networked CI platforms. When getting started with CI pipelines, teams typically want to ensure that code will compile, pass unit tests, and build a container image. After catching these low hanging fruit of syntax errors, engineering teams need to dig much further to find business logic and scalability errors.

Today, the Envoy community has introduced Envoy Gateway, a new project to better support Kubernetes deployments via the new Kubernetes Gateway API, which is the next generation Ingress specification in Kubernetes world. Kong has been deeply invested in the success of Envoy since we started developing Kuma in 2019 – now used in Kong Mesh (built on top of Kuma).

In our last development cycle, we spent time improving our table performance in AppSignal. As customers stay around for longer, data starts piling up. A view with just 10 items in the beginning gathers hundreds of items, and keeps growing. Besides filtering data in the front-end to reduce the returned data, we wanted to ensure our data could keep growing without timeouts in our GraphQL API or slow-loading pages in our app.

Have you ever found passwords to be extremely inconvenient? In a developing world, you've been using older technology?

One of the most common questions we’re asked by prospective customers is “what’s the right way to get started with API monetization?” In this article, we’ll do our best to lay out what we’ve seen work most frequently — and call out a few common pitfalls as well. What we can say with certainty is that, “Build it and they will come,” doesn’t work as an API monetization strategy.

Open Banking is a key digital transformation initiative in many countries. Its aim is to provide end users with more control of their financial data and to enable companies involved in banking, financial services, and insurance (BFSI) to quickly offer new services. The Kong-AWS partnership provides the right technology enabling these financial institutions to transform and meet the key requirements of Open Banking.

At Moesif, we’ve put a lot of work into improving viewing details and trends for specific users and companies. This includes our recent addition of adding profile dashboards to add individual and reusable charts to user and company profiles Now, we’ve added even further functionality by allowing users to customize what each individual user and companies profile view looks like.

Recent events over the past two years have shown that delivering enhanced digital experiences is critical for business success. The ability to innovate fast is now the differentiating factor that determines whether a business is a leader or a follower.

This is the second installment of the series. As a result, if you haven't yet completed Part 01 of the series, it is highly urged that you do so first. According to the official website, Asgardeo is an IDaaS that allows developers to create seamless login experiences in minutes. Let's concentrate on the performance optimization approaches utilized in react and webpack in this article.

Have you ever wanted to accept payments in Rails? With Stripe Checkout, it's never been easier. Jeffrey Morhous shows us how.

Over the last ten years, APIs have grown in popularity and utilization. They've evolved into critical components of application infrastructure, and as businesses continue to use and build them, good API architecture will become increasingly important. A smart API design helps performance and the overall developer experience, whether they're public or internal. The most common APIs employ HTTP requests to access and use data and follow a RESTful architecture.

This post explains the approaches we used to improve performance in our application. This knowledge will also assist you in applying these strategies to your projects as required. Please keep in mind that this post series focuses solely on the front end. According to the official website, Asgardeo is an IDaaS that allows developers to create seamless login experiences in minutes.

Consumer onboarding is one of the, if not the most, important functions of a customer identity and access management (CIAM) solution. An overly complicated onboarding workflow significantly detracts from the consumer experience. Providing an effective, engaging and efficient onboarding workflow without compromising security has always been a challenge among security and risk professionals.

In part 1 of this series, we introduced the three most common abstract workflows based on the method in which they are initiated. But what makes an abstract workflow a concrete workflow are the different types of components that make up the workflow. In this article, we will take a look at these components.

When talking about API integration, the matter of API rate limiting is unavoidable. Researching what the rate limits of the APIs you’re going to ‘consume’ in your integrations are should be part of your overall preparation for the development of your project scope. It is also a crucial detail to know when you will be designing your integrations; rate limits will define early on what mechanism you need to implement to avoid hitting them in the first place.

Do you recall what your first password was? It was probably something easy that you could remember easily, such as your birthdate or the name of your pet. However, as you created additional online accounts, your passwords grew more complex and difficult to remember. It's a problem that many people face. As a result, many of us tend to reuse passwords across many accounts, exposing our personal information to theft.

In this tutorial, you will learn how to work with the gRPC Golang library for microservice communication by creating a simple note-taking application. APIs and service-to-service communication are what make modern microservice architecture possible. REST is generally the preferred implementation pattern, but if you only use REST, you could miss out on the significant performance gains that gRPC can offer. gRPC can provide better speed and efficiency than REST APIs.

API providers need to observe their APIs to get meaningful data about whether and how they are consumed in practice. API observability is a form of monitoring that passively logs API traffic to an observability service. Different from traditional API monitoring, with API observability you: Monitor interactions to improve developer experience Understand how customers use your API Troubleshoot your API Observing REST APIs is well understood and supported, but not every API is a REST API.