Systems | Development | Analytics | API | Testing

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.

Founding a developer-first startup isn’t quite the same as starting a regular company. When your primary focus is on creating products to sell to developers, you need to build a sales strategy around those developers’ needs. The occasional email with a ‘click here for a demo’ button just won’t cut it. Instead, it’s time to work on your content strategy. Why take our word for it?

API providers need to understand how their consumers are using their APIs. Usage metrics are essential because they tell you about API adoption, how your API is growing over time, and which endpoints are seeing more (or less) use. When you look at API usage metrics, you should be measuring the active users on your API in the sense that most closely aligns with your service.

For our latest expert interview on our blog, we’ve welcomed Jon M Quigley to share his thoughts on the topic of software engineering and his journey at Value Transformation.

In the first part of this two-part series, we examined LiveView assigns in detail — demystifying assigns, looking at some key concepts, and debugging. Now, we'll turn our attention to three common mistakes that you might make with assigns and how to avoid them. Let's get started!