As a product leader, there’s no better way to show the value of your API platform then by graphically displaying key metics. If you’re already working with Tableau, it’s easy to extract key charts, or workspaces, from Moesif’s dashboards and insert them into your visualization platform. The information from Moesif will be inserted into Tableau as a web page object.
In HeathTech apps, it’s often the case that you’re dealing with private or health-related data. This requires compliance with regulations, such as HIPAA in the United States. These regulations force you to handle sensitive data in a well-defined manner, so only specific people can read it, and if they do, it should be logged for later auditing.
Azure API Management (APIM) is a powerful platform that enables you to publish and scale APIs while ensuring they are secured. One of the great features of Azure APIM is that you can add plugins and transforms to your APIs without any code change or restarts. These capabilities are deployed using XML Policies which are a collection of statements.
Like any online service, your API users expect high availability and good performance. This also means one customer should not be able to starve another customer’s access to your API. Adding rate limiting is a defensive measure which can protect your API from being overwhelmed with requests and improve general availability. Similarly, adding quota management also ensures customers stay within their contract terms and obligations ensuring you’re able to monetize your API.
The Health Insurance Portability and Accountability Act, or HIPAA for short, is a set of laws around handling health-related data in information systems. It defines safeguards, which are rules you have to follow when handling health data for your customers. There are three safeguard categories: All three categories have to be handled correctly if you want your API to be HIPAA compliant. In a companion article we covered those key requirements and how to build HIPAA complaint API platforms.
Modern API businesses are migrating towards usage-based billing models which enables automatic expansion revenue while removing barriers to adopting a new API. With Moesif you can integrate with subscription management solutions like Recurly and Chargebee to quickly add advanced usage-based billing in a few minutes. In this guide, we’ll walk through integrating Moesif with Chargbee and some recommendations for usage-based billing.
Ep. 11: Jeannie Hawrysz, leader of API Programs at SAS Joining us is Jeannie Hawrysz, the Lead API Architect at SAS, a 22,000 person business analytics company. Before that she was an 18-year veteran at IBM and was the Technical Development Manager for IBM’s API Connect Micro Gateway. In our podcast she shares how to successfully launch API programs in non API-first companies.
This article provides an introduction to API Observability and how it fits within the overall APIOps Cycles. Then, we will walk through an example of how to successfully deploy and leverage Tyk Gateway and Moesif API Observability on Amazon EC2.
Leading customer success for developer-first or API-first businesses is quite different from traditional enterprise software. The best API products are designed to be self-serve and hands-off, meaning customers rarely need to sign into a web portal once implementation is done. If you’re a Stripe or Twilio customer, when’s the last time you signed into their web portal? Hopefully not recently, otherwise that may imply a problem or issue.
Things don’t always go well when using an API for the first time, especially if you’re a beginner and it’s your first time integrating an API into another system. Often documentation is lacking in terms of errors, since it’s easier to anticipate things going right, than things going wrong. In HTTP, many status codes can give you an idea of what was going on when you called an API.
