Moesif had the privilege of picking the brain of the expert who literally wrote the book on API Product Management. In a wide-ranging discussion with Dr. Amancio Bouza we found out what you should really care about as an API product manager, and it’s not what you may think (hint: see the title). We also cover pricing your API, how to become a better product manager and what books should be on your nightstand.

You have an API program that developers are adopting; Customers have signed up, but some haven’t integrated yet; Of those that have integrated, a few got stuck early on and went silent; Ideally, you’d like to help both sets of customers move through the developer funnel. Moesif can act a catalyst for your developers, proactively informing them of integration issues before frustration sets in and they give up. Ensure they have a good experience – unblock your customers ASAP.

Hiring a New York or Menlo Park white-shoe law firm to write your app’s Terms of Service (ToS) might bring peace of mind, but how do you ensure that your expensive rules are actually adhered to. Just like the pervasive abuse of customer review guidelines in B2C companies, B2B companies also suffer from multiple/unverified review problems. Similarly, by their design, APIs are also vulnerable to misuse by bad actors, but this time through brute force attacks.

As with any product lifecycle, a key responsibility for API architects and API product owners is deciding when to sunset or retire a feature or offering. The API lifecycle is no different, but requires careful planning to carry out the deprecation to minimize customer impact. Unlike a packaged solution or module which is more of a black box, APIs enable your customers to build custom functionality which may have required months of integration work and testing.

This is the second in a series of playbooks that walks you through the steps required to automate key monitoring and altering functions within your product. Through automation, Moesif will save you time, resources and energy. Automating repetitive processes is a key attribute in whole-product design. By combining payload observability with behavioral emails, Moesif’s able to make you more productive through sophisticated workflows of many functional, performance and product issues.

Keeping your customers happy is paramount. And nothing alienates them more than stopping their service after they’ve made an innocent mistake. This playbook walks you through the steps required to keep your customers in the loop when quota or billing issues arise.

This guide walks you through how to stand up cross-platform analytics to track customer behavior across both your APIs and web apps. By tracking customer behavior on both APIs and web apps, you’re able to fully understand the customer journey and metrics like Time to First Hello World and Time to Value. However, gathering the data by itself isn’t enough. After all, if it’s not acted on, it’s not of much use.

Maintaining the performance and reliability of your API platform are two of the most important issues to ensure the continuing success of your product. APIs should run as efficiently as possible, and one way of safeguarding that is to rate limit, or constrain, the number of HTTP requests made in a given time period.

Automating repetitive processes is a key attribute in whole-product design. By combining payload observability with behavioral emails, Moesif is able to make you more productive through sophisticated workflows on many functional, performance and product issues. This article walks through how to set up playbooks that can save you time, resources and energy. We’ve highlighted a small number of key areas where our playbooks can assist you in the management of your product.

Behavioral email is automated and targeted messages sent to customers based on their actions or behavior. By triggering on how your customers interact with your website or product, you’re able to send email whose content is actually aligned with what they’re doing, and will therefore be far more likely to resonate.