<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by moesif on Medium]]></title>
        <description><![CDATA[Stories by moesif on Medium]]></description>
        <link>https://medium.com/@Moesif?source=rss-32854f49697d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7117SI380Nsqjw9ine2hCQ.png</url>
            <title>Stories by moesif on Medium</title>
            <link>https://medium.com/@Moesif?source=rss-32854f49697d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:06:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Moesif/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Understanding API Error Codes: 10 Status Errors When Building APIs For The First Time And How To…]]></title>
            <link>https://medium.com/moesif/understanding-api-error-codes-10-status-errors-when-building-apis-for-the-first-time-and-how-to-21064b145377?source=rss-32854f49697d------2</link>
            <guid isPermaLink="false">https://medium.com/p/21064b145377</guid>
            <category><![CDATA[api-error-codes]]></category>
            <category><![CDATA[api-monitoring]]></category>
            <category><![CDATA[api-status-code-tracking]]></category>
            <category><![CDATA[real-time-error-alerts]]></category>
            <dc:creator><![CDATA[moesif]]></dc:creator>
            <pubDate>Thu, 20 Mar 2025 16:30:47 GMT</pubDate>
            <atom:updated>2025-03-20T16:30:47.211Z</atom:updated>
            <content:encoded><![CDATA[<h3>Understanding API Error Codes: 10 Status Errors When Building APIs For The First Time And How To Fix Them</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KC-_yvINzxdFRqhztnboAQ.png" /></figure><p>When making your first API call, issues can arise, especially if you’re new to API integration. It’s common for documentation to lack details on API error status codes, as the focus is often on successful scenarios rather than potential problems.</p><p>HTTP status codes provide insight into what occurred during your API call. These standardized codes range from 100 to 511, each with a specific meaning. However, only codes from 400 to 511 indicate an error response.</p><p><a href="https://www.moesif.com/features/api-analytics?utm_source=medium&amp;utm_medium=top-cta&amp;utm_term=10-error-status-codes">Moesif API Analytics</a> can help track and analyze API errors in real-time, providing deep insights into API performance and response trends. This ensures developers can diagnose issues more effectively and optimize their API’s reliability.</p><p>Let’s explore the 10 most prevalent HTTP status codes that signal an error response, whether on the client or server side.</p><h3>Understanding HTTP Status Codes</h3><p>HTTP status codes are a crucial part of the HTTP protocol, used to convey the results of a client’s request. They are divided into five categories: informational responses, successful responses, redirection messages, client error responses, and server error responses. Understanding HTTP status codes is essential for developers, as they provide valuable information about the outcome of a request. By analyzing status codes, developers can identify errors, optimize their applications, and improve user experience.</p><p>When you make an API call, the server responds with an HTTP status code that indicates whether the request was successful or if there was an issue. For instance, a 200 OK status code means the request was successful, while a 404 Not Found status code indicates that the requested resource could not be found. By familiarizing yourself with these codes, you can quickly diagnose problems and take appropriate action to resolve them.</p><h3>Error Types and Causes</h3><p>HTTP errors can be broadly classified into two categories: client-side errors and server-side errors. Client-side errors, such as 400 Bad Request, 401 Unauthorized, and 403 Forbidden, occur when the client’s request is invalid or cannot be processed by the server. These errors often result from issues like malformed request syntax, invalid authentication credentials, or insufficient permissions.</p><p>On the other hand, server-side errors, such as 500 Internal Server Error, 502 Bad Gateway, and 503 Service Unavailable, occur when the server encounters an unexpected condition or is unable to fulfill the request. These errors can be caused by server overload, internal configuration errors, or issues with upstream services. Understanding the types and causes of errors is crucial for developers to diagnose and fix issues efficiently.</p><h3>Client-Side Status Codes</h3><p>Status codes in the 4XX range typically indicate client-side errors, though modifications to the API can also trigger them. These status codes inform the user agent about the nature of the error, guiding it to take specific actions such as retrying requests or modifying document views. Here are the 5 most common client-side status error codes and how to solve for them:</p><h3>400 Bad Request: Malformed Request Syntax</h3><p>The <em>400 Bad Request</em> error message is one of the most common HTTP status codes, indicating that your API request was not properly formatted. Deceptive request routing can also result in a 400 Bad Request error, as it involves malformed or invalid requests that the server cannot process. If no additional error details are provided in the response body, it’s essential to consult the documentation. You might be missing a query parameter, a field in the request body, or there could be an error in a header field. Additionally, incorrect syntax in your request data could be the culprit.</p><p>This differs from the <em>422 Unprocessable Entity</em> error message, which occurs when your request is properly formatted but cannot be processed.</p><h3>403 Forbidden</h3><p>403 Forbidden status indicates that you lack the necessary permissions to access the requested URL. Although you are authenticated, the user or role associated with your credentials is not authorized to perform the API request.</p><p>This error may also occur due to authentication problems, such as using an incorrect API key or attempting to access features not included in your subscription plan. To avoid a 403 Forbidden error and gain network access, ensure proper authentication.</p><h3>404 Not Found</h3><p>The 404 Not Found error is among the most frequent HTTP status codes encountered. It signifies that the URL specified in your request is not available on the API server or the origin server. Although categorized as a 4XX error, typically indicating a client-side issue, it can also suggest a problem on the server’s end. Changes in API URL paths after a version update or server-related issues can lead to this error.</p><p>Errors from a prior request might also trigger a 404 Not Found error, particularly if earlier interactions resulted in state management problems between requests.</p><p>To address this, first verify for typos in your client code, then investigate potential API issues.</p><p>This status code further implies that you haven’t authenticated with the API. The API is unable to identify you and, therefore, cannot fulfill your request.</p><p>Usually, you need to register and obtain an API key for most APIs. This key should be included in an HTTP header field when making a request to inform the API of your identity.</p><p>This HTTP status code is akin to the less common <em>407 Proxy Authentication Required</em>, which indicates a lack of authentication with the proxy.</p><h3>429 Too Many Requests</h3><p>API subscription plans often have usage limits, with lower-cost options allowing fewer requests per second for your API key. If you’re sending too many requests quickly, consider implementing throttling in your client. Request headers can dictate conditions that affect rate limits and response behavior, including status codes like 412 (Precondition Failed) and 304 (Not Modified). This response might also indicate you’ve reached a daily, weekly, or monthly limit on your account. Without utilizing API analytics, you might hit these limits without receiving notifications or alerts.</p><p>An API might seem ideal until you encounter its limitations, which can render it unsuitable for your needs. It’s crucial to understand your API subscription details before integration to avoid potential issues down the line.</p><h3>Server-Side Status Codes</h3><p>The 5XX range of status codes typically indicates server-side errors, although sometimes an invalid API call that should result in a 4XX error might instead return a 5XX error if not properly handled by the server. Here are the five most common server-side errors and how to resolve them:</p><h3>500 Internal Server Error</h3><p>This HTTP status code can mean anything really, but it usually indicates the API server crashed. It could have been caused by something related to your API call. A 500 error can also occur if the server encounters issues with the message body during content negotiation.</p><p>Double-check the docs to make sure you did everything right: query fields, body fields, headers, and format.</p><p>If the issue persists, it could be due to an API update that introduced problematic code or data from an upstream service. In such cases, your best course of action is to contact the API’s support team for</p><h3>501 Not Implemented</h3><p>The <em>501 Not Implemented</em> status code relates to the HTTP method used to request a URL. To resolve this, try using a different HTTP method for your request.</p><p>Some response codes, like 501, dictate that the user agent will continue using the same HTTP method from the prior request.</p><p>Typically, an HTTP request using an incorrect method results in a 404 Not Found status. A Not Implemented status, however, suggests that the method is not available “yet.” This status allows the API creator to inform clients that this method will be accessible in future requests.</p><h3>502 Bad Gateway</h3><p>This response indicates that the server you contacted was not the actual API server but rather a gateway or proxy. The proxy server attempts to communicate with the API server on your behalf. This error response also suggests that the API server did not respond. This could be due to a network issue, the API server crashing, or it being down for maintenance.</p><p>A 502 error indicates that the proxy server could not get the requested response from the API server.</p><p>A “bad gateway” error is generally a temporary issue and should be addressed by the API provider. However, if the problem continues, it’s advisable to contact their support team for assistance.</p><h3>503 Service Unavailable</h3><p>The 503 Service Unavailable status signifies a server error. This typically occurs when the server is overwhelmed by too many API requests and cannot handle additional ones. While this issue may resolve itself as clients reduce the number of future requests, it might also indicate that the API provider hasn’t allocated sufficient resources.</p><p>Request headers can influence the server’s response behavior, potentially leading to a 503 error if certain conditions are not met.</p><p>To enhance your client’s resilience against this error, consider implementing a delay before sending another request. However, if the error code persists, it’s crucial to reach out to the API provider for further assistance.</p><h3>504 Gateway Timed Out</h3><p>Similar to the 502 Bad Gateway status, this response code indicates that the server you’re contacting is acting as a proxy for the actual API server. In this case, the issue lies with the API server’s delayed response.</p><p>This could be related to high network latency between the proxy and the API server. It could also mean that the API server takes too long to process your request. Additionally, a 504 error can occur when a user agent requested content that the server cannot provide due to slow response times.</p><p>To address this issue, examine whether the content of your request might be contributing to the timeout. If you are requesting an excessive amount of data or performing a calculation that takes an extended time, consider minimizing the request.</p><p>If you think your request is reasonable and the status doesn’t go away, contact support.</p><h3>Best Practices for Error Handling</h3><p>Error handling is a critical aspect of web development, and best practices can help developers handle errors effectively. Here are some best practices for error handling:</p><ol><li><strong>Use meaningful error messages</strong>: Provide clear and concise error messages that help users understand what went wrong. Avoid generic messages like “An error occurred” and instead offer specific details about the issue.</li><li><strong>Log errors</strong>: Log errors to track and analyze issues, and to identify patterns and trends. This can help you pinpoint recurring problems and address them proactively. <a href="https://www.moesif.com/features/api-analytics?utm_source=medium&amp;utm_medium=top-cta&amp;utm_term=10-error-status-codes">Moesif API Analytics</a> can help streamline this process by providing detailed logs and filtering capabilities to detect anomalies.</li><li><strong>Use error codes</strong>: Use standardized error codes, such as HTTP status codes, to convey error information. This makes it easier for developers to understand and troubleshoot issues.</li><li><strong>Handle errors centrally</strong>: Handle errors centrally, using a single error handling mechanism, to simplify error handling and reduce code duplication. This approach ensures consistency and makes it easier to manage errors across your application.</li><li><strong>Test error handling</strong>: Test error handling mechanisms thoroughly to ensure they work as expected. Simulate different error scenarios to verify that your application responds appropriately and provides useful feedback to users.</li></ol><p>By integrating <a href="https://www.moesif.com/features/api-monitoring?utm_source=medium&amp;utm_medium=top-cta&amp;utm_term=10-error-status-codes">Moesif API Monitoring</a>, developers can receive real-time alerts on critical API failures, ensuring that error handling mechanisms are optimized and efficient.</p><h3>Error Prevention Strategies</h3><p>Preventing errors is always better than handling them. Here are some strategies to prevent errors:</p><ol><li><strong>Validate user input</strong>: Validate user input to prevent malformed requests and reduce the risk of errors. Ensure that all required fields are present and that the data is in the correct format.</li><li><strong>Use caching</strong>: Use caching to reduce the load on servers and prevent errors caused by high traffic. Caching can improve performance and reduce the likelihood of server overload.</li><li><strong>Optimize database queries</strong>: Optimize database queries to prevent errors caused by slow or inefficient queries. Use indexing, query optimization techniques, and database tuning to improve query performance.</li><li><strong>Use load balancing</strong>: Use load balancing to distribute traffic evenly and prevent errors caused by server overload. Load balancing can help ensure that your application remains responsive even under heavy load.</li><li><strong>Monitor performance</strong>: Monitor performance regularly to identify potential issues and prevent errors. Use monitoring tools to track key metrics and set up alerts for unusual activity.</li></ol><p>By implementing these strategies, you can reduce the likelihood of errors and ensure a smoother experience for your users.</p><h3>Monitoring HTTP Status Codes With Moesif</h3><p>Moesif offers comprehensive <a href="https://www.moesif.com/features/api-monitoring?utm_campaign=Int-site&amp;utm_source=medium&amp;utm_medium=body-cta&amp;utm_content=10-error-status-codes">monitoring and notification</a> features, enabling you to automatically track any HTTP status code errors and gain valuable insights from your error response patterns.</p><p>With <strong>real-time error alerts</strong>, <a href="https://www.moesif.com/features/api-monitoring?utm_source=medium&amp;utm_medium=top-cta&amp;utm_term=10-error-status-codes">Moesif API Monitoring</a> helps identify critical issues before they impact users, allowing teams to proactively resolve them. Whether it’s a spike in 500 Internal Server Errors or unexpected 429 rate-limit errors, Moesif ensures you stay informed with actionable notifications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*mFWTanKAeQKSLKwobuTzag.png" /></figure><p>API calls are consistently monitored with user identity, facilitating the swift identification and resolution of errors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*tDfcu3zGa6w_vKexRsYVgA.png" /></figure><h3>Summary</h3><p>Undoubtedly, you’ll see many error codes when using APIs, but most have reasonable fixes. Some are related to server errors and some to client-side errors, where often one can cause the other. Request headers allow clients to customize their HTTP requests and influence the server’s response behavior.</p><p>Make sure to thoroughly read the documentation and API notes to avoid missing any crucial details during integration. If issues persist, reach out to the API provider for assistance.</p><p>Sometimes, the API provider may not resolve an issue for a consumer. If you’re using a widely-used API, consider searching online for solutions, particularly on <a href="https://stackoverflow.com/">StackOverflow</a> or generative artificial intelligence chatbot’s like <a href="https://chatgpt.com/">ChatGPT</a>, to find a fix for your error responses. Stay determined, and you’ll see your 200 OK status codes in no time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21064b145377" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moesif/understanding-api-error-codes-10-status-errors-when-building-apis-for-the-first-time-and-how-to-21064b145377">Understanding API Error Codes: 10 Status Errors When Building APIs For The First Time And How To…</a> was originally published in <a href="https://medium.com/moesif">Moesif</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why a Unified View of API Usage is Critical for Managing Multiple API Gateways]]></title>
            <link>https://medium.com/moesif/why-a-unified-view-of-api-usage-is-critical-for-managing-multiple-api-gateways-e8320575cb97?source=rss-32854f49697d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8320575cb97</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[analytics-api]]></category>
            <category><![CDATA[webdev]]></category>
            <category><![CDATA[api-gateway]]></category>
            <dc:creator><![CDATA[moesif]]></dc:creator>
            <pubDate>Tue, 04 Mar 2025 15:23:03 GMT</pubDate>
            <atom:updated>2025-03-04T15:23:03.280Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ct4pTtAIsLIc6kPSGqaV_A.png" /></figure><p>APIs have become the backbone of our digital world, with surveys showing that <a href="https://www.postman.com/state-of-api/2024">over 70% of developers plan to increase API usage year-over-year</a>. They power everything from mobile apps and SaaS integrations to IoT devices and partner platforms, enabling businesses to deliver seamless services and experiences to customers. As organizations grow, however, so does the complexity of their API ecosystem. Many teams end up deploying multiple API gateways, often to manage different product lines, microservices, or regional deployments.</p><p>While multiple gateways can offer flexibility and specialized features, they also create new challenges. Each gateway might have its own monitoring dashboards, security configurations, documentation portals, and analytics tools. Product managers, developers, and operational teams quickly find themselves juggling scattered bits of data as they attempt to track API usage, performance metrics, and monetization results across these disparate solutions.</p><p>That’s why forward-thinking organizations are turning to <strong>unified API management for multiple API gateways</strong>. By consolidating data from all their gateways into a <strong>single source of truth</strong>, they gain the ability to track both operational KPIs (like uptime and error rates) and business KPIs (like usage growth and revenue impact) from one shared dashboard. This not only streamlines troubleshooting and optimization but also enables product managers to “package” their APIs effectively whether for new subscription tiers, developer-friendly bundles, or usage-based pricing models.</p><p>Let’s explore the reasons organizations end up with multiple API gateways, the pitfalls and pain points they encounter, and the specific benefits that a unified approach can deliver. Along the way, you’ll see how incorporating centralized analytics and leveraging platforms like <strong>Moesif</strong>, can help unravel the complexity, drive better decisions, and ultimately boost your bottom line.</p><h3>Unified API Management for Multiple API Gateways: Why They Exist in an Organization</h3><p>For many organizations, having multiple API gateways isn’t necessarily an intentional design choice. Instead, it often evolves organically over time as the business scales or adapts to new requirements. Here are a few common scenarios:</p><ul><li><strong>Organic Growth Across Teams</strong>: Teams select API gateways based on their specific needs, leading to multiple “best-of-breed” gateways operating in parallel.</li><li><strong>Mergers and Acquisitions</strong>: Companies inherit different API infrastructures and maintain multiple gateways to ensure compatibility and avoid integration disruptions.</li><li><strong>Varied Deployment Environments</strong>: Different regions require specialized gateways for compliance, data sovereignty, or latency optimization (e.g., GDPR in the EU, domestic payment systems in the U.S.).</li><li><strong>Specialized Use Cases</strong>: Internal microservices may use lightweight gateways, while customer-facing APIs require advanced features like authentication flows and developer portals.</li></ul><p>An API management solution can help manage the complexities of having multiple API gateways by providing a flexible protocol that allows businesses to switch between different gateways without needing to rework their developer portal. This enhances integration and functionality across the organization.</p><h4>The Problem and Why It Matters</h4><p>Although multiple gateways can serve unique demands, it quickly becomes tricky to manage. Teams end up with fragmented data on API usage, performance, and developer adoption. Each gateway might provide its own analytics dashboard, making cross-team collaboration and strategic decision-making difficult.</p><p>Without a unified view across these gateways, product managers and leadership struggle to see which APIs are truly driving revenue, where traffic is spiking, or how user onboarding differs from one product line to another. In fact, recent research shows that <a href="https://www.salesforce.com/news/stories/connectivity-report-2023/">38% of revenue-generating digital assets in enterprises are API-driven</a>, making visibility across multiple gateways critical. Let’s dive deeper into these challenges and how a consolidated approach can save organizations from operational headaches while unlocking valuable new business insights. A developer portal can help manage these issues by providing a seamless interface with various API gateways, enabling fast key provisioning and integration, and offering a unified view that simplifies the evaluation process for API management solutions.</p><h3>Challenges of Managing Multiple API Gateways and the Power of Unified API Management</h3><p>As organizations scale, different teams, business units, or regions may adopt various API gateways based on their unique requirements — whether for performance, security, compliance, or regional deployment. While this flexibility allows for tailored solutions, it also introduces operational inefficiencies, governance inconsistencies, and fragmented data visibility. Without a unified approach, companies struggle to optimize API performance, enforce security policies, and drive monetization strategies effectively. API providers can help manage these challenges by offering centralized solutions that streamline operations, enhance security, and create new revenue streams through various pricing models like pay-per-use and partnerships.</p><h4>The Hidden Costs of API Fragmentation</h4><p><strong>Data Silos and Limited Insights</strong></p><ul><li><strong>Inconsistent API Metrics</strong>: Each gateway provides separate analytics, making it difficult to gain a comprehensive view of API usage, performance, and adoption trends.</li><li><strong>Difficult Monetization Tracking</strong>: API monetization models vary across gateways, leading to inconsistent revenue tracking and missed optimization opportunities.</li></ul><p>Understanding API users can help overcome data silos and gain better insights by enriching user profiles and analyzing API usage alongside revenue and customer success.</p><p><strong>Limited Business Visibility and Growth Potential</strong></p><ul><li><strong>Unclear API Adoption Metrics</strong>: Understanding customer behavior and high-value integrations is challenging when data remains siloed. Tracking API usage growth can help improve business visibility and growth potential by identifying trends and ensuring consistent usage over time.</li><li><strong>Hindered API Packaging Strategies</strong>: Product managers lack the insights needed to refine pricing tiers, subscription models, and usage-based billing structures.</li></ul><h3>The Solution: A Unified View for API Management</h3><p>A <strong>unified API management strategy</strong> eliminates these challenges by consolidating API analytics, governance, and monetization tools into a single platform. Moesif provides deep visibility into API performance, security, and usage patterns across multiple gateways, empowering teams to make data-driven decisions and maximize API business potential. API management solutions can provide a unified view for API management, offering innovative features and developer portals that are essential for organizations, especially in multi-gateway environments.</p><h4>Holistic API Observability and Governance</h4><ul><li><strong>Real-Time API Monitoring</strong>: <a href="https://www.moesif.com/features/api-analytics?utm_source=blog&amp;utm_medium=content-link&amp;utm_content=MEDIUM-Unified-View-of-API-Usage">Moesif can aggregate usage and performance metrics</a> from multiple API gateways, enabling rapid issue detection and resolution. Monitoring CPU and memory usage can help in holistic API observability and governance by providing insights into application responsiveness and server health, which are crucial for resource planning and diagnosing performance issues.</li><li><strong>Standardized Security Policies</strong>: <a href="https://www.moesif.com/features/api-governance-rules?utm_source=blog&amp;utm_medium=content-link&amp;utm_content=MEDIUM-Unified-View-of-API-Usage">Enforce rate limiting</a> and compliance requirements consistently across all API deployments.</li></ul><h4>Smarter Monetization and Product Strategy</h4><ul><li><strong>Cross-Gateway API Insights</strong>: Product managers can analyze API adoption, revenue impact, and retention rates in a single unified view within Moesif.</li><li><strong>Optimized Pricing and Billing</strong>: Gain the intelligence needed to refine monetization models, implement tiered pricing, and maximize API revenue. Understanding the API product lifecycle can further enhance these strategies by providing insights into key performance indicators relevant to business impact and operational success.</li></ul><h4>Aligning Business Goals with API Strategy</h4><ul><li><strong>Unified KPI Tracking</strong>: Moesif enables organizations to track API performance, customer engagement, and business impact through a single analytics platform with <a href="https://www.moesif.com/features/api-dashboards?utm_source=blog&amp;utm_medium=content-link&amp;utm_content=MEDIUM-Unified-View-of-API-Usage">custom API dashboards</a>.</li><li><strong>Scalable API Growth</strong>: Centralized visibility into API usage trends supports infrastructure planning and expansion strategies.</li></ul><p>With Moesif, companies can transform chaotic, multi-gateway environments into streamlined, data-driven ecosystems that enhance developer experience, improve security, and drive new revenue opportunities.</p><h4>Unified Analytics Help Product Managers Package and Monetize APIs</h4><p>When an organization has visibility into <strong>who</strong> is using their APIs, <strong>how</strong> they’re using them, and <strong>why</strong> they’re valuable, it becomes far easier to design effective pricing and packaging strategies. This is where unified analytics across multiple gateways truly shines. Let’s explore how product managers can leverage this holistic data.</p><h4>Segmenting and Identifying High-Value API Usage</h4><ul><li><strong>Usage Segmentation</strong>: Aggregating data across gateways helps segment usage by customer tiers, feature adoption, or endpoint activity. If enterprise customers heavily rely on a particular API, it may justify premium pricing or SLAs.</li><li><strong>Customer Profiling</strong>: Understanding which customers generate the highest traffic or revenue allows for better API packaging and monetization strategies.</li></ul><h4>Optimizing Pricing, Packaging, and Monetization</h4><ul><li><strong>Subscription vs. Pay-Per-Use</strong>: A clear view of API consumption enables Product Managers to choose the right pricing model — subscriptions for predictable costs or pay-per-use for flexibility.</li><li><strong>Feature-Based Monetization</strong>: Advanced features, such as analytics or premium data, can be placed in higher-tier plans based on real usage data.</li><li><strong>Multi-API Bundles &amp; Upsell Paths</strong>: Bundling related APIs and tracking usage thresholds can drive upsells, ensuring that developers move into higher tiers when they exceed their limits.</li></ul><h4>Data-Driven Adjustments and Transparency</h4><ul><li><strong>Real-Time Optimization</strong>: A unified view allows for quick adjustments to pricing and packaging based on under or overutilized features.</li><li><strong>Promotional Campaign Tracking</strong>: Integrated analytics provide insights into how trials or promotions impact usage, guiding future marketing efforts.</li><li><strong>Clear Metering &amp; Billing Transparency</strong>: Giving customers visibility into their API usage reduces billing disputes and builds trust, while automated alerts prevent unexpected overages.</li></ul><p>A singular view of usage is a powerful enabler for API productization and monetization. It provides the granular insights product managers need to craft compelling offers, set competitive pricing, and nurture stronger relationships with customers.</p><h3>Key API Metrics: Why a Unified View Matters</h3><p>Bringing together multiple API gateways under one management framework grants you the power to observe performance, reliability, and revenue-generation in a consistent, holistic way. These <strong>key metrics</strong> form the bedrock of continuous improvement, helping you spot bottlenecks, optimize resource allocation, and validate strategic decisions. Increased API usage is a key metric for understanding API performance and customer engagement.</p><h4>Product and Business KPIs</h4><ul><li><strong>Revenue or Billing Metrics</strong>: For monetized APIs, track revenue per call, average revenue per user (ARPU), and churn rates. These metrics can confirm whether your pricing models and product tiers are viable.</li><li><strong>Conversion Rates</strong>: If you offer freemium or trial tiers, measure how many developers or businesses upgrade to paid plans. This indicates how compelling your paid features are and where you might refine your funnel.</li><li><strong>Feature Adoption</strong>: Monitor usage of key endpoints or functionalities. Understanding which features gain the most traction guides future roadmap decisions and helps you prioritize improvements that yield the highest ROI.</li></ul><h4>Adoption and Usage Metrics</h4><ul><li><strong>API Call Distribution</strong>: With multiple gateways, it’s vital to see how traffic is distributed across various services and endpoints. This reveals which APIs are under heavy load or show strong growth potential.</li><li><strong>New vs. Returning Developers</strong>: A unified view of developer onboarding metrics — like time-to-first-successful-call or repeat usage — indicates how well your APIs retain interest and whether your documentation or portals are effective.</li><li><strong>Geographical/Regional Usage</strong>: Tracking where calls originate can guide infrastructure decisions (e.g., data center locations) and help you tailor security policies for each region.</li></ul><h4>Operational Metrics</h4><ul><li><strong>Latency (Average and Peak)</strong>: Monitoring response times is crucial for ensuring a seamless end-user experience. High latency can signal underlying issues in either the gateway configurations or your backend services. In fact, <a href="https://www.cloudflare.com/en-ca/2024-api-security-management-report/">Cloudflare’s API Performance Report</a> shows that 57% of internet traffic is now composed of API requests, making speed and efficiency a top priority.</li><li><strong>Error Rates</strong>: Tracking the frequency and type of errors (4XX, 5XX) helps surface potential configuration problems, code bugs, or external dependencies failing.</li><li><strong>Throughput and Request Volume</strong>: By understanding how many requests each gateway handles — and during which time frames — you can proactively manage capacity, load balance effectively, and predict scaling needs.</li></ul><p>In a multi-gateway environment, relying on fragmented statistics can lead to misinformed decisions. A unified dashboard ensures every team, from product management to engineering, has the data they need to troubleshoot issues, iterate on features, and prove ROI.</p><h3>Business and Growth: Why You Need a Unified Dashboard</h3><p>While operational stability and a strong developer experience are vital, most organizations ultimately measure API success by its impact on the <strong>bottom line</strong> and long-term <strong>market positioning</strong>. A unified API strategy can serve as a foundation for sustainable growth, allowing product teams to focus on strategic initiatives rather than firefighting.</p><h4>Customer Acquisition and Retention</h4><ul><li><strong>Targeted Upsell/Cross-Sell</strong>: By analyzing usage across gateways, you can identify which customers or partners might benefit from additional API features or higher-tier plans. Automated alerts or in-app notifications can then prompt timely upsells, increasing average revenue per user.</li><li><strong>Reduced Churn through Insights</strong>: A single pane of glass for customer activity enables quick identification of at-risk accounts — e.g., a sudden drop in API calls could signal dissatisfaction or technical hurdles. Product managers can intervene proactively, offering support or new features to keep users engaged.</li></ul><h4>Strategic Growth and Market Expansion</h4><ul><li><strong>Data-Backed Roadmap Decisions</strong>: Comprehensive usage data drives more accurate prioritization of new features, expansions, or acquisitions. Leadership can see precisely which APIs or endpoints are fueling growth — and invest accordingly.</li><li><strong>Confident Expansion into New Markets</strong>: If the data shows strong traction in a specific region or industry, leadership can allocate resources strategically, designing localized solutions or forging new partnerships.</li><li><strong>Preparing for Emerging Business Models</strong>: Whether it’s launching new subscription tiers or integrating with ecosystem partners, a unified API platform makes it simpler to experiment with — and measure — new revenue models.</li><li>Staying Agile in Fast-Changing Markets: Unified metrics and streamlined workflows help your teams pivot quickly in response to market feedback or disruptive trends, ensuring long-term competitiveness.</li></ul><h4>Cross-Functional Visibility and Scalable Collaboration</h4><ul><li><strong>Single Source of Truth for Stakeholders</strong>: When executives, product managers, and DevOps share the same metrics, conversations shift from “do we have the data?” to “how do we use it?” This alignment empowers better coordination on product strategy, sales, and support.</li><li><strong>Bridging Silos in Large Organizations</strong>: In multi-division or globally distributed companies, a unified approach ensures that successes and challenges are visible across the organization, reducing duplication of effort and fostering synergy.</li><li><strong>Scalable Growth and Future-Proofing</strong>: A well-structured API management strategy ensures that teams can scale efficiently, breaking down data silos and creating a foundation for long-term business growth.</li></ul><p>Centralized API management isn’t just about operational efficiency; it’s also a strategic growth lever. When teams have clear, unified data on API usage and performance, they can make stronger decisions about product direction, pricing strategies, and market expansion. In the next section, we’ll discuss how these elements come together in real-world scenarios, using unified analytics to maximize both technical efficiency and business ROI.</p><h3>Conclusion</h3><p>From the moment an organization deploys its first API gateway to the point where dozens of microservices and product lines are live, the complexity of managing and measuring API usage can grow exponentially. Multiple gateways, each with its own analytics and operational quirks, can easily lead to data silos and fragmented insights. Yet by <strong>consolidating</strong> these gateways under a single lens, companies unlock new levels of transparency and control.</p><p>While each organization’s path to unified API management is unique, the overarching takeaway remains constant: <strong>centralizing your API data is a multiplier on success</strong>. It nurtures a holistic understanding of user behavior, helps maintain strong SLAs, and aligns teams around shared, data-driven goals.</p><p>If you’re exploring solutions in this space, <strong>Moesif</strong> is capable of providing deep insights into both the operational and business aspects of your APIs. The key is to find tools and processes that facilitate, rather than hinder, your multi-gateway strategy. <a href="https://www.moesif.com/wrap?onboard=true&amp;utm_source=blog&amp;utm_medium=bottom-cta&amp;utm_content=MEDIUM-Unified-View-of-API-Usage">Sign up today for a free trial</a>, no credit card required.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8320575cb97" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moesif/why-a-unified-view-of-api-usage-is-critical-for-managing-multiple-api-gateways-e8320575cb97">Why a Unified View of API Usage is Critical for Managing Multiple API Gateways</a> was originally published in <a href="https://medium.com/moesif">Moesif</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best Practices: Maximizing AI Revenue Growth with Customer Success]]></title>
            <link>https://medium.com/moesif/best-practices-maximizing-ai-revenue-growth-with-customer-success-e8f4ae9c316f?source=rss-32854f49697d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8f4ae9c316f</guid>
            <category><![CDATA[monetization]]></category>
            <category><![CDATA[revenue]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[revenue-cycle-management]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[moesif]]></dc:creator>
            <pubDate>Fri, 22 Dec 2023 22:30:13 GMT</pubDate>
            <atom:updated>2023-12-22T22:30:13.296Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xWc7_9dDz1qIQF2IzyJq2A.png" /></figure><p>In the world of artificial intelligence, maximizing revenue growth is of great importance for businesses seeking to capitalize on their AI products. Like all SaaS tools, the defining linchpin in widespread product adoption is the end user experience. There is an intricate relationship between customer success and <a href="https://www.moesif.com/solutions/metered-api-billing?utm_campaign=Int-site&amp;utm_source=blog&amp;utm_medium=sticky-cta&amp;utm_content=Maximizing-AI-Revenue-Growth">how to make money</a> from AI products, as the successful integration of AI products into a given market relies heavily on not only the technological capabilities of the solution but also on how effectively businesses cater to their customers.</p><p>The intersection of customer success with how to make money from AI offerings is a strategic balance where technology meets user satisfaction and drives <a href="https://www.moesif.com/blog/api-monetization/api-strategy/What-Is-PLG-For-AI/?utm_campaign=Int-site&amp;utm_source=blog&amp;utm_medium=body-cta&amp;utm_content=Maximizing-AI-Revenue-Growth">business growth</a>. As businesses introduce AI products to the market, an emphasis on customer success becomes a differentiator. Customer success practices including personalized onboarding, continuous support, and proactive engagement are not just ancillary components of CS success. They’re integral elements that ensure users derive optimal value from AI solutions, encouraging customer satisfaction and lowering churn.</p><p>The commercial viability of an AI tool is not solely contingent on its technical capabilities; if that were the case, there would be a greater monopoly in the market. Rather, success hinges on how effectively businesses can align their AI technology with the unique needs of their customers, fostering loyalty, and driving sustained revenue growth.</p><h3>Commercializing AI-Based Offerings: An Overview</h3><p>Generating revenue from AI-based offerings is a multifaceted process to turn innovative (or more user friendly than competition) AI technology into a marketable and profitable product. As mentioned before, sometimes a product doesn’t have to be groundbreaking to be successful. Rather, a focus on a cohesive and enjoyable user experience can be the deciding factor in a company’s choice of machine learning solution.</p><h3>Value Proposition</h3><p>The journey begins with identifying opportunities in a given market where AI solutions can address specific needs or challenges. This phase includes market research to understand customer demands, competition, and potential niches for AI software. Challenges arise in navigating the complexity of AI development, from the initial investment in cutting-edge technology and talent acquisition to research and development. The <a href="https://www.moesif.com/features/api-governance-rules?utm_campaign=Int-site&amp;utm_source=blog&amp;utm_medium=body-cta&amp;utm_content=Maximizing-AI-Revenue-Growth">commercialization process</a> also entails creating a compelling value proposition, highlighting how the AI application addresses pain points and delivers unique benefits to potential users.</p><h3>AI in Healthcare</h3><p>One example of an industry that could significantly benefit from the adoption of AI-based software is the healthcare sector. Generative AI tools and AI algorithms have the potential to revolutionize various aspects of healthcare, ranging from diagnostic tools and personalized treatment plans to administrative processes assisted by AI model technology. For this example, AI startups for healthcare would need to build a HIPAA compliant AI powered tool, and likely trained on unique, complex language models that may not be easy for the AI product provider to set up. As such, AI companies would need to satisfy a need that could be monetized effectively to offset the costs associated with creation and maintenance of a medical LLM, or some kind of integration accessing a current provider like Med-PaLM.</p><h3>Pricing Model</h3><p>Opportunities emerge as businesses position their generative AI solutions as efficient and capable of driving significant value for users. Once developed, deciding on a pricing model strategy becomes a business priority. Having effective marketing strategies is one thing, but pricing your AI based product is a can of worms on its own. Because of the expensive nature of offering an AI system, the upstart and <a href="https://www.moesif.com/blog/api-monetization/api-strategy/AI-Infrastracture-Costs/?utm_campaign=Int-site&amp;utm_source=blog&amp;utm_medium=body-cta&amp;utm_content=Maximizing-AI-Revenue-Growth">maintenance costs</a> associated with artificial intelligence and big data models can’t be overlooked and should be accounted for in the pricing structure of your AI API. By employing a usage based pricing plan, businesses can directly offset the actual usage of their AI products. Usage based pricing also enables organizations to tailor sales approaches to appeal to a diverse customer base, including self service data scientist or data analyst users.</p><h3>Customer Success</h3><p>Ensuring user-friendly interfaces, seamless integration into existing workflows, and comprehensive customer service further enhance the customer experience and, by result, improve customer success. Throughout this journey, the iterative nature of AI development enables continuous improvements and adaptations based on user feedback and <a href="https://www.moesif.com/features/api-analytics?H1=API-Analytics-for-AI-Apps&amp;utm_campaign=Int-site&amp;utm_source=blog&amp;utm_medium=body-cta&amp;utm_content=Maximizing-AI-Revenue-Growth">analytics</a>, presenting ongoing opportunities for refinement and feature expansion. Ultimately, successful commercialization via the AI revolution requires transformative capabilities to not only meet user needs but to create new opportunities.</p><h3>Cost Considerations in AI Commercialization</h3><p>Building AI products comes with unique challenges and expenses that reflect the complex nature of artificial intelligence development.Substantial computational power is necessary to train and run AI models effectively, often requiring specialized hardware which can be expensive to acquire and maintain. Another challenge lies in procuring and managing large volumes of high-quality big data for training AI models. Acquiring datasets for large language models can be time-consuming and costly. Additionally, ensuring data privacy and compliance with industry or governmental regulations adds another layer of complexity and expense.</p><p>Beyond initial model costs, research and development can be substantial financial strains, given the iterative nature of AI development and prompt engineering. Continuous testing, algorithm refinement, and research based on the latest natural language processing advancements require ongoing investment, which can be costly in terms of hours and money.</p><h3>Customer Success Best Practices for AI Revenue Growth</h3><p>The role of customer success holds pivotal importance as businesses strive to not only deliver cutting-edge technology but also ensure that customers derive maximum value from their AI investments. Customer service for generative AI tools extends beyond the initial purchase, as lasting partnerships are cultivated through personalized experiences and ongoing support. This approach can maximize customer satisfaction, retention, and, ultimately, foster long-term revenue growth.</p><h3>Strategies for Maximizing Customer Success</h3><ul><li><strong>Personalized Onboarding</strong>: Tailor the onboarding process to individual customer use cases to ensure a smooth introduction to your generative AI solutions.</li><li><strong>Ongoing Support</strong>: Continuous support is essential for addressing evolving customer requirements. Responsive and knowledgeable dedicated customer success teams and intuitive, full-scope documentation reinforces customer confidence and satisfaction.</li><li><strong>Proactive Engagement</strong>: Anticipating customer needs and engaging proactively based on user insights can cultivate a stronger partnership. Regular check-ins, support around bottlenecks, and timely content updates or enhancements demonstrate a commitment to customer success.</li></ul><h3>Customer Success through Moesif</h3><p>Moesif can play a pivotal role in elevating customer success for any SaaS product, but particularly within the AI landscape. By providing powerful, real-time insights into how customers interact with machine learning products, Moesif empowers AI companies to understand user behavior, optimize product usage, and intervene proactively when necessary.</p><p>For example, <a href="https://www.moesif.com/features/api-monitoring?utm_campaign=Int-site&amp;utm_source=blog&amp;utm_medium=body-cta&amp;utm_content=Maximizing-AI-Revenue-Growth">monitoring API usage</a> as it relates to free trial milestones and notifying sales teams of MQLs at critical junctures enables timely engagement, enabling faster conversion of trial users into paying customers. By analyzing user behavior, customer support teams can offer personalized, targeted content and support to help users maximize their usage of your AI product, streamlining their workflows and reducing your churn rate. Additionally, Moesif’s ability to detect changes in API usage patterns offers valuable signals for potential upsells for non-technical teams, ensuring that AI startups can align their pricing and offerings with customer growth.</p><p>Moesif’s ability to manage customer success metrics extends beyond mere <a href="https://www.moesif.com/features/api-analytics?utm_campaign=Int-site&amp;utm_source=blog&amp;utm_medium=body-cta&amp;utm_content=Maximizing-AI-Revenue-Growth">analytics</a>; it can be a strategic enabler for AI-based organizations to nurture strong, value-driven relationships with their customers. Enhances your overall customer experience and position your AI products for <a href="https://www.moesif.com/solutions/api-product-management?utm_campaign=Int-site&amp;utm_source=blog&amp;utm_medium=body-cta&amp;utm_content=Maximizing-AI-Revenue-Growth">sustained success</a> and revenue growth in an ever-evolving landscape with Moesif.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8f4ae9c316f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moesif/best-practices-maximizing-ai-revenue-growth-with-customer-success-e8f4ae9c316f">Best Practices: Maximizing AI Revenue Growth with Customer Success</a> was originally published in <a href="https://medium.com/moesif">Moesif</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing Volume-Based Pricing]]></title>
            <link>https://medium.com/moesif/implementing-volume-based-pricing-e4a504760adf?source=rss-32854f49697d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4a504760adf</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[monetization]]></category>
            <category><![CDATA[usage-based-billing]]></category>
            <dc:creator><![CDATA[moesif]]></dc:creator>
            <pubDate>Fri, 15 Dec 2023 23:49:32 GMT</pubDate>
            <atom:updated>2023-12-15T23:49:32.030Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_P0qYJTo-zRdC9QYHT42eQ.png" /><figcaption>Implementing Volume-Based Pricing</figcaption></figure><p>When monetizing APIs, a popular approach is volume-based pricing. Of all the monetization models you can apply to your APIs, volume-based pricing is one of the easiest to implement. This blog will cover the basics of applying volume-based pricing to your APIs so your customers can be billed accordingly. Let’s start by looking at the finer details of volume-based pricing regarding monetized APIs.</p><h3>What is volume-based pricing?</h3><p>Volume-based pricing is a billing strategy commonly used to monetize APIs. This approach adjusts the cost based on the volume of usage. Typically, usage is measured by the number of API calls or data transferred. This pricing model is designed to cater to diverse user bases, from startups to large enterprises, by offering flexible pricing that aligns with their usage levels. With volume-based pricing, the unit price traditionally goes down as usage increases.</p><h3>Why Implement Volume-Based Pricing?</h3><p>As mentioned, in most volume-based pricing models for APIs, the price per API call typically decreases as the volume of usage increases. This pricing structure incentivizes higher usage while making the service more cost-effective for large-volume users. Here are a few facets and benefits of volume-based pricing.</p><h4>Tiered Pricing Structure</h4><p>API providers often use a tiered pricing model. Each tier has a set range of API calls, and the cost per call decreases as you move to higher tiers. For example, the first 1,000 calls might cost 10 cents each, but calls 1,001 to 10,000 might cost only 8 cents each, and so on.</p><h4>Encouraging Higher Usage</h4><p>Volume-based pricing encourages users to increase API usage since the unit cost becomes more economical at higher volumes. This can be particularly appealing for growing businesses anticipating increased API usage.</p><h4>Cost Predictability</h4><p>While the per-call cost decreases, customers can also predict their expenses more accurately as they understand how much the cost will reduce as they scale up. This makes cost a very linear calculation, one that is easy to forecast.</p><h4>Balancing Accessibility and Revenue</h4><p>For API providers, this model helps balance making their services accessible to smaller users (who might be sensitive to high costs at low volumes) while still generating significant revenue from larger customers.</p><h4>Custom Agreements for Very High Volumes</h4><p>Some API providers might negotiate custom pricing agreements for high-volume users, which could deviate from the standard tiered model to better suit large clients’ specific needs. These agreements can still keep the essence of volume-based pricing but on a more customizable level.</p><p>A massive amount of benefits can be derived from a relatively simple implementation using volume-based pricing models. It’s easy for customers to understand and a great revenue driver at scale.</p><h3>What is Moesif?</h3><p>Regarding API monetization and implementing volume-based pricing, Moesif is a go-to solution for making implementation easy. At its core, Moesif is an advanced API analytics and monetization platform. Within the platform, users can uncover critical insights into how their APIs are being used and efficiently monetize their existing APIs. It’s designed to help companies optimize, troubleshoot, and secure their API infrastructures, with a strong emphasis on aiding in effective API monetization strategies. Let’s look at some functionality in greater detail:</p><h3>API Usage Analytics</h3><p>Moesif allows businesses to track and analyze how their APIs are used. This includes detailed data on API calls, error rates, endpoint performance, and user behavior patterns.</p><h3>API Monetization Capabilities</h3><p>A standout feature of Moesif is its robust support for API monetization, allowing users to track and charge users for API usage. API monetization with Moesif enables businesses to:</p><ul><li><strong>Track Billing Metrics</strong>: Understand and monitor API usage in the context of billing and revenue generation.</li><li><strong>Identify Revenue Opportunities</strong>: Discover which features or endpoints are most popular and generate the most revenue.</li><li><strong>Implement Volume-Based Pricing</strong>: Easily track and manage usage-based billing, such as volume-based pricing models.</li></ul><h3>Customer Insights</h3><p>Moesif’s analytics capabilities provide deep insights into customer usage patterns, helping businesses understand which customers are the most active or potentially at risk of churning. This also helps companies determine which APIs they should charge for and how much they can charge for usage.</p><h3>Real-Time Monitoring and Alerts</h3><p>The platform offers real-time monitoring of API performance, alerting businesses to issues as they arise, such as an increase in latency, enabling quick response and resolution.</p><h3>What is Moesif’s Product Catalog?</h3><p>Moesif’s Product Catalog is a comprehensive tool designed to manage billing plans and prices for APIs. It serves as a centralized platform where business owners can create, manage, view, and archive various billing plans and prices, streamlining the product creation process within Moesif. This integration ensures API product compatibility with Moesif’s API metering and billing solution. The key benefits of using Moesif’s Product Catalog include:</p><ol><li><strong>Ease of Use</strong>: Business owners can create plans and prices directly within the Moesif UI, eliminating the need to access multiple systems.</li><li><strong>Integration with Billing Systems</strong>: Moesif integrates with your billing system, which remains the system of record. Any plan or price created in Moesif will also appear in your billing provider, ensuring seamless accounting and financial management.</li><li><strong>Support for Multiple Billing Systems</strong>: The Product Catalog is designed to work with multiple billing systems simultaneously, such as Zuora for enterprise customers and Stripe for self-service options.</li></ol><h3>How to implement volume-based API pricing</h3><p>To implement volume-based pricing, we will use Stripe and Moesif. With Moesif’s Product Catalog and Billing Meter functionality, we can do all this right within the Moesif platform!</p><blockquote>NOTE: You need to enable and configure the Stripe plugin in Moesif for the steps below to work. The simple steps to set that up are available <a href="https://www.moesif.com/docs/metered-billing/integrate-with-stripe/">here</a>.</blockquote><h3>Create the Plan</h3><p>After logging into Moesif, navigate to the <strong>Product Catalog</strong> by clicking the corresponding menu item in the left-side navigation. On the <strong>Plans</strong> page, click the <strong>Create New</strong> button in the top-right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QgkzAw9QtjaSb0a-.png" /></figure><p>On the <strong>Create Plan</strong> screen, you’ll fill out the <strong>plan name</strong> and select the billing provider. In this case, we will select <strong>Stripe</strong>. Once done, click on the <strong>Create</strong> button in the top-right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ASm5QySsU4RKnVv3.png" /></figure><h3>Create the Price</h3><p>Next, we will create the <strong>Price</strong> in Moesif by clicking on the <strong>Price</strong> menu item under the <strong>Product Catalog</strong> on the left-side menu. On the <strong>Price</strong> screen, click the <strong>Create New</strong> button in the top-right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ocQtg4F-g2ycD4DF.png" /></figure><p>On the next screen, you’ll add the <strong>price name</strong> and select the <strong>Linked Plan</strong> from the dropdown. In this case, we will select “My API Plan,” the plan we made in the previous step above.</p><p>Under <strong>Pricing</strong>, we will select the <strong>Pricing Model</strong> as “Volume” and leave the <strong>Meter Usage as</strong> with the defaults (unless you want to change it for your specific use case). You can add each of your tiers under the <strong>Price Structure</strong> section. You can click the <strong>Add Tier</strong> button at the bottom if you need another tier. You’ll see we’ve added four tiers in the example below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DY4iqNol3BpSsbK0.png" /></figure><h3>Create the Billing Meter</h3><p>Now that the plan and price have been created, we will create the Billing Meter to record the usage and send it to the correct plan in Stripe. To do that, we will click on the <strong>Billing Meters</strong> menu item in the left-side menu. On the <strong>Billing Meters</strong> screen, click the <strong>Add Billing Meter</strong> button in the top-right of the screen.</p><p>This will bring you to the <strong>Create Billing Meter</strong> screen. Here, you will give the meter a <strong>name</strong>, link it to our plan and price under the <strong>Link to</strong> section, and create our <strong>filter</strong> and <strong>metrics</strong>. Below is an example of a meter for a specific API endpoint (“/test-service”) that will count each API call and attribute it to the “Volume Pricing” price that we created earlier. Once you’ve created your meter, click <strong>Create</strong> in the top-right to create and activate the meter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9Z7t7EYMxdzS1mzg.png" /></figure><h3>Profit!</h3><p>With this in place, API usage will be billed based on your volume-based pricing model. This example has shown you how easy it is to create a volume-based pricing model and track usage towards it with Moesif and Stripe. Of course, this could also be done with other billing providers, including Chargebee, Zuora, and many others.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4a504760adf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moesif/implementing-volume-based-pricing-e4a504760adf">Implementing Volume-Based Pricing</a> was originally published in <a href="https://medium.com/moesif">Moesif</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Self-Serve and Sales-Led API Monetization — Unlocking Product Led Growth]]></title>
            <link>https://medium.com/moesif/self-serve-and-sales-led-api-monetization-unlocking-product-led-growth-9f16487c194b?source=rss-32854f49697d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f16487c194b</guid>
            <category><![CDATA[monetization]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <dc:creator><![CDATA[moesif]]></dc:creator>
            <pubDate>Fri, 08 Dec 2023 23:37:26 GMT</pubDate>
            <atom:updated>2023-12-08T23:37:26.273Z</atom:updated>
            <content:encoded><![CDATA[<h3>Self-Serve and Sales-Led API Monetization — Unlocking Product Led Growth</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1hwgHRj6y52Ms0QpJLzDxg.png" /><figcaption>Self-Serve and Sales-Led API Monetization: Unlocking Product Led Growth</figcaption></figure><p>There are as many monetization pitfalls as there are methods of monetizing APIs. As the market has shifted over the years, selling APIs and creating product userbases has become more important than ever. Today, we’re going to discuss a strategy that can lead to explosive growth — let’s talk self-service and product led growth.</p><h3>The Shifting Product Landscape</h3><p>The reality is that selling APIs is more difficult than ever before. The modern landscape has shifted dramatically over the years, moving both the consumption model as well as the value proposition for most adoptees of API platforms. A monolithic API provider with structured UIs and full-service integration plans used to be the gold standard, delivering a value proposition of a full-service partnership with full-service integration. As the industry and community has shifted towards automated microservices and product led growth, which deliver value through specific and targeted use cases, the idea of buying into a traditional integration approach has diminished substantially for the average API consumer.</p><h3>The Decline of Sales-Led Growth</h3><p>What this has ultimately resulted in is a shift of power between the provider of an API product and the consumer. When integrating a service requires bringing a team on premises to install proprietary systems and launch custom server clusters, the power <strong>and cost</strong> of this API management overwhelmingly lands in the camp of the software. As this has shifted, the calculus has changed substantially, with the adoptee becoming the powerhouse authority.</p><p>This has undermined the traditional pathway of sales-led API monetization and, subsequently, product growth. Sales-led is conceptually based on the idea that you have something someone else wants, and as such, you should set the price and API monetization strategy as close to the upper limit as possible to extract value and revenue. The problem with this growth strategy is that it assumes the product has a clear value proposition and is an outstanding choice. Today, the consumer has never had so much choice and flexibility, so the idea that a product can extract value through this pathway is not really true in most industries anymore.</p><p>All of this adds up to a simple truth — adoptees are more empowered than ever, and they need to have a solution that meets their specific needs with as little friction in adoption as possible. Each hiccup along the way reduces the likelihood of success and long-term retention of API users. When the authority was in the product, things could afford to be complex or high-friction — after all, the product was what the product was. In today’s API marketplace, the product has to be fast to deliver and easy to integrate with as few initial blockers as possible.</p><h3>The Self-Serve Model</h3><p>Enter the self-serve model. The basic idea of the self-serve model is to lower the friction to onboarding as much as possible by allowing the adoptee to decide on their API consumption and API usage: what they need, how they need it, and how they will pay for it. This can take several forms, but the core concept remains the same — low friction leads to high adoption. Self-serve delivers some major benefits — let’s take a look at a few of them.</p><h3>Reduced Onboarding Friction</h3><p>Self-service delivers reduced initial friction through a variety of mechanisms. Using click-through terms of service can help reduce initial legal paperwork and hurdles for an API business and the API developers using a given service alike. Automated integration of an API gateway with a simple step-by-step process can reduce the time to market for integration of the product. Simple payment options can reduce the need for client approvals and expenses. Even something as simple as allowing the user to decide between pre-pay and post-pay agreements can be provided far more simply and effectively through a self-serve business model.</p><h3>Enhanced User Experience</h3><p>The self-serve API monetization model is all about prioritizing the experience of the user, and as such, it delivers the best user experience for both adoptees and developers. Self-serve delivers ease and autonomy — not only is the product easy to use, the adoptee has autonomy to choose how they use it. This autonomy can result in long-term increases in adoption and retention, but even more importantly, it results in a product that is easy to use and easy to advocate for in a competitive API ecosystem.</p><h3>Scalability and Extensibility</h3><p>The self-serve model boosts scalability and extensibility by allowing adoptees to choose exactly what services they need when they need it, increasing revenue growth without losing direct monetization upsell opportunities. Standard systems of old might require a full rollout before any benefit can be gained, but with a self-serve approach, this barrier is lowered substantially. If a user only needs a low tier of functionality now, but is likely to use a higher tier later, they will prioritize a solution that allows them to increase their services at will over a system that requires manual deployment or support. With tiered pricing options, a flexible usage based pricing model is attractive to users who may not know their true product usage requirements, where they are granted API access, and which then results in the SaaS company to ensuring API revenue generation.</p><h3>Cost Effectiveness</h3><p>Self-serve systems are cost effective for all parties involved. Because you can tie business logic to the services being rendered at the developer level, costs can be controlled by scaling only to the demand your clients have placed on your self-serve product. For the adoptee, costs can be controlled by using only what API call volume (or whatever monetizable metric you’ve chosen) is needed at the moment and scaling over time. When an organization decides to open APIs up to the public, they not only join the API economy, but diversify their revenue recognition. This increased cost effectiveness positions your API to be a powerhouse option, as flexibility is almost always going to be valued quite highly on a ranked list of attributes for services.</p><h3>Accelerating the Flywheel — How Self-Serve Feeds Product Led Growth</h3><p>Self-serve models unlock a massive potential benefit in the form of product led growth acceleration. product led growth is a simple concept — the product should sit at the center of your growth, driving user acquisition, conversion, and retention. A self-serve model is the first big step towards accelerating this process.</p><p>Consider what a typical self-serve model looks like in practical terms. First, your user onboards and decides to check out the product. From that moment, everything rides on the product — all the user needs to experience is their “Aha” moment, the moment where they realize the product is a good fit for their use case. Flexible adoption through a self-service API business model increases the chances of this happening, and a good product should provide ample opportunity for multiple “Aha” moments.</p><p>Once the user has had that moment, however, the self-service models kicks the product led growth model into high gear. As the adoptee accelerates their use, the sales team should engage their efforts, identifying new use cases and leading the charge on new product iteration. As the adoptee becomes an evangelist for the product, pushing for adoption and further iteration, the product itself becomes better and more attractive, bringing additional users into the fray, while accelerating the use of the existing client base.</p><p>This strategy has proven itself time and time again for exceptional growth — and all it takes is the creation of a strong product and a low-friction self-serve approach.</p><h3>Creating Evangelists</h3><p>One big benefit of this model is the creation of product evangelists. A product evangelist is a dream come true for many developers — an adoptee who falls in love with the product to such an extent that they evangelize its use and accelerate user awareness and acquisition. In order to effectively creative product evangelists, you have to think like a product evangelist — so what specifically does this type of developer want?</p><p>Product evangelists need:</p><ul><li>a product they trust,</li><li>a product they can share widely and</li><li>a product others can validate their experience with.</li></ul><p>Effective self-serve models and product led growth strategies should meet these demands. A product that is low-friction and transparent in its pricing and functionality is a product that can be trusted — this can be bolstered even further through adequate and effective documentation. A product that is shareable is one that has clarity as to the value proposition — a product should have clear benefits and should document these benefits through blog posts, analytics, customer case studies, white papers, etc. Finally, a product that can validate experience is one where a new user can be influenced into adoption and immediately see the value in the product — in other words, a validating product is a low-friction product.</p><h3>Conclusion</h3><p>Ultimately, a self-service model is an incredibly powerful way to enable product led growth in API monetization, and should be considered within the full context of the form and functionality of the API. With proper attention, developers can create an incredibly powerful product led growth flywheel that is powered by a self-serve model which compounds evangelists into new evangelists day by day — and all it takes is a great product and the right intent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f16487c194b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moesif/self-serve-and-sales-led-api-monetization-unlocking-product-led-growth-9f16487c194b">Self-Serve and Sales-Led API Monetization — Unlocking Product Led Growth</a> was originally published in <a href="https://medium.com/moesif">Moesif</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[a balance between cost control and performance can be challenging to achieveKeeping AI…]]></title>
            <link>https://medium.com/moesif/a-balance-between-cost-control-and-performance-can-be-challenging-to-achievekeeping-ai-af469c11ea97?source=rss-32854f49697d------2</link>
            <guid isPermaLink="false">https://medium.com/p/af469c11ea97</guid>
            <category><![CDATA[api-monetization]]></category>
            <category><![CDATA[api-development]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[moesif]]></dc:creator>
            <pubDate>Fri, 01 Dec 2023 22:58:33 GMT</pubDate>
            <atom:updated>2023-12-01T23:03:43.699Z</atom:updated>
            <content:encoded><![CDATA[<h3>Keeping AI Infrastructure Costs Down with API Governance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ugg-cqJ40xgKN7jIkm25Sw.png" /></figure><p>The growing importance of AI in business is undeniable, with more than <a href="https://www.forbes.com/advisor/business/software/ai-in-business/">50% of businesses</a> employing artificial intelligence for security and combating fraud. Additionally, beyond the practical applications for businesses externally, AI can be used internally to deliver better customer experiences through competitive tools and features. As the role of AI within an API business’ operations expands, so do the associated AI infrastructure costs. These expenses can quickly become a significant financial burden if left unchecked. Like all outward facing API-based tools, the key to success is API governance.</p><p>That’s where API governance steps in as a way of managing infrastructure costs and avoiding financial setbacks of monumental proportions. API governance allows an organization to regulate and optimize how AI resources and services are accessed and utilized, ensuring that businesses can offer an AI solution and features without breaking the bank. Governance serves as a strategic framework for controlling expenses in an effort to maintain the quality and reliability of offered AI implementation within services and solutions.</p><h3>Understanding AI Infrastructure Cost</h3><p>AI infrastructure costs are a significant consideration for businesses considering offering artificial intelligence solutions. These costs typically stem from three primary factors: data storage and processing, model training and deployment, and infrastructure management.</p><h3>Data Storage and Processing</h3><p>Data management can be a substantial financial burden, as AI models often require many datasets, requiring efficient or vast storage solutions and powerful processing capabilities. This can be a large cost investment for businesses, as non-AI based solutions pivoting towards AI likely will not inherently have the capability to manage the volume of data required for an AI project.</p><h3>Model Training and Deployment</h3><p>Model training and deployment costs quickly add up, as they involve the computational power required to develop and deploy an AI model (or, more likely, multiple generative AI models). This process can strain a company’s finances, especially if frequent model updates are needed due to data drift, bug fixes or optimizations, or even changes in regulations.</p><h3>Infrastructure Management</h3><p>The need for infrastructure management adds to overall expense, as businesses must ensure that their chosen AI system(s) can handle an increase in queries. This requires an optimization of resource allocation, and maintaining infrastructure to support AI products, which can be costly to manage.</p><p>In the realm of AI technology, cost optimization is not just a financial concern; it’s a strategic imperative. As a business increasingly relies on AI features and products to drive growth, cost efficiency becomes a major business goal. Without a proper AI cost optimization strategy, AI development can quickly become unsustainable financial endeavors that can financially cripple an organization’s growth efforts.</p><p>To maintain profitability, organizations must continually assess and streamline their AI infrastructure costs through budget allocation, efficient resource utilization, and a concerted focus on eliminating unnecessary expenditures. Cost optimization not only ensures that an AI application remain financially viable but also allows businesses to direct their resources towards new features/products, research, and other strategic initiatives, ultimately maximizing the value AI can bring to the organization. By understanding that computing power will add to your overall artificial intelligence cost, you can optimize your internal business processes.</p><h3>What is API Governance?</h3><p>API governance refers to a structured framework or set of practices that dictate how APIs are deployed and managed within an organization. Governance consists of policies, procedures, and standards that “govern” the use of APIs (internally and externally) to ensure consistency, security, and compliance around more than just AI initiatives. API governance allows businesses to regulate how their software components, data, and services interact with one another or with external integrations, providing a roadmap for API development and usage.</p><p>API governance is of particular value in the realm of artificial intelligence. In an AI product, where data and models are often shared across applications and platforms, having a well-defined API governance strategy should be the cornerstone of any AI API product plan. Governance ensures that AI resources are used effectively and responsibly by employees internally and paying customers externally, enabling a financially-motivated approach to API development, deployment, and maintenance. By setting clear guidelines for AI APIs, businesses can foster interoperability, data security, and compliance with industry standards.</p><p>Because the relationship between AI and APIs is symbiotic, robust API governance can help businesses strike a balance between offering an API product with AI capability, and controlling access to AI assets. It not only streamlines the integration of AI capabilities into external applications but also ensures that AI services are secure and align with the broader goals of your organization.</p><h3>The Benefits of API Governance for Cost Control</h3><p>API governance plays a major role in controlling the costs associated with AI infrastructure by providing several essential benefits through analytics insight.</p><p>Governance frameworks ensure efficient resource allocation. AI models often require significant computational resources. With proper governance, organizations can allocate these resources optimally, preventing over-provisioning or underutilization. This process can be cost saving through means of eliminating wasteful spending on unnecessary infrastructure.</p><p>API governance also is used to enable monitoring and management of API usage by customers. By closely tracking how APIs are utilized, businesses can identify <a href="https://www.moesif.com/blog/engineering/api-monitoring/The-Difference-Between-Synthetic-API-Monitoring-and-API-Real-User-Monitoring/?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta&amp;utm_content=AI-infrastructure-costs">usage patterns</a>, bottlenecks, and potential areas for optimization. This real-time insight into API usage helps organizations make data-driven decisions, ensuring that they are investing in the right places to achieve their data science objectives effectively.</p><p>Furthermore, API governance serves as a guard against unauthorized access and misuse. It establishes access controls, authentication mechanisms, and security measures that protect sensitive AI assets from unauthorized users and potential data breaches.</p><p>API governance can be used to enhance AI product management. With facilitated version control, documentation, ensure that AI models remain up-to-date, reliable, and cost-efficient over time. Effective lifecycle management and user analytics prevent the accumulation of obsolete models that drain resources without delivering value and reduce the risk of costly errors resulting from poorly managed model updates.</p><h3>Best Practices for Implementing API Governance</h3><p>Implementing API governance is the <a href="https://www.moesif.com/blog/api-monetization/api-strategy/How-to-Enforce-API-Usage-Policies/?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta&amp;utm_content=AI-infrastructure-costs">key to maintaining control</a>, security, and efficiency for any API product, but particularly for AI operations. These policies should define who has access to AI resources, what they can do with them, and under what circumstances. Some guiding principles of API governance:</p><ul><li><strong>Establish Clear API Usage Policies</strong>: Create transparent policies that define who can access AI resources, what they can do with them, and under what conditions.</li><li><strong>Utilize Rate Limiting and Throttling</strong>: Set limits on API usage to prevent resource overconsumption and employ throttling to maintain consistent service quality internally and externally.</li><li><strong>Authentication and Access Controls</strong>: Implement strong authentication mechanisms and access controls to protect AI data and resources from unauthorized access and misuse with API keys, OAuth2 tokens, etc.</li><li><strong>Monitoring and Reporting Regularly</strong>: Continuously monitor API usage, performance, and security, and generate reports to detect anomalies, spot trends, and address issues promptly.</li><li><strong>API Versioning and Deprecation Strategies</strong>: Develop strategies to manage API versions effectively, ensuring the <a href="https://www.moesif.com/blog/api-product-management/deprecation/How-to-Properly-Deprecate-an-API-Using-Moesif?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta&amp;utm_content=AI-infrastructure-costs">orderly transition</a> from older, potentially inefficient APIs to newer, optimized ones while maintaining compatibility.</li></ul><h3>Challenges and Pitfalls</h3><p>API governance, while vital for the efficient management of AI infrastructure, is not without its challenges and potential pitfalls. There are two prominent issues that organizations face: data security and compliance concerns. Beyond the delicate equilibrium of cost control and performance optimization data security and compliance concerns are hugely important. Proper API governance must prioritize data protection, privacy, and compliance with regulatory standards, like GDPR or HIPAA. Striking the right balance between enabling access for AI-driven tasks and safeguarding data integrity is a challenge that demands extensive planning.</p><p>Additionally, a balance between cost control and performance can be challenging to achieve. Organizations need to allocate resources optimally and strategically to ensure AI systems operate without overspending or under delivering. However, an overly cost-centric approach can compromise performance and severely impact user experience.Treading carefully is essential to maximize the value of an AI infrastructure while maintaining financial sustainability for your organization at large. To navigate these challenges, companies must adopt an approach to API governance that integrates security, compliance, cost-efficiency, and performance optimization.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af469c11ea97" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moesif/a-balance-between-cost-control-and-performance-can-be-challenging-to-achievekeeping-ai-af469c11ea97">a balance between cost control and performance can be challenging to achieveKeeping AI…</a> was originally published in <a href="https://medium.com/moesif">Moesif</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[11 Most Popular Tools for Logging and Monitoring API Calls]]></title>
            <link>https://medium.com/moesif/11-most-popular-tools-for-logging-and-monitoring-api-calls-6d794a12c0f1?source=rss-32854f49697d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d794a12c0f1</guid>
            <dc:creator><![CDATA[moesif]]></dc:creator>
            <pubDate>Mon, 27 Nov 2023 00:00:12 GMT</pubDate>
            <atom:updated>2025-03-27T17:55:07.666Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UBKfAC-iTjfg7peY.png" /></figure><p>Monitoring and API logging, facilitated by various API monitoring tools, is no longer a nice-to-have — for many API providers, it has become a key part of ensuring growth and success in the ever-evolving API landscape. There are as many API monitoring tool providers as there are approaches to this topic, but we’ve gathered together a list of the top 11 in the market today. But first, let’s take a look at a few things to cosider.</p><h3>What is API Monitoring?</h3><p>API monitoring is the process of continuously tracking and analyzing the performance, functionality, and reliability of Application Programming Interfaces (APIs). It involves monitoring API calls, requests, and responses to ensure they are functioning correctly and efficiently. A well-structured API log includes timestamps, HTTP methods, endpoints accessed, request and response details, client information, and latency. By keeping a close eye on these interactions, developers can proactively identify and address issues, minimizing downtime and optimizing overall efficiency. Real-time insights into API performance and reliability enable quick troubleshooting and data-driven decision-making, ensuring that APIs deliver a seamless user experience.</p><h3>Key API Metrics to Monitor</h3><p>Monitoring key API metrics is crucial for ensuring the performance, reliability, and security of APIs. Some of the essential metrics to keep an eye on include:</p><ul><li><strong>Response Time</strong>: The time taken by an API to process a request and return a response. Lower response times indicate better performance.</li><li><strong>Error Rate</strong>: The number of API calls resulting in non-200 status codes. A high error rate can signal underlying issues that need immediate attention. Error logs provide detailed information about exceptions and errors encountered during API operations, including error messages and stack traces.</li><li><strong>Uptime</strong>: The percentage of time a service is available. High uptime is critical for maintaining user trust and satisfaction.</li><li><strong>CPU Usage</strong>: The percentage of CPU resources used by an application. Monitoring CPU usage helps in identifying performance bottlenecks.</li><li><strong>Memory Usage</strong>: The amount of memory used by an application. Efficient memory usage is vital for optimal performance.</li><li><strong>Endpoint Performance</strong>: The performance of specific API endpoints. Monitoring individual endpoints helps in pinpointing issues.</li><li><strong>API Calls per Minute</strong>: The number of API calls made per minute. This metric helps in understanding the load on the API.</li><li><strong>Log Data</strong>: The data generated by API logs, including request and response data. Analyzing log data provides deep insights into API interactions.</li></ul><h3>API Logging and Monitoring Best Practices</h3><p>Effective API logging and monitoring are critical for maintaining robust API performance. Here are some best practices to follow:</p><ul><li><strong>Log All API Requests and Responses</strong>: Ensure that every API request and response is logged for comprehensive tracking.</li><li><strong>Use a Centralized Logging System</strong>: Collect and manage log data in a centralized system for easier analysis and troubleshooting.</li><li><strong>Monitor API Performance and Reliability in Real-Time</strong>: Real-time monitoring helps in quickly identifying and addressing issues.</li><li><strong>Set Up Alerts and Notifications for Critical Issues</strong>: Configure alerts for critical issues to ensure prompt response and resolution.</li><li><strong>Use Log Data to Troubleshoot Issues and Optimize Performance</strong>: Analyze log data to identify and fix performance bottlenecks.</li><li><strong>Implement Secure Logging Practices</strong>: Protect sensitive data by following secure logging practices.</li><li><strong>Regularly Review and Refine Logging and Monitoring Practices</strong>: Continuously improve your logging and monitoring strategies to keep up with evolving needs.</li><li><strong>Use Structured Logs</strong>: Structured logs use a uniform format across all entries, facilitating easier querying and analysis.</li></ul><h3>Real-Time Monitoring and API Observability</h3><p>Real-time monitoring is essential for achieving API observability, providing instant insights into API performance and reliability. By analyzing log data and metrics in real-time, developers can quickly detect and respond to issues, optimizing API performance and reducing downtime. Real-time monitoring enables:</p><ul><li><strong>Quick Issue Detection and Response</strong>: Immediate identification of problems allows for prompt resolution.</li><li><strong>Optimized API Performance and Reliability</strong>: Continuous monitoring helps in maintaining high performance and reliability.</li><li><strong>Improved User Experience</strong>: Minimizing downtime and performance issues leads to a better user experience.</li><li><strong>Data-Driven Decision Making</strong>: Real-time insights support informed decision-making.</li><li><strong>Integration with Other Observability Tools</strong>: Seamless integration with other tools enhances overall observability.</li></ul><h3>Choosing the Right API Monitoring Tool</h3><p>Selecting the right API monitoring tool is crucial for effective API monitoring. Consider the following factors:</p><p>By considering these factors, developers can choose the right API monitoring tool for their needs, ensuring effective API monitoring and observability.</p><h3>1 — Moesif</h3><p><a href="https://www.moesif.com/features/api-logs?utm_campaign=Int-site&amp;utm_source=medium&amp;utm_medium=body-cta&amp;utm_content=most-popular-tools-for-logging">Moesif</a> is a powerful, feature-rich solution for API monitoring and tracking. Moesif also provides detailed insights into API transactions, capturing information about API requests and responses to ensure quality and performance. Rather than synthetic monitoring, Moesif provides real user monitoring, giving businesses the ability to dive into their API performance and API call data. By combining real-time event logging with product analytics (including API endpoint analysis, API testing, and API gateway integration), monetization systems (including quotas, governance, and metered billing), and alerts (both real-time and behavioral, as well as API security), Moesif promises to unlock better revenue performance, improve user retention, and generate unprecedented insight and awareness across your API.</p><h3>Benefits</h3><ul><li>Provides powerful context and deep introspection through unlocked application-layer visibility</li><li>Easy to set up across a variety of systems and implementations</li></ul><h3>Drawbacks</h3><ul><li>Governance Rules only available on enterprise tier</li></ul><h3>2 — Prometheus</h3><p><a href="https://prometheus.io/docs/prometheus/latest/management_api/">Prometheus</a> is a widely-adopted open source monitoring solution. Prometheus also excels in infrastructure monitoring, helping to ensure system reliability and performance. It has generated quite a following due to its developer outreach backing, with ample documentation, blogs, video content, etc. That being said, Prometheus was designed to generate insights based on metrics, and thus is often considered more an “insights” solution than a “logging” one. Logs are stored locally and are then pointed to by Prometheus when an issue is detected per the metrics — for this reason, users typically use Prometheus in addition to an API logging solution for remote hosting, which makes Prometheus — at least for a subset of users — a half solution for monitoring API products.</p><h3>Benefits</h3><ul><li>Well-documented and easy to implement</li><li>Ample insights generated from small amounts of data</li></ul><h3>Drawbacks</h3><ul><li>Lack of native cloud logging support</li><li>May not be a complete solve for many users</li></ul><h3>3 — Sematext</h3><p><a href="https://sematext.com/">Sematext</a> offers a very popular solution in Sematext Logs. Sematext Logs supports the creation of detailed log entries, capturing essential data for troubleshooting and performance monitoring. Sematext positions their offering as a Log Management-as-a-Service model, supporting the exfiltration of API logs from containers, infrastructure, applications, etc. It facilitates this by supporting Syslog or the Elasticsearch API, which opens it to a wide range of implementations. Because it supports these solutions, you can use Sematext natively, bypassing more expensive options which require third party solutions for performance monitoring.</p><h3>Benefits</h3><ul><li>Wide support for systems and application.</li><li>Cheaper to use than many other solutions</li></ul><h3>Drawbacks</h3><ul><li>Requires using either Syslog or Elasticsearch, which can be limiting in some situations</li><li>Requires buying into the “as-a-Service” dynamic</li></ul><h3>4 — Papertrail</h3><p><a href="https://www.papertrail.com/">Papertrail</a> is a logging solution from SolarWinds Cloud, a Software-as-a-Service solution. Each log entry in Papertrail captures critical elements like timestamps and request details, aiding in diagnosing issues. Papertrail allows for a large amount of customizability, and because it’s part of what is typically a holistic solution, it offers substantial cross-service and cross-database API logging that is often much slower and more expensive in other solutions. The drawback, of course, is that Papertrail works best as part of the SolarWinds Cloud service — and if you’re not using that service, your experience may not be as good as it could be with other open-source or free software solutions. If you currently are a SolarWinds customer, the best solution for your API monitor may be Papertrail.</p><h3>Benefits</h3><ul><li>Highly customizable</li><li>Cross-service and cross-database</li></ul><h3>Drawbacks</h3><ul><li>Part of a suite of offerings that do better as part of SolarWinds Cloud</li><li>Not robustly open-source</li></ul><h3>5 — Checkly</h3><p><a href="https://www.checklyhq.com/">Checkly</a> is a very new player in the logging software scene, but it brings a lot to the table. Checkly provides insights into key metrics such as response times and error rates, crucial for evaluating API performance. Beyond its powerful synthetic monitoring and API logging, it also allows for deep contextual inspection, diving into payload, responses, headers, and more. Latency, which refers to the time delay between API request and response time, is another critical metric Checkly helps to monitor. This amount of logging and API analytics provide a great amount of context and can improve your visibility quite significantly through application performance monitoring. Pricing is relatively simple and follows a freemium model — that being said, more complex environments might quickly run above the relatively modest 10,000 API calls in the free plan, and the custom plan may have higher costs compared to something that is self-hosted.</p><h3>Benefits</h3><ul><li>Relatively inexpensive</li><li>Provides high context</li></ul><h3>Drawbacks</h3><ul><li>Very new player, so not as proven</li><li>Limited freemium offering</li></ul><h3>6 — Datadog</h3><p><a href="https://www.datadoghq.com/">Datadog</a> bills itself as an observability platform, offering a relatively feature-complete solution for logging, website monitoring, application monitoring, and reporting for REST API-based products and beyond. Datadog’s suite of monitoring tools provides real-time insights into API performance and reliability. It allows users to set specific metric-based rules to generate alerts across channels like Slack, SMS, email, etc. Datadog is relatively cheap, which is a big reason it has seen good adoption across the board — that being said, it doesn’t provide as much detail as some other solutions in the marketplace, making it a good generalist middle-of-the-road API management solution.</p><h3>Benefits</h3><ul><li>Feature-complete compared to others on this list</li><li>Relatively cheap to deploy</li></ul><h3>Drawbacks</h3><ul><li>Limited detail compared to other solutions</li></ul><h3>7 — Sauce Labs</h3><p><a href="https://saucelabs.com/">Sauce Labs</a> used to be called API Fortress, and under that name, it generated a bit of a reputation as a cloud-based REST API monitoring solution. Setting up Sauce Labs for monitoring involves establishing secure connections to ensure data integrity and security. Sauce Labs continues this success by providing testing, monitoring, and reporting, but for those looking principally for API log tooling, Sauce Labs can seem a bit too feature-complete. Ultimately the use case for Sauce Labs is a bit of column A and column B — if you want to collect API logs for the purpose of generating reports and insights, Sauce Labs is a great solution. If you want to log to just log, this might be another in the column of “too good for what you need”.</p><h3>Benefits</h3><ul><li>Very mature in the market</li><li>Widely adopted giving a huge user community</li></ul><h3>Drawbacks</h3><ul><li>Perhaps too mature for those looking only for logging</li><li>A bit too general for specific use cases</li></ul><h3>8 — Amazon CloudWatch</h3><p><a href="https://aws.amazon.com/cloudwatch/">Amazon CloudWatch</a> brings the proven logging and monitoring approaches on offer from Amazon. Amazon CloudWatch is one of the most flexible API monitoring tools available, offering robust logging and monitoring capabilities. This solution is relatively robust, but the main selling point is in the pricing model — CloudWatch is very flexible, offering pay-as-you-go, which allows for easy scaling. That being said, the solution is tooled specifically for the AWS API gateway, which makes it a hard sell to anyone not utilizing AWS systems. Because of the usage based nature of CloudWatch’s payment structure understanding the performance metric that eat your budget can help guide the decision to use CloudWatch for uptime monitoring or synthetic API monitoring.</p><h3>Benefits</h3><ul><li>Relatively efficient and feature rich</li><li>Pay-as-you-go pricing makes it flexible</li></ul><h3>Drawbacks</h3><ul><li>Tooled for AWS specifically, which may exclude it from some stacks</li></ul><h3>9 — AppDynamics</h3><p><a href="https://www.appdynamics.com/">AppDynamics</a> is particularly powerful and is backed by the Cisco product offering. It offers real-time data visualization and analysis, and provides relatively robust solutions like resource waterfalls to show the impact of each element of the API service in the overall efficiency and user experience. AppDynamics provides comprehensive monitoring for any application programming interface, ensuring optimal performance and reliability. That being said, this is another offering that is run by a corporate entity, and its quite expensive — for many developers, this might be a huge negative that is difficult to overcome no matter how beautiful the visualizations are in practice.</p><h3>Benefits</h3><ul><li>Backed by Cisco and its mature product offering</li><li>Real-time data visualization</li></ul><h3>Drawbacks</h3><ul><li>Not open source and corporate in nature</li><li>Quite expensive</li></ul><h3>10 — Uptrends</h3><p><a href="https://www.uptrends.com/">Uptrends</a> offers a robust multi-step logging and API monitoring tool, selling itself as a logging and alerting system first and foremost. Uptrends offers “Private Checkpoints”, a solution that unlocks testing behind private networks and firewalls. Uptrends is very clearly leaning on its solution as a “problem resolution” one, with one area of the site boasting “Yesterday we detected 332k errors. How’s your site doing?”. The main drawback here is that Uptrends is very clearly selling itself as an analysis tool rather than just an API log tool. For developers looking for logging — and just logging — Uptrends is too far down the monitoring path.</p><h3>Benefits</h3><ul><li>Robust logging and monitoring</li><li>Works on private systems and networks</li></ul><h3>Drawbacks</h3><ul><li>Monitoring-heavy makes logging a second thought</li><li>Provides ample analysis which may just be a cost increase vs. a utility increase for some stacks</li></ul><h3>11 — Graphite</h3><p><a href="https://graphiteapp.org/">Graphite</a> is an open source monitoring and logging system that utilizes a push-based design architecture. What this means is that Graphite allows services to push their API logs into a component called Graphite Carbon, which is then stored in a database for later deep introspection and transformation. Prometheus, another open-source monitoring toolkit designed for cloud-native applications, is often used alongside Graphite for enhanced monitoring capabilities. Graphite’s main selling point is its easy deployment through its native Synthesize product, an automated installation and configuration system which promises to get users up and running with minimal headache.</p><h3>Benefits</h3><ul><li>Open source and feature-rich</li><li>Easy deployment</li></ul><h3>Drawbacks</h3><ul><li>Depends on its own solutions — may be stack limiting</li></ul><p>We hope this list has helped you see the offerings in the current marketplace. Please note that this list is not exhaustive — nonetheless, it provides a good overview of the most common solutions available today! Feel free to let us know if there are more solutions you’d love included in this list.</p><p><em>Originally published at </em><a href="https://www.moesif.com/blog/api-analytics/api-strategy/11-Most-Popular-Tools-for-Logging-and-Monitoring/"><em>https://www.moesif.com</em></a><em> on November 27, 2023. Updated on </em>March 24, 2025.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d794a12c0f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moesif/11-most-popular-tools-for-logging-and-monitoring-api-calls-6d794a12c0f1">11 Most Popular Tools for Logging and Monitoring API Calls</a> was originally published in <a href="https://medium.com/moesif">Moesif</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Secret to Building an Effective Customer Success Dashboard]]></title>
            <link>https://medium.com/moesif/the-secret-to-building-an-effective-customer-success-dashboard-8d000df2e0e3?source=rss-32854f49697d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d000df2e0e3</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[saas-marketing]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[moesif]]></dc:creator>
            <pubDate>Fri, 10 Nov 2023 22:26:00 GMT</pubDate>
            <atom:updated>2023-11-10T22:26:00.279Z</atom:updated>
            <content:encoded><![CDATA[<p>The secret to customer success is making your customers happy and supporting them to succeed. A simple concept — until you try to implement it. You’ll need a great product and a great customer service team, for starters. You’ll also need an in-depth understanding of the customer experience, including their pain points and how you can help solve them.</p><p>This is where things get trickier, but the answer could already be tucked away in your data. All you need is an effective customer success dashboard to automate the identification of issues and then support you to solve them — as the dashboard example below demonstrates.</p><h3>Customer Success KPI Dashboard Example</h3><blockquote><em>”A couple of years ago, when we encountered errors from sub-optimal client API practices, we might share a permalink with a team member so they could look at logs. That worked reasonably well, but you’re still sifting through logs. Now, events that belong together can be grouped and easily shared in a dashboard. Issues can then be proactively addressed, resulting in better customer experiences.” Conrad Caplin, Co-Founder, Pronto CX.</em></blockquote><h3>What is a Customer Success Dashboard?</h3><p>When it comes to understanding and enabling <a href="https://www.moesif.com/blog/customer-success/monitoring/Data-Driven-Customer-Success-and-How-API-Data-Provide-the-Leading-Indicator-of-Account-Health/?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta">customer success</a>, implementing an effective customer success dashboard that enables swift key performance indicator (KPI) analysis should be at the heart of your approach.</p><p>A customer success dashboard is a visual tool that helps you to track everything from how your product is being used to your retention rate, churn rate, monthly revenue and more.</p><h3>Why are Customer Success Dashboards Important?</h3><p>A good customer success KPI dashboard is a testament to the difference that such a dashboard can make to customer satisfaction. It enables an organization to implement both reactive and proactive measures to drive up its customer success levels.</p><p>Retaining users starts with understanding the steps at which they get stuck when using your product and why. Generally, organizations have historically employed a reactive strategy to API problems, giving their customers an opportunity to grow impatient and become at risk for canceling their contracts. Through a customer success driven strategy, automate the monitoring and display of API usage and gain customer insights. Identify situations where your company can proactively intervene and help your customers be successful.</p><h3>How Do You Measure Customer Success KPI?</h3><p>Customer success dashboards can support the journey from <a href="https://www.brightgauge.com/blog/customer-success-dashboards">new customer</a> to loyal, retained customer. To monitor that journey, you need to measure various customer success KPIs. Some of the most important include:</p><ul><li>Customer churn rate</li><li>Customer lifetime value</li><li>Monthly recurring revenue</li><li>Customer support tickets</li><li>Net promoter score</li><li>Customer satisfaction</li></ul><p>You can also add in any KPI that will support understanding your own customers’ success and monitoring it, such as API calls as in the customer success API dashboard example above.</p><h3>Customer Success Overview Dashboard Template</h3><p>Your customer success overview dashboard template will be shaped around your specific product. That said, it’s possible to outline some broad examples of what such a dashboard should include.</p><h3>What Should Be on a Customer Success Dashboard?</h3><p>Start by understanding what success means to your customers and what your goals are. After all, <a href="https://www.softwareag.com/en_corporate/customers/customer-stories.html">customer success stories</a> vary hugely from business to business.</p><p>What you monitor is up to you. Say you have a sales rep who has implemented behavioral emails to try and accelerate API integration. You can monitor the impact on your dashboard.</p><p>Your dashboard will be a mix of customer health indicators and KPIs, monitoring both positive and negative customer success metrics. Positive metric examples include number of new customers and monthly recurring revenue. Churn rate, meanwhile, is an example of a negative metric.</p><h3>How Do You Measure the Effectiveness of a Dashboard?</h3><p>You can measure the effectiveness of your customer success dashboard by monitoring your overall customer satisfaction and success levels. Another measure of effectiveness is the return on investment that your dashboard delivers.</p><h3>What are 3 Benefits of a Dashboard?</h3><p>When it comes to customer success, a dashboard delivers multiple benefits. Three of the most useful are:</p><ul><li>Reducing customer churn</li><li>Creating more stable revenue</li><li>Increasing customer satisfaction</li></ul><p>By supporting your customers’ success, you’re supporting your own.</p><h3>View Customer Success Metrics and Gain Insights</h3><p>We touched on customer success metrics when talking about KPIs above. Monitoring rates such as <a href="https://www.moesif.com/blog/developer-marketing/Market-Your-SaaS-Platform-To-Developers/?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta">customer churn</a> provides an overview of customer success that can drive unique insights into your customer experience and your own business.</p><p>Key to identifying the customer success metrics that will provide the most useful and comprehensive oversight is understanding what your <a href="https://weld.app/blog/top-customer-success-metrics">customer needs</a>. You can then track your success in meeting those needs through relevant metrics.</p><h3>How Do You Track Customer Success?</h3><p>Being able to view customer success metrics and gain insights is hugely valuable. But how do you do it?</p><p>To track customer success, you need to implement a range of metrics that can provide an overview of your progress. Let’s take a look at a few of these.</p><h3>What are the Important API Customer Success Metrics?</h3><p>The most important API customer success metrics for your business will be those that dive into the detail of what you’re achieving. Examples of such metrics include:</p><p><em>Customer retention rate</em></p><p>It’s all very well winning new business, but if your customers don’t stick with your product, you have a problem. Tracking what proportion of your customers you retain over time is key not just to understanding your customer success performance but to supporting the long-term viability of your enterprise.</p><p><em>Customer health score</em><br><br>You can use a customer health score to determine what proportion of your customers are ‘healthy’ and what proportion are ‘at risk’. On an individual customer basis, this helps you identify which customers are likely to grow and which you are at risk of losing. At an organizational level, it can serve as an early warning system if you identify a growing proportion of customers at risk.</p><p><em>Net promoter score</em></p><p>A long-established tool in market research, as well as in monitoring customer success and business growth, your net promoter score relates to the proportion of people who would recommend your business (or product) to a friend or colleague. Tracking your net promoter score can reveal a great deal about how positively (or otherwise!) your customers view your business.</p><p><em>Customer lifetime value</em></p><p>Monitoring customer lifetime value tells you what a customer is worth over the entire period of their relationship with your business. Calculating your customer lifetime value and then monitoring it to ensure that it increases is an effective way to track your growing customer success.</p><p><em>Customer churn rate<br></em><br>The lower your customer churn rate, the better. After all, it costs your business more to go out and find new customers than it does to retain existing ones. As such, working to reduce your churn rate can deliver long-term rewards.</p><p><em>Monthly recurring revenue</em><br><br>Your monthly recurring revenue is the amount of income that you get from your customers each month. Tracking it is essential to understanding your customer success performance and to monitoring the financial viability of your business.</p><p><em>Customer retention costs</em><br><br>We mentioned above that it’s cheaper to retain customers than go out and find new ones, but retaining customers is far from cost-free. By measuring the cost of your customer success work and comparing it to your number of customers, you can monitor how much it costs to retain each customer.</p><p><em>Customer satisfaction score</em><br><br>A customer satisfaction score measures, quite simply, how satisfied your customers are with your business. It is an excellent indicator of customer success, particularly when combined with the metrics detailed above. Together, they provide a comprehensive overview of your customer success performance.</p><h3>Making a Success of Customer Success Dashboards for API Products</h3><p>Customer success dashboards for API products are a hugely important tool for understanding the impact that those products can deliver and the implications of that impact for the overall success of your business.</p><p>If you’re ready to implement a customer success API dashboard, why not get in touch with the Moesif team to discover how we can help you analyze, interrogate and monitor your customer success data?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d000df2e0e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moesif/the-secret-to-building-an-effective-customer-success-dashboard-8d000df2e0e3">The Secret to Building an Effective Customer Success Dashboard</a> was originally published in <a href="https://medium.com/moesif">Moesif</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Dynamic Sampling and How it Works]]></title>
            <link>https://medium.com/moesif/what-is-dynamic-sampling-and-how-it-works-14af8258315e?source=rss-32854f49697d------2</link>
            <guid isPermaLink="false">https://medium.com/p/14af8258315e</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[moesif]]></dc:creator>
            <pubDate>Fri, 03 Nov 2023 23:17:19 GMT</pubDate>
            <atom:updated>2023-11-03T23:17:19.207Z</atom:updated>
            <content:encoded><![CDATA[<p>Sometimes you may want to limit the amount of analytics data coming into Moesif. This could be because you want to exclude specific traffic, such as internal or health check traffic, or you may want to reduce unnecessary data to control cost. Dynamic Sampling, available to customers on our Enterprise plan, was built to do just this. Dynamic Sampling lets you control which API calls are logged to Moesif based on customer or API behavior. Moesif intelligently extrapolates metrics for accurate reporting even with multiple sample rates. That means that no matter what rules or sample rates you have set up, you can be sure you are still seeing an accurate representation of your data.</p><p>Dynamic Sampling is controlled by setting up sampling rules in the Moesif Dashboard. You can create rules based on criteria such as request path, response status codes, user or company behaviors, and more. You can also control the applied sample rate for each rule. The sample rate is the percentage of events that will make their way into Moesif. For example, if you set a rule to sample 50% of events, Moesif will log half of the matching events intelligently (and not just log every other event to meet the 50% sampling rate).</p><h3>Why use Dynamic Sampling</h3><p>Our Dynamic Sampling feature serves two use cases for customers:</p><ul><li>Gives users the capability to trim down excessive or uninteresting calls populating within Moesif while retaining the insight you gain from the platform.</li><li>Allows users to reduce their Enterprise subscription costs and save money. Moesif considers the sampling rules you have created and intelligently extrapolates usage metrics.</li></ul><blockquote>Sampled API calls do not count against your quota; for example, if your API usually sees 1 million API calls per month but the global sample rate is set to 25%, only the 250 thousand events per month coming into Moesif will count towards that quota.</blockquote><h3>When not to use Dynamic Sampling</h3><p>It would be best if you avoided Dynamic Sampling on specific events moving into Moesif. These use cases include when you are leveraging with other Moesif features like <a href="https://www.moesif.com/solutions/metered-api-billing?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta&amp;utm_content=What-Is-Dynamic-Sampling">Metered Billing</a> or <a href="https://www.moesif.com/features/api-governance-rules?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta&amp;utm_content=What-Is-Dynamic-Sampling">Governance Rule</a> where you’ll want every call to be assessed in Moesif.</p><p>Dynamically sampling the number of API calls coming into Moesif would impact a monetized API because it would fail to track the exact usage, likely missing some events depending on the sampling rate applied. This will affect your billing meters and the invoices being sent to customers. However, a way around this is to apply Dynamic Sampling to endpoints that are not monetized and let events counted within your Billing Meter sample at 100%.</p><p>Another reason not to use Dynamic Sampling is when your logged API calls are less than the number of calls your subscription plan supports. For example, suppose you are making fewer API calls than your subscription plan includes. In that case, dynamic sampling is unnecessary unless you are simply trying to exclude data you don’t want in Moesif to keep data cleaner. Examples of this may be not including traffic from health check probes or internal testing.</p><h3>Four types of sample rates</h3><p>Dynamic Sampling rules are categorized into four kinds of sample sets and are prioritized in the following manner:</p><ul><li>Sample rates for a single user or company</li><li>Sample rates based on regex rules</li><li>Sample rates based on user behaviors and demographics (<a href="https://www.moesif.com/docs/user-analytics/saved-cohorts/?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta&amp;utm_content=What-Is-Dynamic-Sampling">Saved Cohorts</a>)</li><li>Sample rates applied globally</li></ul><p>This means that if a sample rate is set for a specific customer, this will take priority over a sample rate associated with a behavioral cohort that a customer belongs to. Global sample rates have the lowest priority and are, by default, set to 100% for all customers. If an API call matches multiple rules, it gets processed by the first kind of sample rate in the prioritization hierarchy.</p><h3>How to create Dynamic Sampling rules in Moesif</h3><p>Now that you’ve learned what Dynamic Sampling is and what it can do. Let’s briefly look at how to set up some Dynamic Sampling rules. First, navigate to the <strong>Dynamic Sampling</strong> screen within Moesif.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qhsbIPEVbK62QENQ.png" /></figure><p>Here is where we can access all of the sampling rates that have been created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QGfIXBUzcgXvq55k.png" /></figure><p>Selecting the <strong>+ Rule</strong> button will allow us to create new user or company, regex, or cohort sampling rules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FP21KywEeVQICnHu.png" /></figure><h3>Specific users or companies</h3><p>After selecting either <strong>New User Rule</strong> or <strong>New Company Rule</strong>, select the <strong>user lookup</strong> or <strong>company lookup</strong> button, respectively.</p><blockquote>In this example we will be showcasing the user lookup however the process is the same for companies.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GdiEZSmRjwV4DCxq.png" /></figure><p>Proceed to select an <strong>ID</strong> from the user list to enter a their <a href="https://www.moesif.com/docs/getting-started/users/?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta&amp;utm_content=What-Is-Dynamic-Sampling"><strong>Profile View</strong></a>. You can use the <strong>Users Where</strong> filter to quickly get at the user you are looking for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZrFASekp_WMPVJoV.png" /></figure><p>On the Profile View under Sample Rate, select the pencil icon to change the specific user’s sample rate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z7FzA761EP4f-btV.png" /></figure><p>Disable the inherit toggle to allow adjustments of the user’s sample rate. Set the desired sample rate by typing in the rate manually, or by using the slider, and select save.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rN-qt9lP0C_dJkgZ.png" /></figure><h3>Regex rules</h3><p>Returning to the Dynamic Sampling rules page, select <strong>New Regex Rule</strong> in the <strong>+ New</strong> dropdown, enter your desired criteria and sample rate and save it. In this example; we have set the sampling rate to zero to exclude all <em>GET</em> requests to any of our health endpoints. These calls will not appear in the UI or count against our event quota.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cIzgl4_lFNXgGxJV.png" /></figure><h3>Behaviors or demographics via Saved Cohorts</h3><blockquote>Behavior and demographic sampling is accomplished by utilizing <a href="https://www.moesif.com/docs/user-analytics/saved-cohorts/?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta&amp;utm_content=What-Is-Dynamic-Sampling">Saved Cohorts</a>; if you are unfamiliar with Saved Cohorts check out our <a href="https://www.moesif.com/blog/technical/api-analytics/Saved-Cohorts-The-What-Why-And-How?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta&amp;utm_content=What-Is-Dynamic-Sampling">blog post</a>, <a href="https://www.moesif.com/docs/guides/guide-creating-saved-cohorts/?utm_campaign=Medium&amp;utm_source=placed-article&amp;utm_medium=body-cta&amp;utm_content=What-Is-Dynamic-Sampling">written guide</a>, or <a href="https://youtu.be/gwdV9B1ibOY">video guide</a> to learn more.</blockquote><p>Setting sampling rates for cohorts is quite easy. Select the <strong>+ New</strong> button on the Dynamic Sampling rules page then either <strong>New User Rule</strong> or <strong>New Company Rule</strong>. A modal will appear letting you select a perviously saved cohort. Continue to set your desired sample rate as well as the priority. Priorities are ordered within user or company cohorts. User sample rules always takes precedence over company sample rules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*olsj1FLRau1AdMCs.png" /></figure><h3>Globally</h3><p>You can apply global rules by clicking the <strong>Settings</strong> button on the Dynamic Sampling rules page. The resulting modal that appears allows you to set the global sample rate, suppress known bot traffic, as well as stop traffic from given IP addresses either expressly or through regex rules. The bottom of the modal showcases all users or companies that have their sample rates set within their respective user profiles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AW9-j3wRqsKWe0m0.png" /></figure><h3>Try it out</h3><p>For many reasons, Dynamic Sampling can be an essential part of your Moesif configuration. We also reviewed some limitations and scenarios where Dynamic Sampling would not be the best choice, such as when applying a Billing Meter or Governance Rule to an endpoint. Lastly, we went through how to set up different types of rules within Moesif itself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14af8258315e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moesif/what-is-dynamic-sampling-and-how-it-works-14af8258315e">What is Dynamic Sampling and How it Works</a> was originally published in <a href="https://medium.com/moesif">Moesif</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Get Customer and Application Context When Logging API Calls for 3scale API Gateway]]></title>
            <link>https://medium.com/moesif/how-to-get-customer-and-application-context-when-logging-api-calls-for-3scale-api-gateway-bd9bcb677de7?source=rss-32854f49697d------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd9bcb677de7</guid>
            <category><![CDATA[api-development]]></category>
            <category><![CDATA[3scale]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[moesif]]></dc:creator>
            <pubDate>Thu, 26 Oct 2023 21:34:54 GMT</pubDate>
            <atom:updated>2023-10-26T21:34:54.987Z</atom:updated>
            <content:encoded><![CDATA[<p>As APIs handle enormous amounts of data of a widely varying type, the critical question for any data provider is how specifically to secure this data. An authentication method that gives power to developers to build applications for all of their needs, determines who could access the APIs to protect sensitive data and ensure the request aren’t tempered. Authentication is when an entity proves an identity. Simply put, authentication is the act of verifying that you are who you claim to be. Without authentication, there wouldn’t be an easy way to associate requests with the specific user data and no way to protect requests from malicious users that might delete other user’s data. Authentication shouldn’t be an afterthought but rather built into the very fabric of your API.</p><h3>Authentication Patterns</h3><p>Depending on our API we may need to use different authentication patterns to issue credentials for access to our API. These can range from API keys to custom configurations.</p><p>3Scale supports the following authentication patterns:</p><h4>Standard API Keys</h4><p>An authentication model where a single randomized strings or hashes acts as an identifier and a secret token. Each application with permissions on the API has a single unique string. By default the name of the key parameter is user_key. We can use this same label or choose another label before making the authorization calls to 3scale.</p><h4>Application Identifier and Key pairs</h4><p>An authentication model where the immutable identifier — Application Id (App_Id) and mutable secret key strings — Application Keys (App_Keys) are separated into two tokens. The App_Id is constant and may or may not be secret. Each application may have 1-n Application Keys where each key is associated directly with App_Id and should be treated as secret.</p><p>In 3Scale, each service could use a different authentication pattern but only one pattern could be used per service. In the authentication section, we could choose the required Authentication mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NT6-z6DjigvqZRaN.png" /></figure><h3>Application Context</h3><p>3Scale provides an admin API endpoint to fetch application context associated for each user. Application context contains the details associated with an individual user about their interaction with 3Scale APIs like first_traffic_at, first_daily_traffic_at and other personally identifiable information data like - user_id, user_account_id, service_id, plan information and other details. With access to these details, it would be easy to associate requests with the specific user.</p><p>Depends on the authentication method we use, we call the admin endpoint to fetch the application context. While using the standard API keys authentication method, we fetch the application context by calling this endpoint -</p><pre>curl -v -X GET &quot;https://#{domain}/admin/api/applications.xml?access_token=#{ADMIN_ACCESS_TOKEN}&amp;user_key=#{user_key}&quot;</pre><p>While using the application identifier and key pairs authentication method, we fetch the application context by calling this endpoint -</p><pre>curl -v -X GET &quot;https://#{domain}/admin/api/applications.xml?access_token=#{ADMIN_ACCESS_TOKEN}&amp;app_id=#{app_id}&amp;app_key=#{app_key}&quot;</pre><h3>Setting Up Moesif API Analytics with 3Scale</h3><p>Moesif has a <a href="https://luarocks.org/modules/moesif/lua-resty-moesif">plugin available in the Luarocks</a> to capture API requests and responses and log to Moesif for easy inspecting and real-time debugging of your API traffic via 3Scale. The plugin captures metrics locally and queues them which enables the plugin to send metrics data to the Moesif collection network out of band without impacting your app.</p><p>The recommended way to install Moesif is via Luarocks:</p><pre>luarocks install --server=http://luarocks.org/manifests/moesif lua-resty-moesif</pre><h3>Authentication Credentials Location</h3><p>3Scale provides flexibility to an end-user to pass authentication credentials via HTTP_Headers or as query_parameters while calling an API. Moesif would look for the credentials in both headers and query parameters and fetch the application context for that particular user. Moesif provide a configuration option to set the field name which is the same name used while configuring the API authentication setting. By default, 3Scale uses user_key for standard API Key and app_id and app_key for App_Id and App_Key pair authentication method.</p><h3>Identify User and Company (Account)</h3><p>The admin endpoint returns the application context as a XML entity. Moesif provides a configuration option to set the field name from 3Scale’s application XML entity which will be used to identify the user and the company (account). The field name are id and user_account_id by default for user and company, but other valid examples include user_key and service_id.</p><pre>-- Function to parse 3Scale XML entity<br>-- @param `user_id_name` The 3scale field name from 3scale&#39;s application XML entity used to identify the user. Default `id`.<br>-- @param `company_id_name` The 3scale field name from 3scale&#39;s application XML entity used to identify the company (account). Default `user_account_id`.<br>-- @param `debug`  A flag to print logs<br>function parseXML(user_id_name, company_id_name, debug)<br>    -- config_response is the response from an api call to fetch application context which is a XML entity <br>    local response_body = config_response:match(&quot;(%&lt;.*&gt;)&quot;)<br>    if response_body ~= nil then <br>        local xobject = xml.eval(response_body)<br>        local xapplication = xobject:find(&quot;application&quot;)<br>        if xapplication ~= nil then<br>            local xtable = {}<br>            for k, v in pairs(xapplication) do<br>                if v ~= nil and type(v) == &quot;table&quot; then <br>                    xtable[v:tag()] = k<br>                end<br>            end</pre><pre>            local key = xapplication[xtable[user_id_name]]<br>            if key ~= nil then <br>                if debug then<br>                    ngx.log(ngx.DEBUG, &quot;Successfully fetched the userId &quot;)<br>                end<br>                -- Set the UserId<br>                local user_id = key[1]<br>            else <br>                if debug then<br>                    ngx.log(ngx.DEBUG, &quot;The user_id_name provided by the user does not exist &quot;)<br>                end<br>            end<br>            local companyKey = xapplication[xtable[company_id_name]]<br>            if companyKey ~= nil then <br>                if debug then<br>                    ngx.log(ngx.DEBUG, &quot;[moesif] Successfully fetched the companyId (accountId) &quot;)<br>                end<br>                -- Set the CompanyId (AccountId)<br>                local company_id = companyKey[1]<br>            else <br>                if debug then<br>                    ngx.log(ngx.DEBUG, &quot;[moesif] The company_id_name provided by the user does not exist &quot;)<br>                end<br>            end<br>        else<br>            if debug then<br>                ngx.log(ngx.DEBUG, &quot;Application tag does not exist &quot;)<br>            end<br>        end<br>    else<br>        if debug then<br>            ngx.log(ngx.DEBUG, &quot;Xml response body does not exist &quot;)<br>        end<br>    end<br>end</pre><h3>Conclusion</h3><p>In this way, the plugin would link every event or action to an individual customer and behavioral trends can be discovered by looking at multiple events together to identify product issues such as why users stop using your API or which features or endpoints they engage with the most.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd9bcb677de7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/moesif/how-to-get-customer-and-application-context-when-logging-api-calls-for-3scale-api-gateway-bd9bcb677de7">How to Get Customer and Application Context When Logging API Calls for 3scale API Gateway</a> was originally published in <a href="https://medium.com/moesif">Moesif</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>