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.