<?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 Brenton House 🕵️‍♂️ on Medium]]></title>
        <description><![CDATA[Stories by Brenton House 🕵️‍♂️ on Medium]]></description>
        <link>https://medium.com/@brentonhouse?source=rss-1bbcfdf4e397------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6_uv9HDMis-FHClhTWXH5w.jpeg</url>
            <title>Stories by Brenton House 🕵️‍♂️ on Medium</title>
            <link>https://medium.com/@brentonhouse?source=rss-1bbcfdf4e397------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:58:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brentonhouse/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[API First Strategy Explained]]></title>
            <link>https://medium.com/brentonhouse/api-first-strategy-7544fb11f00c?source=rss-1bbcfdf4e397------2</link>
            <guid isPermaLink="false">https://medium.com/p/7544fb11f00c</guid>
            <dc:creator><![CDATA[Brenton House ️‍♂️]]></dc:creator>
            <pubDate>Wed, 26 Jan 2022 17:59:31 GMT</pubDate>
            <atom:updated>2022-01-31T19:00:51.547Z</atom:updated>
            <content:encoded><![CDATA[<p>Understanding API First Strategy and benefits of API-led Integration</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_To8IkwOw4C_0JuebjCPhA.jpeg" /><figcaption>Understanding API First Strategy and benefits of API-led Integration</figcaption></figure><h3>What is an API First Strategy?</h3><p>API First is more than building an API for every product you have. API First is a strategic and tactical methodology for how you view your products and your business and about adopting a mindset where your products are capabilities that you can deliver. API First focuses on the business value of APIs and what they deliver.</p><p>An API First and API-led Integration Strategy is essential to every organization. The companies that are adopting an API First Strategy are the ones that are gaining ground the quickest in the growing API Economy. API First allows you to view your business as a set of API Products that work together to provide the features, data, and capabilities that your organization’s products produce.</p><p>APIs are what enable businesses to engage with consumers in the digital world and are how your products are going to be judged in the API Economy.</p><p>How fast are things moving in the API Economy? Let’s take a look.</p><h3>What happens in a minute?</h3><blockquote>A lot can happen in a minute.</blockquote><p>In a single minute:</p><p>UPS will deliver 11,319 packages</p><p>Apple will make a little over $70k dollars</p><p>In a single minute, over $3 million dollars will be donated to charities around the world.</p><p>In the next 60 seconds, over 700K telephone calls will be made.</p><blockquote><em>60 seconds is not a lot of time but it is enough time for a lot to happen.</em></blockquote><h3>A lot can also happen in a digital minute</h3><p>In fact, according to the <a href="https://www.domo.com/blog/what-data-never-sleeps-9-0-proves-about-the-pandemic/">2021 results compiled by Domo</a>, a lot DOES happen in a digital minute.</p><p>These are some pretty big numbers.</p><p>For instance, in the next 60 seconds:</p><ul><li>People watch 694K hours of videos on YouTube</li><li>Twitter users post 575k tweets</li><li>Slack users send 148k messages</li><li>Users stream 452k hours of video on Netflix</li><li>Google conducts 5.7M searches</li><li>12M people send an iMessage</li><li>6M people shop online</li><li>Users send 2M SnapChats</li><li>People watch 167M videos on TikTok</li></ul><p>The list goes on and on but there is one thing in common.</p><blockquote><em>All of these services (and more!) are powered by APIs.</em></blockquote><h3>Why APIs?</h3><p>Whether or not you are creating your own APIs you are consuming and using APIs. Everything runs on APIs.</p><blockquote><em>APIs enable the Digital Ecosystem</em></blockquote><p>So instead of asking Why APIs? a better question might be Why API Management and Governance?</p><p>API Management and governance have become a crucial part of the API Economy and the strategy and priories of businesses and enterprises around the world.</p><p>But let’s take a look at the world without them.</p><p>In a world without API Governance, we have:</p><ul><li>No Central Governance over Design and Development</li></ul><blockquote>The design for an API and integrations with other systems can have a huge impact on the direction and success of an API program.</blockquote><ul><li>No Full Lifecycle API Management</li></ul><blockquote><em>Full Lifecycle API Management covers everything from design and development of an API all the way through to retirement of an API.</em></blockquote><ul><li>No API Policy Enforcement</li></ul><blockquote>API Policies cover and enforce security and so much more</blockquote><ul><li>No Monetization of APIs</li></ul><blockquote>API Monetization is is not just referring to APIs that you sell or license. This is also talking about using APIs to leverage the business value of your other digital and physical products and services. It could also be controlling access or rate limiting APIs in order to be more secure or to protect resources from expensive traffic hits.</blockquote><ul><li>No Visibility over API Usage</li></ul><blockquote><em>How are APIs being used? (This goes for Public APIs / Internal APIs / Partner APIs / 3rd Party APIs)</em></blockquote><ul><li>Many Challenges for API Reuse</li><li><em>What APIs do we have?</em></li><li><em>What 3rd Party APIs are we using?</em></li><li>*Controlling access to APIs that are reused *</li><li><em>What about versioning? What version of an API is being reused?</em></li><li><em>The same goes for updates? Will APIs that are being reused be updated or patched when the original is updated?</em></li></ul><h3>What it looks like with an API Digital Ecosystem that is properly managed</h3><ul><li>Portfolio Consolidation of existing and overlapping services</li><li>Rapid integration API catalog with existing technology</li><li>Visibility to enable governing and managing full API lifecycle and API reuse</li><li>Scalable and flexible integration of new microservices components</li><li>Mitigating risks by enabling future modernization through APIs</li></ul><p>To do this you have to have a solid plan that includes these important goals:</p><h3>Creating an API-led Integration Strategy</h3><p>APIs and Integrations are at the heart of Digital Transformation and an API-led integration strategy can ensure that you are equipped to succeed. A clear API strategy will allow you to transform your data and processes into digital capabilities that add value to your organization.</p><h3>Securing Executive Backing</h3><p>One of the key concepts behind a successful API Strategy is having executive backing. Identifying who all the stakeholders will be (both internal and external) is an important first step. It is important for everyone to realize their role, from executives, management, IT, Marketing, and Accounting… Everyone is a player in this game. Everyone needs to be invited to take ownership of the adoption, use of, and support of the API Program and its role in the Digital Transformation journey of your organization.</p><p>With stakeholders identified, executive backing and participation can remove a lot of possible friction points that might exist when making changes in an organization to support the adoption of an API program and strategy.</p><p>This is a critical step.</p><p>An API program and strategy needs to be executive-driven. Without good leadership and sufficient resources, API programs can become weak and fail.</p><h3>Defining the Goals of your API Program</h3><p>What are the goals and objectives of your API program? What do you see being accomplished through the successful implementation of your API Strategy?</p><p>Some common outcomes and goals that organizations might target include:</p><ul><li>Securely managing access to data for customers, partners, and employees.</li><li>Open more opportunities for integrations with and from third parties.</li><li>Remove friction by making data more accessible through self-service channels.</li><li>Increase revenue by leveraging APIs and integrations with other products and services.</li><li>Empowering customers and employees through digital workflows that were not available before</li></ul><h3>Identifying Target Audiences</h3><p>It doesn’t matter if this is a public, a partner, or an internal API. It is important to be able to identify who the target audiences and users of your API program are going to be. In fact, according to a recent developer survey, <a href="https://www.devopsdigest.com/api-adoption-on-the-rise-across-all-industries">75% of developers reported working on internal APIs</a>.</p><p>The target audience for a particular API program might be employees but it is important to remember that they are still your end-users and ultimately, the success or failure of your API program is going to have a lot to do with them. Don’t take for granted that employees are going to love your internal API just because they work for your organization. Make the <a href="https://blog.softwareag.com/api-developer-portal">API developer experience a priority</a> with a great developer portal and documentation.</p><p>Once you have identified your target audience, work with small groups of early adopters across your community. Find your API champions and leverage their desire and passion to use your APIs and adopt the API program to your advantage. Get feedback early and often throughout the program on many areas including:</p><ul><li>The design and user experience</li><li>The terminology used in the APIs and documentation</li><li>Opportunities for improvement</li></ul><p>Listen and be responsive to the concerns of your user base and let them know they have a voice. This will do wonders for the future adoption of your API Program and give the users a sense of ownership that you can leverage to organically grow your program.</p><h3>Managing your APIs as Products</h3><p>If your API is a product:</p><ul><li>It will be designed with the customer in mind</li><li>It will be marketed to target customers</li><li>It will have a great user experience</li><li>You will make sure it works to build trust</li><li>It will have a great support community</li></ul><h3>Aligning Organization around Digital Strategy and Experience</h3><p>As mentioned earlier, the participation and support of Executives can make a dramatic difference in the success of any Digital Strategy. There are often many adjustments that will need to be made to teams, resources, products, and marketing, to align around changes to the entire digital experience and an API-centric product focus. Executive stakeholders must be actively supportive of the teams the necessary financial and resource investments for the duration of the journey.</p><p>Some of the things that can be done to make the adoption of an API Program smoother are to:</p><ul><li>Clearly articulate the vision and across organization</li><li>Be transparent with any necessary changes that are planned</li><li>Focus on organizational value gained by a successfully implemented program</li><li>Make sure everyone understands the value that they bring to the program</li><li>Encourage innovation and capture new ideas that can benefit adoption</li></ul><p>It will probably be necessary to organizationally align teams by service. Some of the new roles you might see in the organization include</p><ul><li>API Product Manager</li><li>API Developers/Architects</li><li>API Security Specialists</li></ul><h3>Securing your APIs</h3><p>The importance of <a href="https://blog.softwareag.com/api-security-explained">API Security and Cybersecurity</a> goes far beyond your APIs themselves. As your API program grows, you will want to be sure that you have a comprehensive security strategy in place. Your cybersecurity strategy should not be static but will live and grow with your organization, your APIs, and your digital strategy.</p><p>API Security starts with your API Gateway, making sure that it is properly configured and that you are taking advantage of all the security features in the product. You will also want to make sure your API Gateway can easily integrate with any other security products and applications you have in place with your API Management system.</p><p>Treat every API like it is a public API. Even if there are no plans to make it a public API, the security measures that you put in place need to be solid and secure in order to protect your applications and APIs. This will help to build trust with your employees and end-users while providing security and privacy for them AND their data.</p><h3>About Brenton House</h3><p><a href="https://blog.softwareag.com/author/brenton-house">Brenton House is Vice President of Digital Evangelism at Software AG.</a> As an API and Digital Transformation Evangelist and Strategist, he has connected enterprises with API solutions and microservices, to help drive innovation and overall business growth for many organizations.</p><p>In his 25+ years of experience, he has worked across many industries including broadcasting, advertising, retail, financial services, supply chain, transportation, technology, and publishing — gaining a breadth of knowledge on all things APIs and Integrations. His diverse experience set and unique creative skill sets have enabled him to equip organizations in creating captivating and innovative products that delight users.</p><p><a href="https://linkedin.com/in/brentonhouse">👉 Connect with Brenton House on LinkedIn! 👈</a></p><h3>Check out some of our other resources to continue learning more about APIs and Integrations!</h3><p>⭐ Software AG Blog ▪ <a href="https://blog.softwareag.com/">https://blog.softwareag.com</a><br>⭐ API Knowledge Portal ▪ <a href="https://knowledge.softwareag.com/">https://knowledge.softwareag.com</a><br>⭐ Software AG Tech Community ▪ <a href="https://techcommunity.softwareag.com/">https://techcommunity.softwareag.com/</a><br>🎬 Software AG YouTube Channel ▪ <a href="https://youtube.com/softwareag">https://youtube.com/softwareag</a><br>🎬 Brenton House’s YouTube Channel ▪ <a href="https://youtube.com/brentonhouse">https://youtube.com/brentonhouse</a><br>🎬 API Shorts YouTube Channel ▪ <a href="https://youtube.com/apishorts">https://youtube.com/apishorts</a></p><p>👇👇👇 FREE online API Maturity assessment here! 👇👇👇</p><blockquote><a href="https://www.softwareag.com/api-maturity"><em>https://www.softwareag.com/api-maturity</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7544fb11f00c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brentonhouse/api-first-strategy-7544fb11f00c">API First Strategy Explained</a> was originally published in <a href="https://medium.com/brentonhouse">Brenton House — Digital Strategist and Influencer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 10 API Integration Trends for 2022]]></title>
            <link>https://medium.com/brentonhouse/top-10-api-integration-trends-for-2022-49b05f2ef299?source=rss-1bbcfdf4e397------2</link>
            <guid isPermaLink="false">https://medium.com/p/49b05f2ef299</guid>
            <category><![CDATA[api-management]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[api-development]]></category>
            <category><![CDATA[api-integration]]></category>
            <category><![CDATA[trends]]></category>
            <dc:creator><![CDATA[Brenton House ️‍♂️]]></dc:creator>
            <pubDate>Thu, 09 Dec 2021 19:51:49 GMT</pubDate>
            <atom:updated>2022-01-19T12:23:31.469Z</atom:updated>
            <content:encoded><![CDATA[<p>APIs are driving everything in 2022. Software AG’s Senior API Strategist, Brenton House, reveals the API Integration trends for 2022 and walks you through why these are important and how you can leverage these to ensure the success of the API portfolio at your organization.</p><p>Use these as a guide to see how Digital Transformation is driving your organization forward and what you need to do to ensure you are not left behind.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZY7JSZIZgXU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZY7JSZIZgXU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZY7JSZIZgXU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/595bbb435536e8ad32a077a848835090/href">https://medium.com/media/595bbb435536e8ad32a077a848835090/href</a></iframe><h3>So where are API Integration trends heading in 2022?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b62968WVBox6C_6KibAxIQ.png" /><figcaption>2022 API Integration Trends — API Economy Growth</figcaption></figure><h3>API Economy Growth</h3><blockquote><strong>At number 10, we have API Economy Growth.</strong></blockquote><p>The API Economy is taking the world by storm. When talking about the API Economy, we are not just referencing your ability to sell access to your APIs and data.</p><p>No, it’s much more than this. It’s about:</p><ul><li>Revolutionizing how enterprises are organizing their teams, resources, and budgets.</li><li>The entire supply chain being powered by APIs</li><li>Ordering dinner and having it delivered to your home.</li><li>Providing a way to request an Uber ride and track it from beginning to end</li><li>Streaming movies and television shows to televisions, computers, and mobile phones around the world</li><li>Ordering fresh groceries and having them delivered from store to front porch</li></ul><p>APIs on their own are not enough to drive this digital ecosystem. APIs are simply the enablers for and the gateway to the digital and physical products that you are already creating or plan on creating. APIs are what enable businesses to engage with consumers in the digital world. APIs are how your products are going to be viewed, purchased, consumed, and judged in this digital economy.</p><p>In order to compete in this very competitive API market, companies are adopting API First strategies. They are realizing that their APIs are a Product, and not an add-on to their existing products. These decisions to put budget and resources behind their API teams will allow them to succeed and win in 2022.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3QDvT2Yspsms4M6TdowXYg.png" /><figcaption>2022 API Integration Trends — API-Led Modernization</figcaption></figure><h3>API-Led Modernization</h3><blockquote><strong>At number 9 we have Modernization. Specifically, how APIs are powering the modernization of businesses across all verticals.</strong></blockquote><p>Mainframe and legacy systems can be a big dependency (and liability) for many organizations. We are seeing an increase in the number of companies that are using APIs and API Platforms to replace and extend the capabilities of their legacy systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h1Oh4nMYhZ_mbgD6IamGLg.png" /><figcaption>2022 API Integration Trends — API and Integration Experience</figcaption></figure><h3>API and Integration Experience</h3><blockquote><strong>Coming in at number 8, we have the API and Integration Experience.</strong></blockquote><p>Everyone wants the experience with their API products to be magical. From APIs, API Documentation, API Developer Portals, and API Artifacts, a lot can be said about the user and developer experience across the entire API landscape.</p><p>The reason API Experience is on the Top 10 list is that along with the huge growth of APIs in the past few years, there has been a corresponding growth in expectations that users and developers have when they go to consume or integrate with an API product.</p><p>API Products and Portfolios need to include things like:</p><ul><li>Being intuitive (a must-have!)</li><li>Well-documented APIs</li><li>Self-Service Developer Portal</li><li>Having a great onboarding experience (zero to API in 5 minutes)</li><li>Consistent and useful error messaging</li><li>Keep it simple (it has one job)</li><li>Don’t be ugly (great UX and aesthetics)</li><li>Providing great logging and analytics</li><li>Including code samples and Postman scripts</li><li>Free-forever developer tier</li></ul><p>A great developer and user experience for your APIs and integrations can give you an edge up over your competition and make a world of difference as to whether your digital and non-digital products are successful in this competitive market.</p><p><a href="https://blog.softwareag.com/api-developer-portal">You can read more about creating a great API and integration experience here.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K21UNYKK3nF8pVmghu21gQ.png" /><figcaption>2022 API Integration Trends — Open API Standards</figcaption></figure><h3>Open API Standards</h3><blockquote><strong>At number 7 we have Open Standards for APIs and Integrations. In the past few years, we have seen everything opening up and an increase in the adoption of open standards.</strong></blockquote><p>With the advancement of tools, technology, code, and no-code solutions, it’s actually not that difficult to build an API these days. However, building APIs that are extensible, scalable, actually use best practices, and properly implement open standards can be a much more difficult feat.</p><p>RESTful APIs and open standards such as SOAP, Swagger, OpenAPI, JSON Schema, AsyncAPI, and GraphQL have been around for a while but we are seeing substantial growth in the community around the development of these standards and the participation from businesses and individuals in keeping these standards up-to-date with new features and improved documentation.</p><p>My recommendation would be to get involved with the groups that support these standards and participate in the process of growing the API community. If you are consuming and using these standards, (and I am sure you are), keep up-to-date with the changes to ensure you are producing and integrating with APIs in the best possible (and securest) way.</p><p>Take a look at some of the Open Standard communities that have been growing in the past year:</p><ul><li><a href="https://swagger.io/specification/">OpenAPI Specification (v3.0.3)</a></li><li><a href="https://spec.graphql.org/October2021/">GraphQL Specification(October 2021 edition)</a></li><li><a href="https://json-schema.org/specification.html">JSON Schema Specification (2020–12)</a></li><li><a href="https://www.asyncapi.com/docs/specifications/v2.2.0">AsyncAPI Specification (v2.2.0)</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q7Qw9DKgZiE6XpgB33rWcg.png" /><figcaption>2022 API Integration Trends — API Best Practices</figcaption></figure><h3>API Best Practices</h3><blockquote><strong>Closely related to Open API Standards, we have API Best Practices coming in at number 6.</strong></blockquote><p>While there have always been Best Practices of some sort around the use of APIs, Integrations, and Microservices, it has been kind of hit-and-miss with what you could find and where you might find it. Often best practices might have conflicting messages or be so vague as to lead to branches of differing micro best practices.</p><p>Although RESTful APIs are solidifying their position as the current standard for APIs, we are also seeing an increase in the use of GraphQL, gRPC, and others. This has driven an increased need for formalized Best Practices around, not only covering what technology and standards to use, but how to do it in the best possible way so as to reduce the amount of future rework involved.</p><p>Best Practices include many API topics including (but not limited to):</p><ul><li><a href="https://blog.softwareag.com/api-developer-portal">API Design</a></li><li><a href="https://blog.softwareag.com/api-security-explained">API Security</a></li><li><a href="https://www.softwareag.com/en_corporate/platform/integration-apis.html">API Integrations</a></li><li>API Transformations</li><li>Logging and Tracing</li><li>Code and Design Linting</li><li>Error Handling</li><li>Monetization</li><li>Onboarding</li><li>Versioning</li><li>Observation</li><li>Analytics</li><li>Documentation</li><li>Testing / Audits</li><li>Pagination / Bulk Data Handling</li><li>Eventing — WebHooks / Polling / Web Sockets</li><li>Scalability</li><li>And many more!</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*856UvTuqiPkiYLSl-QZ2UQ.png" /><figcaption>2022 API Integration Trends — Industry Specific Breakouts</figcaption></figure><h3>Industry-Specific Breakouts</h3><blockquote><strong>At number 5 we are seeing an increase in the push for industry vertical-specific ecosystems around APIs and integrations</strong>.</blockquote><p>Take <a href="https://blog.softwareag.com/open-banking-apis">Open Banking</a> as an easy example of this. If you are in the financial industry (especially if you are in a geographical region that has government regulations around this), you have been aware of the changes both in standards and government regulations that have shaped how financial and banking APIs integrate with one another.</p><p>The healthcare industry is also seeing similar growth with the development and implementation of <a href="https://fhir.org/">FHIR (Fast Healthcare Interoperability Resources)</a> and other healthcare standards.</p><p>Expect to see a continuation of growth in some of these existing verticals as well as spikes and new growth in other industries.</p><p>Keep a watchful eye on Government, Manufacturing, Transportation/Logistics, Retail, Insurance, Supply chain, Telecom, and some others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MVNP3Z5IFeWT65rme30ibw.png" /><figcaption>2022 API Integration Trends — API and Integration Automation</figcaption></figure><h3>API and Integration Automation</h3><blockquote><strong>At number 4 we have API Automation</strong></blockquote><p>I am a huge fan of automation and am actually excited to see the increase in API Automation adoption.</p><p>This goes beyond some of the automation that we have seen in previous years:</p><ul><li>Automated API integration tests</li><li>Automated code unit tests</li><li>Automated publishing</li><li>Automated security checks.</li></ul><p>GitHub has recently announced a new development tool called <a href="https://copilot.github.com/">GitHub CoPilot</a>. GitHub Copilot is an artificial intelligence tool developed by GitHub and OpenAI to assist users by auto-completing code. Now there has been a lot of feedback on this (both good and bad) but the point is things are changing. The goal of automation is not to replace workers but to allow workers to focus on more important tasks.</p><p>Keep an eye out for an increase in:</p><ul><li>Automation for API design with various no-code solutions</li><li>Automation with API Integrations</li><li>Automation in API creation</li><li>Automation for API Management and Governance</li><li>Advancements in automation for API Security</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GRhtOI-ZKRbbJaPJuXA8xw.png" /><figcaption>2022 API Integration Trends — Adaptive API Management</figcaption></figure><h3>Adaptive API Management</h3><blockquote><strong>At number 3 we have Adaptive API Management</strong></blockquote><p>Managing the entire API Lifecycle can be challenging. Every organization is different and often the needs and requirements can be quite complex. Enterprises need to adapt quickly to changes in the market, changes in government regulations, changes in technology, and even changes in how (and where) people work.</p><p>New APIs are created every day and people need API Management that can adapt as well. Whether you are adapting to new API policy requirements, new API security threats, new API integration requirements, or new API consumer or partner opportunities, the need for an Adaptive API Management system is growing every day.</p><p>Because of issues like these, 2022 will see the continued growth of Adaptive API Management systems like webMethods which provides a robust and holistic approach to API Management. Some organizations need on-prem solutions. Others want to use cloud-based SaaS solutions. But a growing number will need something in-between with a mix of both.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zIRsZL65313KBWM4lcvevQ.png" /><figcaption>2022 API Integration Trends — Adaptive API Management</figcaption></figure><h3>Seamless Integration Solutions</h3><blockquote><strong>At number 2 we have Seamless Integrations</strong></blockquote><p>An API without any integrations is like a car without fuel or power. It’s may look pretty but it is not very functional.</p><p>Not only do APIs need to accept integrations and integrate with other APIs but there can also be complex requirements for chaining and transforming the incoming and outgoing data across these integrations.</p><p>APIs need to be able to easily integrate with anything, anywhere. 2022 will see the need for seamless API integrations that grow and scale even further with solid and proven integration tools standing out from the crowd because of their smooth and seamless handling of integration processes, both on-premise and in the cloud. Because of this increased demand for secure integrations with other APIs and systems, organizations want and need products that can remove the friction from their integration experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V5qK5CQxiEHg1HqqEiNEDw.png" /><figcaption>2022 API Integration Trends — API Security and Cybersecurity</figcaption></figure><h3>API Cybersecurity</h3><blockquote><strong>At number 1 we have API Security and Cybersecurity</strong></blockquote><p>As long as there have been APIs, there have been hackers who are searching for vulnerabilities in those APIs. API Security and Cybersecurity is of critical importance for EVERY organization. Especially now. NOBODY wants to be in the headlines for all the wrong reasons.</p><p>Earlier, Gartner had predicted that by 2022, API abuses will move from infrequent to the most-frequent attack vector. The growth in not only the number of APIs but the exponential increase in API usage has made this prediction all the more impactful on businesses around the world.</p><p>According to a more recent Gartner CIO and Technical Executive survey, cyber and information security are at the top of the list for planned investments in 2022. This is not surprising as business leaders are feeling the pressure to put budget and resources behind cybersecurity to protect their APIs, data, customers, and the reputation of their companies.</p><p>You may have heard the phrase “<strong>Shift Left, Shield Right</strong>”.</p><p><strong>“Shift Left</strong>&quot; is referring to is shifting your security focus to the beginning of the API Lifecycle process and to integrate it into the design, development, and every other step of the API Lifecycle all the way to the retirement of an API.</p><p><strong>“Shield Right</strong>&quot; is talking about the emphasis on continuing to protect your APIs at runtime and beyond. Doing this will allow you to provide a defense against unknown attacks.</p><p>Closely related to API Cybersecurity is the topic of encryption and privacy. Because of the close relation to security, they are included in this topic. Organizations are increasing their understanding and proper implementation of encryption to protect their data. Everything from storage and transmission of data requires a critical security eye when planning and implementing DevOps security. Privacy is also directly related to this as API Cybersecurity is an essential key to securing the privacy of users and employees. Not only does data need to be secured but sometimes the best decision is not to store the data at all. There are a lot of government regulations surrounding privacy in certain parts of the world but security and privacy requirements can also drive a strategy that reduces unnecessary data to protect both consumers and enterprises alike.</p><p>API Cybersecurity as it is important for everyone to understand API Cybersecurity, what is at risk, and how to protect and defend your APIs and other systems from attacks.</p><p><a href="https://www.youtube.com/watch?v=6LP_3FZDiPU&amp;list=PLKUnjn-fSXRTy8sPPXGrNNBDPVOOi3U49">Check out this series of short videos to learn more about API Cybersecurity.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e1IkM-9ilCrDt_JA0HRThA.png" /><figcaption>API Trends 2022 — Composable APIs — Brenton House</figcaption></figure><h3>Composable APIs</h3><blockquote><strong>As a bonus item for the list, keep a close watch on composable APIs.</strong></blockquote><p>While composable architecture has been around for a while, the term is getting some extra attention lately and you will start to see more enterprises that may forego building part or all of an API and instead compose new APIs together from existing APIs (both internal and external) that will integrate with other APIs to add features instead of internally building new APIs or using existing SaaS services.</p><p>Composable APIs have the potential to give organizations the opportunity to reap the benefits from both the flexibility of a custom-built API and the seamlessness of a SaaS API subscription or service. Consumable APIs are heavily powered by the no-code SaaS and on-premise API integration solutions that exist today, such as Software AG’s webMethods.io.</p><h3>About Brenton House</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uoa-deh2aNP63phOmVmlsA.png" /><figcaption>Brenton House — Digital Strategist</figcaption></figure><p><a href="https://blog.softwareag.com/author/brenton-house">Brenton House is Vice President of Digital Evangelism at Software AG</a>. As an API and Digital Transformation Evangelist and Strategist, he has connected enterprises with API solutions and microservices, to help drive innovation and overall business growth for many organizations.</p><p>In his 25+ years of experience, he has worked across many industries including broadcasting, advertising, retail, financial services, supply chain, transportation, technology, and publishing — gaining a breadth of knowledge on all things APIs and Integrations. His diverse experience set and unique creative skill sets have enabled him to equip organizations in creating captivating and innovative products that delight users.</p><h4><a href="https://linkedin.com/in/brentonhouse"><em>Connect with Brenton House on LinkedIn!</em></a></h4><h3>Check out some of our other resources to continue learning more about APIs and Integrations!</h3><p>⭐ Software AG Blog ▪ <a href="https://blog.softwareag.com/">https://blog.softwareag.com</a><br>⭐ API Knowledge Portal ▪ <a href="https://knowledge.softwareag.com/">https://knowledge.softwareag.com</a><br>⭐ Software AG Tech Community ▪ <a href="https://techcommunity.softwareag.com/">https://techcommunity.softwareag.com/</a><br>🎬 Software AG YouTube Channel ▪ <a href="https://youtube.com/softwareag">https://youtube.com/softwareag</a><br>🎬 Brenton House’s YouTube Channel ▪ <a href="https://youtube.com/brentonhouse">https://youtube.com/brentonhouse</a><br>🎬 API Shorts YouTube Channel ▪ <a href="https://youtube.com/apishorts">https://youtube.com/apishorts</a></p><h4>👇👇👇 FREE online API Maturity assessment here! 👇👇👇</h4><blockquote><a href="https://www.softwareag.com/api-maturity"><em>https://www.softwareag.com/api-maturity</em></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mQzecLZ1FrkW_ZUV44Y7lg.png" /><figcaption>Top 10 API Integration Trends for 2022 with Brenton House</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49b05f2ef299" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brentonhouse/top-10-api-integration-trends-for-2022-49b05f2ef299">Top 10 API Integration Trends for 2022</a> was originally published in <a href="https://medium.com/brentonhouse">Brenton House — Digital Strategist and Influencer</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 a Zombie API? — API Cybersecurity 101 with Brenton House]]></title>
            <link>https://medium.com/brentonhouse/what-is-a-zombie-api-6e5427c39b6a?source=rss-1bbcfdf4e397------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e5427c39b6a</guid>
            <dc:creator><![CDATA[Brenton House ️‍♂️]]></dc:creator>
            <pubDate>Mon, 01 Nov 2021 01:51:15 GMT</pubDate>
            <atom:updated>2021-12-29T16:53:48.561Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a Zombie API? <em>— API Cybersecurity 101 with Brenton House</em></h3><p>Don’t let an API bring on the Zombie Apocalypse! Keep your APIs up-to-date with the latest API Security Best Practices!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*dCXkJwqHwYUHYKmA.png" /></figure><blockquote><em>This is part of the </em><a href="https://www.youtube.com/watch?v=6LP_3FZDiPU&amp;list=PLKUnjn-fSXRTy8sPPXGrNNBDPVOOi3U49"><em>API Cybersecurity 101 series by Software AG’s Senior API Strategist, Brenton House</em></a><em>. A continuing series on API Security and Cybersecurity.</em></blockquote><p><em>Have you ever come across an older API at your organization that was built by another team or possibly a contractor that no longer works with your company.</em></p><p>The API works fine and no major bugs and no complaints from the users of the API.</p><p>You may be thinking:</p><p><strong>&quot;If it ain&#39;t broke. Don&#39;t fix it&quot;</strong></p><p><strong>THIS…</strong> is a Zombie API.</p><p>Before we get into the details of a Zombie API, let’s back up a bit and define some terms:</p><h4>What is an API?</h4><p>The acronym API stands for Application Programming Interface. Basically, it is non-human systems (or applications) that talk to each other in an agreed-upon way! Most often, people are talking about Web APIs, which include things like REST, GraphQL, gRPC, SOAP, etc. The introduction of smartphones caused an exponential growth and adoption of APIs as pretty much every single mobile application uses APIs.</p><h4>What is API Security?</h4><p>The simple answer is that it is about applying and managing security for your APIs but we all know, there is <a href="https://brenton.house/what-is-api-security-5ca8117d4911">nothing simple about API Security</a>.</p><h4>There are 7 basic categories for APIs.</h4><ul><li>Public APIs</li><li>Internal APIs</li><li>Partner APIs</li><li>Composite APIs</li><li>Shadow APIs</li><li>Zombie APIs</li><li>Frankenstein APIs</li></ul><h3>So what is a Zombie API?</h3><p>A <strong>Zombie API</strong> is an API that never gets updated because, well, it just works.</p><p>The problem arises when the <strong>Zombie API</strong> suddenly exposes a security vulnerability at your organization because it doesn’t have the latest updates for libraries and SDKs where these vulnerabilities were patched.</p><p>Nobody wants to update <strong>Zombie APIs</strong>.</p><p>It is often categorized as &quot;Technical Debt&quot; because it requires work that the customer isn&#39;t directly asking for.</p><p><strong>Don’t be fooled.</strong></p><blockquote>Nobody wants the Zombie Apocalypse.</blockquote><p><strong>Not you,<br>Not your customers,<br>Nobody.</strong></p><p>Keep your APIs up-to-date…<br>or shut them down!</p><p>Stay prepared and you just might survive the Zombie Apocalypse! 🧟</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*RgxtTCXC6ADdOU7y.png" /></figure><h3>About Brenton House</h3><p><a href="https://blog.softwareag.com/author/brenton-house">Brenton House is Vice President of Digital Evangelism at Software AG.</a> As an API and Digital Transformation Evangelist and Strategist, he has connected enterprises with API solutions and microservices, to help drive innovation and overall business growth for many organizations.</p><p>In his 25+ years of experience, he has worked across many industries including broadcasting, advertising, retail, financial services, supply chain, transportation, technology, and publishing — gaining a breadth of knowledge on all things APIs and Integrations. His diverse experience set and unique creative skill sets have enabled him to equip organizations in creating captivating and innovative products that delight users.</p><p><a href="https://linkedin.com/in/brentonhouse">Connect with Brenton House on LinkedIn!</a></p><h3>Check out some of our other resources to continue learning more about APIs and Integrations!</h3><p>⭐ Software AG Blog ▪ <a href="https://blog.softwareag.com/">https://blog.softwareag.com</a></p><p>⭐ API Knowledge Portal ▪ <a href="https://knowledge.softwareag.com/">https://knowledge.softwareag.com</a></p><p>⭐ Software AG Tech Community ▪ <a href="https://techcommunity.softwareag.com/">https://techcommunity.softwareag.com/</a></p><p>🎬 Software AG YouTube Channel ▪ <a href="https://youtube.com/softwareag">https://youtube.com/softwareag</a></p><p>🎬 Brenton House’s YouTube Channel ▪ <a href="https://youtube.com/brentonhouse">https://youtube.com/brentonhouse</a></p><p>🎬 API Shorts YouTube Channel ▪ <a href="https://youtube.com/apishorts">https://youtube.com/apishorts</a></p><p>👇👇👇 FREE online API Maturity assessment here! 👇👇👇</p><blockquote><a href="https://www.softwareag.com/api-maturity"><strong><em>https://www.softwareag.com/api-maturity</em></strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e5427c39b6a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brentonhouse/what-is-a-zombie-api-6e5427c39b6a">What is a Zombie API? — API Cybersecurity 101 with Brenton House</a> was originally published in <a href="https://medium.com/brentonhouse">Brenton House — Digital Strategist and Influencer</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 a Frankenstein API? — API Cybersecurity 101 with Brenton House]]></title>
            <link>https://medium.com/brentonhouse/what-is-a-frankenstein-api-4d6e59fca6?source=rss-1bbcfdf4e397------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d6e59fca6</guid>
            <dc:creator><![CDATA[Brenton House ️‍♂️]]></dc:creator>
            <pubDate>Mon, 01 Nov 2021 01:50:50 GMT</pubDate>
            <atom:updated>2021-11-04T23:35:46.750Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a Frankenstein API?</h3><p>Unknown APIs can be scary but not every API is a monster</p><p>You may have never heard of a <strong>Frankenstein API</strong>. But there is a good chance you have used one at some point. It is important to know what a Frankenstein API is because your <a href="https://brenton.house/what-is-api-security-5ca8117d4911">API Security</a> could depend on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y9ApA8BzYcINq81iSOty0A.png" /><figcaption>What is a Frankenstein API? API Cybersecurity 101 with Brenton House</figcaption></figure><blockquote><strong><em>This is part of the </em></strong><a href="https://www.youtube.com/watch?v=6LP_3FZDiPU&amp;list=PLKUnjn-fSXRTy8sPPXGrNNBDPVOOi3U49"><strong><em>API Cybersecurity 101 series by Senior API Strategist, Brenton House</em></strong></a><strong><em>. A continuing series on API Security and Cybersecurity.</em></strong></blockquote><p>A <strong>Frankenstein API</strong> is one that is created in the deepest depths of a dark and secret laboratory.</p><h4>No. Not really.</h4><p>But this type of API is usually creatively pieced together using unorthodox methods and is driven by a strong need for functionality.</p><h4>So let’s start with the basics.</h4><h3>What is an API?</h3><p>The acronym API stands for Application Programming Interface. Basically, it is non-human systems (or applications) that talk to each other in an agreed-upon way! Most often, people are talking about Web APIs, which includes things like REST, GraphQL, gRPC, SOAP, etc. The introduction of smartphones caused an exponential growth and adoption of APIs as pretty much every single mobile application uses APIs.</p><h3>What is API Security?</h3><p>The simple answer is that it is about applying and managing security for your APIs but we all know, there is <a href="https://brenton.house/what-is-api-security-5ca8117d4911">nothing simple about API Security</a>.</p><p>Read our latest article that explains <a href="https://brenton.house/what-is-api-security-5ca8117d4911"><strong>What is API Security as part of our API Cybersecurity 101 series.</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1yddEFe27pSOuh9UfQWVg.png" /><figcaption>What is API Security? API Cybersecurity 101 with Brenton House</figcaption></figure><h4>There are 7 basic categories for APIs.</h4><ul><li>Public APIs</li><li>Internal APIs</li><li>Partner APIs</li><li>Composite APIs</li><li>Shadow APIs</li><li>Zombie APIs</li><li>Frankenstein APIs</li></ul><blockquote><strong><em>So what is a Frankenstein API?</em></strong></blockquote><p>What happens when you really need an API for something and that API does not exist?</p><p>Take for instance Google Public Search Results (SERP) API. Have you ever used it?</p><blockquote>Me neither. It doesn’t exist.</blockquote><p>That doesn’t mean that people don’t need APIs like this though. You may have used services that provide APIs to show you how your website (and the websites of others) rank for certain keywords and queries.</p><p>Another example might be where a web application product has an API but it is very limited and doesn’t provide access to all the information and functionality that the corresponding web application does.</p><p>This is another example where someone might end up building an API.</p><p>Now when I say building, I really mean piecing/hacking/cobbling it together using unorthodox and unconventional methods such as screen scraping and other techniques. When done right, these can provide the valuable data that wasn’t provided by the original product but it comes with many risks…</p><p>Some of the risks to be concerned about stem from the fact that this API was not created by the same organization that created the original product.</p><h3>Frankenstein APIs can be extremely fragile</h3><p>A <strong>Frankenstein API</strong> does not have the insider information needed to make the API stable and durable. For instance, if (sorry, WHEN, not if) Google were to change how search engine results were laid out or presented, then every <strong>Frankenstein API </strong>that was created by scraping the Google Search Engine Results Pages (SERP) would most likely break (depending on the how major the changes were).</p><h3>Frankenstein APIs can bypass product security</h3><p>If a <a href="https://brenton.house/what-is-a-frankenstein-api-4d6e59fca6"><strong>Frankenstein API</strong></a><strong> </strong>was created to fill the gap created by missing features in the original product, it is very possible that the mechanism for scraping the data and compiling it into an API would be bypassing security. What I mean by that is the resulting<strong> Frankenstein API </strong>would not require the same security that the scraping tool (or another mechanism) was required to provide in order to retrieve the data from the original application.</p><h3>Frankenstein APIs can cause undue load on resources</h3><p>There is no guarantee on the experience level of the developer (or developers) that creates a<strong> Frankenstein API</strong>. Since they are not part of the organization that created the original application, the techniques used to “retrieve” the data may be, well… less than optimized. The code in a Frankenstein API could be eating up all kinds of resources owned by the original application owner. Calls could be taxing servers, bandwidth, and other resources that all result in lots of money.</p><h3>Frankenstein APIs could expose vulnerabilities</h3><p>This one is not strictly limited to <strong>Frankenstein APIs</strong> but you could be asking for problems. Once you have an external developer or hacker digging through your applications looking for a way to capture the data they need, they could discover vulnerabilities in your system that would not have been found otherwise. Vulnerabilities can be found by hackers not creating <strong>Frankenstein APIs b</strong>ut it would be wise to not create more opportunities.</p><h3>API First to the rescue</h3><p>A solid API First strategy can be helpful in avoiding some of the problems that arise due to <strong>Frankenstein APIs</strong>. If your organization treats APIs like a Product and always creates an API First, BEFORE creating an application, you can <a href="https://brenton.house/what-is-api-security-5ca8117d4911">engineer security into a proper API</a>, thus alleviating the need for a <strong>Frankenstein API</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/567/1*z6luQquzEfdwJEoRb2m-Wg.jpeg" /><figcaption>What is a Frankenstein API? — NO API FOR YOU!</figcaption></figure><h3>NO API FOR YOU!!</h3><p>If you absolutely insist on not providing an API for the users of your applications, you will need to take precautions. By the way, <strong>I DO NOT recommend this option!</strong></p><p>You will need to have very advanced mechanisms in place to protect your web applications (and other sources of data) from screen scraping and other data retrieval mechanisms. This can be tough to do and you will have to be constantly changing it in order to keep of with the latest data retrieval techniques.</p><p>This is not to say that you don’t need to protect against screen scraping if also provide an API but it may remove a lot of the motivation for creating a <strong>Frankenstein API </strong>if you provide a proper API along with your application.</p><p>I am not saying <strong>Frankenstein APIs</strong> are bad, more misunderstood.</p><p>My point is for you to be aware that they exist and to treat them with care, especially in terms of API Security.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-MlDgkJg9xU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-MlDgkJg9xU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-MlDgkJg9xU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7935029b4e2d0e25d991dac0f2bd975f/href">https://medium.com/media/7935029b4e2d0e25d991dac0f2bd975f/href</a></iframe><h3>About Brenton House</h3><p><a href="https://blog.softwareag.com/author/brenton-house">Brenton House is Vice President of Digital Evangelism at Software AG</a>. As an API and Digital Transformation Evangelist and Strategist, he has connected enterprises with API solutions and microservices, to help drive innovation and overall business growth for many organizations.</p><p>In his 25+ years of experience, he has worked across many industries including broadcasting, advertising, retail, financial services, supply chain, transportation, technology, and publishing — gaining a breadth of knowledge on all things APIs and Integrations. His diverse experience set and unique creative skill sets have enabled him to equip organizations in creating captivating and innovative products that delight users.</p><blockquote><a href="https://linkedin.com/in/brentonhouse">Connect with Brenton House on LinkedIn!</a></blockquote><h3>Check out some of our other resources to continue learning more about APIs and Integrations!</h3><p>⭐ Software AG Blog ▪ <a href="https://blog.softwareag.com/">https://blog.softwareag.com</a><br>⭐ API Knowledge Portal ▪ <a href="https://knowledge.softwareag.com/">https://knowledge.softwareag.com</a><br>⭐ Software AG Tech Community ▪ <a href="https://techcommunity.softwareag.com/">https://techcommunity.softwareag.com/</a><br>🎬 Software AG YouTube Channel ▪ <a href="https://youtube.com/softwareag">https://youtube.com/softwareag</a><br>🎬 Brenton House’s YouTube Channel ▪ <a href="https://youtube.com/brentonhouse">https://youtube.com/brentonhouse</a><br>🎬 API Shorts YouTube Channel ▪ <a href="https://youtube.com/apishorts">https://youtube.com/apishorts</a></p><h4>👇👇👇 <strong>FREE online API Maturity assessment here!</strong> 👇👇👇</h4><blockquote><a href="https://www.softwareag.com/api-maturity"><em>https://www.softwareag.com/api-maturity</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d6e59fca6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brentonhouse/what-is-a-frankenstein-api-4d6e59fca6">What is a Frankenstein API? — API Cybersecurity 101 with Brenton House</a> was originally published in <a href="https://medium.com/brentonhouse">Brenton House — Digital Strategist and Influencer</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 API Security? API Cybersecurity Explained!]]></title>
            <link>https://medium.com/brentonhouse/what-is-api-security-5ca8117d4911?source=rss-1bbcfdf4e397------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ca8117d4911</guid>
            <dc:creator><![CDATA[Brenton House ️‍♂️]]></dc:creator>
            <pubDate>Mon, 01 Nov 2021 01:49:53 GMT</pubDate>
            <atom:updated>2022-01-24T18:45:16.000Z</atom:updated>
            <content:encoded><![CDATA[<h3>API Cyber Security Explained!</h3><p>Everything you need to know about API Security and Cybersecurity</p><p><em>So you think your APIs are secure?</em></p><p><strong>You might want to take another look at your security.</strong></p><p>APIs are everywhere and API Security is of the utmost importance for every organization. According to a recent Gartner CIO and Technical Executive survey, Cyber and Information security are at the top of the list for planned investments in 2022.</p><p>As someone who has spent my entire career in the world of APIs and Internet applications, I have seen first-hand the vulnerabilities that can exist with APIs.</p><blockquote><strong>This is part of the </strong><a href="https://www.youtube.com/watch?v=6LP_3FZDiPU&amp;list=PLKUnjn-fSXRTy8sPPXGrNNBDPVOOi3U49"><strong>API Cybersecurity 101 series by Senior API Strategist, Brenton House</strong></a><strong>.</strong></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6LP_3FZDiPU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D6LP_3FZDiPU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F6LP_3FZDiPU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/53862525df35958d963a85b8878c261e/href">https://medium.com/media/53862525df35958d963a85b8878c261e/href</a></iframe><p><strong><em>So let’s start with the basics.</em></strong></p><h3>What is an API?</h3><p>The acronym API stands for Application Programming Interface. Basically, it is non-human systems (or applications) that talk to each other in an agreed-upon way! Most often, people are talking about Web APIs, which includes things like REST, GraphQL, gRPC, SOAP, etc. The introduction of smartphones caused an exponential growth and adoption of APIs as pretty much every single mobile application uses APIs.</p><h3>What is API Security?</h3><p>The simple answer is that it is about applying and managing security for your APIs but we all know, there is nothing simple about API Cybersecurity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*PzDYbhF9elk5XhhR.jpg" /><figcaption>War Games Move — API Cybersecurity 101</figcaption></figure><p>In 1983, there was a movie called <a href="https://www.imdb.com/title/tt0086567/"><strong>War Games</strong></a> that was released to theaters. You may have never heard of the movie but it was about a boy, David, played by Matthew Broderick, who hacks into NORAD’s Military Computer System and accidentally ALMOST starts World War III. The movie got the attention of the most powerful man in the world, at that time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/0*ElddJK4yI_XBe6jw.jpeg" /><figcaption>President Ronald Reagan — API Cybersecurity 101</figcaption></figure><p>According to journalist Fred Kaplan, After seeing a special screening of the movie “War Games”, then-President Ronald Reagan asked the U.S. Military Joint Chief of Staff if something like this could really happen. He asked, “Could someone just break into our most sensitive computers?” A week later, the General response was:</p><blockquote>“The problem is much worse than you think.”</blockquote><p>From that moment on, U.S. Cybersecurity and Defense policy would never be the same.</p><p>Fast forward almost 40 years and everyone with a smartphone has a computer more powerful than any supercomputer that existed at that time. YouTube is now full of free videos and training on how to code and become a serious developer (or a hacker). What that means is that almost anyone, from anywhere, in any country, could be trying to get into your APIs and systems TODAY. Everyone needs to be educated and prepared to defend against API attacks; malicious or not.</p><p>What most don’t understand is that API security starts with <strong>humans, not computers.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/0*6_OoNlInRZdKonZz.jpg" /><figcaption>password on sticky note</figcaption></figure><p>If someone puts their password on a sticky note attached to their monitor, it doesn’t matter how many security checks you do, how much security code you have in place, or what different security products you have installed.</p><p>There are, however, a lot of things that you can do to protect yourself and minimize damage from this and other forms of social hacking. We will be covering this in upcoming articles of our API Cybersecurity series.</p><h3>OWASP Top 10 List for APIs</h3><p>One thing you might have heard of and need to pay attention to is OWASP.</p><p><a href="https://owasp.org/">OWASP</a> is the Open Web Application Security Project.</p><p>It’s an international non-profit organization dedicated to web application security.</p><p>What they are probably most well-known for is their re-occurring <a href="https://owasp.org/www-project-top-ten/">Top 10 list of Web Vulnerabilities</a>.</p><p>But in addition to their lists of web vulnerabilities, they also came out with a <a href="https://owasp.org/www-project-api-security/">Top 10 list for API</a>s. Now it is a few years old but all of these are still important factors to consider with your API Security.</p><p>The latest OWASP API Security Top 10 list includes:</p><ul><li>API1:2019 Broken Object Level Authorization</li><li>API2:2019 Broken User Authentication</li><li>API3:2019 Excessive Data Exposure</li><li>API4:2019 Lack of Resources &amp; Rate Limiting</li><li>API5:2019 Broken Function Level Authorization</li><li>API6:2019 Mass Assignment</li><li>API7:2019 Security Misconfiguration</li><li>API8:2019 Injection</li><li>API9:2019 Improper Assets Management</li><li>API10:2019 Insufficient Logging &amp; Monitoring</li></ul><p>Inside these topics, you are going to discover even more details that you need to be familiar with and understand.</p><ul><li>API Keys</li><li>API Logging</li><li>API Injections</li><li>API Hackers</li><li>Zero Trust APIs</li><li>Shadow APIs</li><li>API Access Control</li><li>API Security Testing</li><li>JWTs</li><li>OAuth and OpenID Connect</li><li>Identity and Access Management</li><li>Multi-Factor Authentication</li><li>API Observation</li><li>API Threat Detection</li><li>And more…</li></ul><p>I will be covering all of these items in the OWASP API Security Top 10 list in detail in upcoming episodes of API Cybersecurity 101.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*Y50WuBGcfjs0cwQg.png" /><figcaption>Best way to secure APIs with API Gateway</figcaption></figure><h3>API Gateway</h3><p>There are some key weapons that you can arm yourself to defend your systems from attacks by API Hackers and intruders. The core to your API cybersecurity strategy is going to be an API Gateway. An API Gateway can provide protection against a lot of things including Denial of Service attacks. They can also provide API Monitoring, Logging, and API Rate Limiting. They can restrict traffic based on IP addresses and other metadata, handle security token validation, and much more. The API Gateway makes it easy to create, maintain, monitor, and secure your APIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*RvJnUy9d9XCVA2lp.png" /><figcaption>Web Application Firewall (WAF) for API Cyber Security</figcaption></figure><h3>Web Application Firewalls (WAF)</h3><p>The Web Application Firewalls (or WAF) stands between the public traffic and your API Gateway or application. A WAF can give you some additional protection against things like bots by using security rules, machine learning, and sometimes, artificial intelligence. They can provide malicious bot detection, identify attack signatures, provide additional IP Intelligence. A WAF can block bad traffic before it even reaches your Gateway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*EYzJLvmN76V85IoM.png" /><figcaption>Best API Security Apps for APIs</figcaption></figure><h3>Standalone Security Products</h3><p>Then there are also stand-alone security products. These products support features that can be broken down into categories such as real-time protection, static code and vulnerability scanning, build-time checking, and security fuzzing.</p><p>Many of the security products in the market will support features in some or all of these categories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*pAp_-LynIVKWdtaB.png" /><figcaption>API Cybersecurity in JavaScript code Java .NET Go</figcaption></figure><h3>Security in Code</h3><p>Last, we have security that is implemented internally to the API or applications themselves. I am not going to go into this very much on this article but I will simply point out the resources required to ensure that all the security is properly implemented in your API code can be difficult to apply consistently across your entire API Portfolio.</p><h3>Cybersecurity Precautions</h3><p>With any security feature or product, it is important to remember that security is a moving target. You want to know that the product (or products) that you use will stay up-to-date in protecting you against the latest vulnerabilities.</p><p>But doesn’t an API Gateway implement “Security as a Feature”? Yes. And it is a critical part of your API Management security strategy. API Gateways integrate with and work well with standalone API security products and Web Application Firewalls to provide solid and comprehensive protection for your APIs. Leaving out the core part of your security strategy, such as an API Gateway, a component that probably knows more about your APIs and the context of your traffic than any other system, is a really bad idea.</p><p>If your only focus is on using Web Application Firewalls or external security products and you ignore (or misconfigure) the protection provided by your API Gateway security, you could be leaving yourself wide-open for an attack.</p><p><strong>Don’t leave yourself vulnerable!</strong></p><h3>API Security Black Box?</h3><p>All of this only reinforces the fact that there is not a one-size-fits-all solution for API Cybersecurity. You can’t just buy an “API Cyber Security black box” from Best Buy, plug it in, and suddenly everything is protected.</p><p>To implement a proper security solution for APIs, it is important to understand your APIs, the 3rd-Party APIs you use, and the functionality and value your APIs are adding to your organization. This will help you better grasp how API Security ties into integrations with your partners and users. API Security is still one area that will require you to spend some time and resources to ensure it is implemented, (and CONTINUES to be implemented) correctly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qWJ_VuJbHAXOl3gZEk4y0Q.png" /><figcaption>API Security — 3rd Party Integrations</figcaption></figure><h3>Security for API Integrations</h3><p>When you are looking at your API ecosystem, don’t forget about API Integrations and the 3rd Party APIs that you will be integrating with. If these 3rd Party APIs or the integrations themselves are insecure, your data, internal systems, and APIs could be compromised. Using a solid API Integration solution (like <a href="https://www.softwareag.com/en_corporate/platform/integration-apis.html">Software AG’s webMethods.io</a>) with a proven track record can not only protect your API Integrations but work seamlessly with your API Gateway platform.</p><h3>API Cybersecurity 101</h3><p>To better equip organizations and individuals better protect themselves and their APIs, We’ve created a new series called API Cybersecurity 101. The purpose of this series of videos and blog posts is to educate and equip everyone from developers to executives with the resources you need to shield and protect your APIs. You can check out our API Cybersecurity video series on YouTube on the API Shorts channel: <a href="https://youtube.com/apishorts">https://youtube.com/apishorts</a></p><h3>About Brenton House</h3><p>Brenton House is Vice President of Digital Evangelism at Software AG. As an API and Digital Transformation Evangelist and Strategist, he has connected enterprises with API solutions and microservices, to help drive innovation and overall business growth for many organizations.</p><p>In his 25+ years of experience, he has worked across many industries including broadcasting, advertising, retail, financial services, supply chain, transportation, technology, and publishing — gaining a breadth of knowledge on all things APIs and Integrations. His diverse experience set and unique creative skill sets have enabled him to equip organizations in creating captivating and innovative products that delight users.</p><h3>Check out some of our other resources to continue learning more about APIs and Integrations!</h3><p>⭐ Software AG Blog ▪ <a href="https://blog.softwareag.com/">https://blog.softwareag.com</a></p><p>⭐ API Knowledge Portal ▪ <a href="https://knowledge.softwareag.com/">https://knowledge.softwareag.com</a></p><p>⭐ Software AG Tech Community ▪ <a href="https://techcommunity.softwareag.com/">https://techcommunity.softwareag.com/</a></p><p>🎬 Software AG YouTube Channel ▪ <a href="https://youtube.com/softwareag">https://youtube.com/softwareag</a></p><p>🎬 Brenton House’s YouTube Channel ▪ <a href="https://youtube.com/brentonhouse">https://youtube.com/brentonhouse</a></p><p>🎬 API Shorts YouTube Channel ▪ <a href="https://youtube.com/apishorts">https://youtube.com/apishorts</a></p><p>👇👇👇 FREE online API Maturity assessment here! 👇👇👇</p><blockquote><a href="https://www.softwareag.com/api-maturity"><strong><em>https://www.softwareag.com/api-maturity</em></strong></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1yddEFe27pSOuh9UfQWVg.png" /><figcaption>What is API Security? API Cybersecurity 101 with Brenton House</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ca8117d4911" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brentonhouse/what-is-api-security-5ca8117d4911">What is API Security? API Cybersecurity Explained!</a> was originally published in <a href="https://medium.com/brentonhouse">Brenton House — Digital Strategist and Influencer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Keys to WINNING with an Awesome API Developer Experience!]]></title>
            <link>https://medium.com/brentonhouse/keys-to-winning-with-an-awesome-api-developer-experience-62dd2fa668f4?source=rss-1bbcfdf4e397------2</link>
            <guid isPermaLink="false">https://medium.com/p/62dd2fa668f4</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[api-integration]]></category>
            <category><![CDATA[api-management]]></category>
            <category><![CDATA[api-gateway]]></category>
            <category><![CDATA[api-development]]></category>
            <dc:creator><![CDATA[Brenton House ️‍♂️]]></dc:creator>
            <pubDate>Tue, 28 Sep 2021 17:44:06 GMT</pubDate>
            <atom:updated>2021-11-04T13:24:45.219Z</atom:updated>
            <content:encoded><![CDATA[<h3>10 Keys to a WINNING API Developer Experience!</h3><p>What does it take to turn the <strong>USERS</strong> of your API Products and API Portfolios into <strong>CHAMPIONS</strong> of your APIs? A <strong>Great API Developer Experience!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i4rqewCYrpfJVytIF6JJ7w.png" /></figure><h4><strong>Let’s face it. Not every API works well.</strong></h4><blockquote><em>But why is that?</em></blockquote><p>What is the difference between an API Portfolio that is a smashing hit and one that is not?</p><p>Well, there are a few very important factors like making sure it works and that has the features that users of the API need and/or want.</p><p>Sometimes, it is because they are missing features.</p><p>Other times, it is because the features that they have, don’t work.</p><p>But often the <strong>API Developer Experience</strong> itself gets forgotten. Most realize that it is something important and necessary but when forced to prioritize it in the long list of backlog items, it often gets bumped down to the bottom.</p><p>If the developer experience for your API products is horrible, users might walk away from your platform instead of being hooked.</p><blockquote><em>What can we do about it?</em></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FU2t_76_EFwI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DU2t_76_EFwI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FU2t_76_EFwI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/38ea4c839d032c777093fbf46e92fbfd/href">https://medium.com/media/38ea4c839d032c777093fbf46e92fbfd/href</a></iframe><p>What exactly does it take for developers and architects to LOVE your API Platform?</p><p>What does it take to turn the USERS of your API Products into <strong>CHAMPIONS</strong> of your APIs?</p><p>I am going to show you the 10 things you need to do to win over the users of your API Portfolio and make them (and you!) successful!</p><p>But first, let’s quickly define a couple of things.</p><h4><strong>First.</strong></h4><h3>What is an API?</h3><p>Basically, it is non-human systems that talk to each other in an agreed-upon way! Most often, people are talking about Web APIs, including things like REST, GraphQL, gRPC, SOAP, etc.</p><h3>What is an API Developer Portal?</h3><p>An <strong>API Developer Portal</strong> can look different depending on the products that are used but most often it is a website that can be used to manage APIs, view documentation, discover APIs, configure things security, and more!</p><blockquote>Okay. Let’s jump into it.</blockquote><blockquote><strong><em>10 Keys to WINNING with an Awesome API Developer Experience!</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*USWCj9MbKKdT9A3Z.png" /><figcaption>Brenton House — API Experience must be Intuitive</figcaption></figure><h3>1. Your API Platform needs to be intuitive.</h3><p>Everything from your API endpoints, API Authentication, API Developer Portal, API Documentation, API code examples.</p><p><strong>Everything!</strong></p><p>For a lot of APIs like REST, gRPC, GraphQL, and other types of APIs, we have some standards.</p><p>Now some of these “standards” are a little loosey-goosey BUT where there aren’t solid guidelines, there are usually some really good published best practices available.</p><p><strong>Follow these.</strong></p><p>Don’t try to come up with your own custom system for APIs or API Portals.</p><h4><strong>Just Don’t.</strong></h4><p>Users will come into this with certain expectations based on industry standards.</p><p>Take advantage of things like OpenAPI, OAuth, AsyncAPI, and Swagger to help you in that process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*IYn_8rabSzXuqlrw.png" /><figcaption>Brenton House — API Experience must be well documented</figcaption></figure><h3>2. Your API Platform needs to be well-documented.</h3><p>How well documented probably depends somewhat on how complex your API Platform is.</p><p>This also goes hand-in-hand with the number 1 rule about being intuitive. The more intuitive your API Platform is, the less reliant on your documentation developers will be.</p><p>There are things you can add to your documentation such as making it interactive. While this might take some additional time in setting up the initial version of this documentation, it can provide a more customized and rich experience for your users.</p><p>Another important part of the API documentation is the changelog.</p><p>It is very important to document what has changed between versions of your API products. Don’t just add a bullet point, if possible, but include how these API calls are different or how a task in the API product will now be performed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*3Bnxg4_Uu24uUuvN.png" /><figcaption>Brenton House — API Experience must have self-service Dev Portal</figcaption></figure><h3>3. You need to have a self-service API Developer Portal of some sort.</h3><p>An <strong>API Developer Portal</strong> is often where you will have the developers go to do things like managing API Keys, creating proxies for APIs, and much, much more.</p><p>If you are using an <strong>API Management system</strong>, you probably already have some sort of an API Developer Portal for the APIs that you are managing in that system but that doesn’t mean that there is nothing that you need to do. Most portals include the ability to customize the portal to fit the needs of your organization.</p><p>If this is the solution that you are using, you will want to make sure that you are presenting things in the best possible way for the users of this portal.</p><p>If you are using your own custom solution for an <strong>API Developer Portal</strong>, a lot of the same rules apply. If this solution is built in-house, you might have more flexibility with what you can change but changes always come with a cost that includes time and resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*DHsXVeniyWNsELGe.png" /><figcaption>Brenton House — API Experience must have great onboarding</figcaption></figure><h3>4. Having an Awesome Onboarding Experience.</h3><p>You know what they say about first impressions, right?</p><p>Well, it’s true.</p><p>This first experience that your users have with your API Platform could make or break your future relationship with this user and affect your bottom line.</p><p>Ideally, you want your users to be able to go from Zero to API in ABOUT 5 minutes.</p><p>A user should be able to:</p><ul><li>Create an account</li><li>Log in</li><li>Create an API key or other authentication token</li><li>Connect to your API</li><li>and challenge completed!</li></ul><h4><strong><em>5 minutes.</em></strong></h4><p>Now, I know not every API or product is the same</p><p>and some are going to be a lot more complicated but in general, let’s aim for 5 minutes.</p><p>I am also not saying that is going to be some masterpiece ready to go into production.</p><p>It is something simple that gives the developer a good feel for your platform and builds a trust level with you and your products.</p><p>If you are taking substantially more time than this, look for your bottlenecks and tackle them to reduce any friction that the user might have when onboarding.</p><p>If you don’t know what your user’s Time to First API is, find that out now!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*Z7uGIIa8gXZMK8at.png" /><figcaption>Brenton House — API Experience must have great errors</figcaption></figure><h3>5. Must have Great Errors.</h3><p>I am not saying that your API should be buggy and have lots of errors, but developers are going to try all sorts of things with your API.</p><p>Things you may not have thought of or maybe things that you have thought of and don’t want them to be able to do.</p><p>When this happens, you will need to provide error responses that are consistent and well-documented.</p><p>There are several different patterns and best practices out there in regards to API errors but be sure you are consistent across your API endpoints. If you are using something like error codes, go ahead and put a URL in the error response that gives the user more context about that error.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*9AvZGhg-cbRA-fY8.png" /><figcaption>Brenton House — API Experience — Keep it Simple!</figcaption></figure><h3>6. You need to keep things simple</h3><p>This applies to your APIs and to your API Developer Portal.</p><p>Don’t overcomplicate things. Focus on one thing at a time and do it really well.</p><p>If there is only one possible thing that the user can do given their current state in your API Developer Portal, then remove or hide the other options. Don’t confuse them but instead guide them to make sure that they are successful (and happy) users!</p><p>Also, when you are focusing on that one thing, be sure it is something that is actually solving a problem for the user.</p><p>Don’t add a bunch of unnecessary steps or tasks in a process flow as this will just frustrate your end-users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*QC2yUlCa6sLlr8b0.png" /><figcaption>Brenton House — API Experience — Don’t be ugly!</figcaption></figure><h3>7. Don’t be ugly.</h3><p>There I said it but it’s true.</p><p>Ugly designs can slow people down.</p><p>This is also directly related to rule number one: API Platforms must be Intuitive. Really poor design of API Developer Portals, API Documentation, and API Endpoints can cause frustration for users.</p><p>Your API Developer Portal or documentation might be ugly because of something as simple as you are using a really bad color palette.</p><p>It could also be that you are trying to cram too much information into one screen.</p><p>It could also be that you don’t understand how the users want to use your portal.</p><p>Take some time to learn more about your users and good design best practices.</p><p>But… Ugliness is not limited to your API Developer Portal or API Documentation.</p><p>It could also be your APIs themselves.</p><blockquote>What do I mean by that?</blockquote><p>Well, I’ve seen some pretty horrendous naming patterns for endpoints and parameters. It may seem like a small thing but you might add some love to your APIs by cleaning them up before publishing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*hKkH1XnZStSe1sUe.png" /><figcaption>Brenton House — API Experience — Show me the code!</figcaption></figure><h3>8. Show me the code!</h3><p>That’s right. Developers who use your APIs want to see some code examples for using your APIs.</p><p>There are several ways to do this.</p><p>Some include this option in the documentation itself but others will incorporate this into the API Developer Portal where the code can be customized to match the specific needs and configuration of that user.</p><p>Either way, you need to include code for a variety of the most commonly used API Client languages.</p><p>Another huge thing related to this is Postman scripts.</p><p>If you don’t know what Postman is, it is THE original (and best) API Client / Testing / Mocking / Everything tool for consuming APIs.</p><p>PLEASE include a Postman collection for your APIs.</p><p>Use things like Postman environment variables to reference configurable things like API keys, endpoints, and such.</p><p>And for bonus points, generate some simple API tests for your calls.</p><p>This will tell the user what to expect when they make successful (and unsuccessful) API calls to your endpoints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*6Xn1uKlaUSGt4rdh.png" /><figcaption>Brenton House — API Experience — Great Logging and Analytics</figcaption></figure><h3>9. API Logging and Analytics.</h3><p>You may not normally think of logging and analytics as something that is related to Developer User Experience but let me show you how it is.</p><p>If you have good logging that is available in a standardized way, a developer will now have access to one more resource that could save YOU time and resources but also possibly get THE USER to a resolved state much quicker.</p><p>Related to this is Analytics.</p><p>Some analytics might be available to a user such as the number of calls.<br>(especially when rate limits are involved),</p><p>But I am talking about some of the analytics that they might never see.</p><p>So if the user can’t see this, how does this benefit the Developer User Experience?</p><p>If you were to thoroughly track what APIs endpoints and methods are being called,</p><p>If you were to thoroughly track what features were being used in your Developer API Portal,</p><p>If you were to thoroughly track what documentation pages were used most often and be able to correlate that to features in your APIs,</p><p>You would then be in the position to know where there might be friction points.</p><p>Where there might be opportunities for feature enhancements.</p><p>You will be able to see what’s hot (and what’s not)!</p><p>Think of it as the developer’s journey through your product.</p><p>Use this data to give your developers the best possible user experience with your APIs, your Developer API Portals, and your API documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ntopXEL5Sww4kgdSx1Pbyg.png" /><figcaption>Brenton House — API Experience — Free Forever Tier</figcaption></figure><h3>10. Free Forever Developer Tier for your API Platform.</h3><p>I cannot emphasize enough how important this is for continuing user satisfaction and relationships with your customer!</p><p>If your API is attractive to developers, there is a good chance that they are going to try it out before their boss tells them that they need to run an official evaluation of your product.</p><p>It might be in a hack-a-thon, side project, or just maybe just because they are curious.</p><p>Either way, developers will often save this off to have working examples of connecting to your API.</p><p>As a developer, you never know when you will need it…</p><p>But if their boss tells them to evaluate your product and it has been over 30 or 60 days and your product’s trial has expired, this is going to leave a sour taste in the mouth of the developer or architect.</p><p>Sure, they can probably get on the phone, call your support department, and get an extension to their trial, but let’s face it.</p><blockquote><em>Nobody wants to have to do that.</em></blockquote><p>I don’t care <strong>HOW</strong> good your support department is.</p><p>Do yourself a huge favor and create a limited tier of your product that is free forever.</p><p>It doesn’t have to have every feature and it can be rate-limited but at least your user’s code will most likely still work when they go to try it later.</p><h3>Conclusion</h3><p>There is a lot to API Developer Experience and this really only scratches the surface.</p><p>Chances are you are already working on (or have successfully accomplished) many of these keys to API Developer Experience but don’t forget about them.</p><p>Take the time as a team to review these and make sure that your APIs (both old and new) as well as your API Developer Portal and documentation are equipping developers and other users to be successful!</p><p>Feel free to connect with me on LinkedIn and ask me any questions or share your experiences with APIs! I would LOVE to hear them!</p><blockquote><a href="https://linkedin.com/in/brentonhouse">https://linkedin.com/in/brentonhouse</a></blockquote><h3>About Brenton House</h3><p>Brenton House is Vice President of Digital Evangelism at Software AG. As an API and Digital Transformation Evangelist and Strategist, he has connected enterprises with API solutions and microservices, to help drive innovation and overall business growth for many organizations.</p><p>In his 25+ years of experience, he has worked across many industries including broadcasting, advertising, retail, financial services, supply chain, transportation, technology, and publishing — gaining a breadth of knowledge on all things APIs and Integrations. His diverse experience set and unique creative skill sets have enabled him to equip organizations in creating captivating and innovative products that delight users.</p><h3>Check out some of our other resources to continue learning more about APIs and Integrations!</h3><p>⭐ Software AG Blog ▪ <a href="https://blog.softwareag.com/">https://blog.softwareag.com</a></p><p>⭐ API Knowledge Portal ▪ <a href="https://knowledge.softwareag.com/">https://knowledge.softwareag.com</a></p><p>⭐ Software AG Tech Community ▪ <a href="https://techcommunity.softwareag.com/">https://techcommunity.softwareag.com/</a></p><p>🎬 Software AG YouTube Channel ▪ <a href="https://youtube.com/softwareag">https://youtube.com/softwareag</a></p><p>🎬 Brenton House’s YouTube Channel ▪ <a href="https://youtube.com/brentonhouse">https://youtube.com/brentonhouse</a></p><p>🎬 API Shorts YouTube Channel ▪ <a href="https://youtube.com/apishorts">https://youtube.com/apishorts</a></p><p>👇👇👇 FREE online API Maturity assessment here! 👇👇👇</p><blockquote><a href="https://www.softwareag.com/api-maturity"><strong><em>https://www.softwareag.com/api-maturity</em></strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62dd2fa668f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brentonhouse/keys-to-winning-with-an-awesome-api-developer-experience-62dd2fa668f4">10 Keys to WINNING with an Awesome API Developer Experience!</a> was originally published in <a href="https://medium.com/brentonhouse">Brenton House — Digital Strategist and Influencer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Saying goodbye to Axway Amplify Platform for Mobile ]]></title>
            <link>https://medium.com/brentonhouse/saying-goodbye-to-axway-amplify-titanium-31a44f3671de?source=rss-1bbcfdf4e397------2</link>
            <guid isPermaLink="false">https://medium.com/p/31a44f3671de</guid>
            <category><![CDATA[titanium-mobile]]></category>
            <category><![CDATA[appcelerator]]></category>
            <category><![CDATA[axway-amplify-platform]]></category>
            <category><![CDATA[axway]]></category>
            <category><![CDATA[brenton-house]]></category>
            <dc:creator><![CDATA[Brenton House ️‍♂️]]></dc:creator>
            <pubDate>Mon, 03 May 2021 22:14:24 GMT</pubDate>
            <atom:updated>2021-11-03T21:28:10.648Z</atom:updated>
            <content:encoded><![CDATA[<h4>🪦 <strong>RIP Axway Amplify Platform for Mobile (2010 - 2022)</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*U1AmmpMwgxCrkjEDRWigsA.jpeg" /><figcaption>RIP Axway Amplify Platform for Mobile (2010–2022)</figcaption></figure><blockquote><em>&quot;Everything has to come to an end, sometime.&quot;</em></blockquote><blockquote><em>- L. Frank Baum, The Marvelous Land of Oz</em></blockquote><p><strong>Axway announces the end to their Axway Amplify Platform product for managing APIs in mobile applications. The End of Life for product is in March 2022.</strong></p><h3>I first met Titanium Mobile a long ago, before she was married to Axway...</h3><p>Back then she was known by her maiden name:</p><h3>Appcelerator</h3><p>It was over 10 years ago and she was so full of life!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/0*VXx8TNvIQCgXECeO.jpg" /></figure><blockquote><em>But first, a little background...</em></blockquote><h3>My name is Brenton House and I ❤️ APIs</h3><p>There. I said it.</p><blockquote>Wait! I thought this was about Titanium and mobile??</blockquote><h3>It is. But to understand mobile (I mean REALLY understand it), you have to understand APIs.</h3><h4>I had invested my career in APIs.</h4><blockquote><strong><em>Designing, Developing, Architecting, and Evangelizing APIs.</em></strong></blockquote><p>I loved seeing the web being created and taking shape.</p><p>Communication standards and APIs (of various shapes, colors, and sizes) appear (and disappear).</p><h3>But mobile was going to change everything.</h3><p>I realized that mobile apps were going to <strong>EXPLODE</strong> the API market as there was suddenly going to be a massive growth in the number of API consumersin the world!</p><p>I never left the API world but I realized that expanding my horizons to include the mobile app economy was essential to being successful with APIs and Integrations in the future.</p><h3>But... I am getting ahead of myself</h3><p>Let me back up a bit...</p><h3>The year is 1989</h3><blockquote>Tim Berners-Lee, a British scientist, invented the World Wide Web (WWW) in 1989, while working at CERN.</blockquote><h4>Wait… let’s not go back that far!</h4><h3>The year is 2007</h3><p><em>although it feels like it was just yesterday.</em></p><p>The mobile development market was suddenly revolutionized with the introduction of the first iPhone by Apple.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*cPyaHY0feV5h7zNd.jpeg" /></figure><p>The first Android phone also released a short time after that and it became clear that developers were either going to have to become experts in both Objective-C for iPhone and Java for Android <strong>or some other solution was going to have to appear.</strong></p><p><em>PhoneGap and similar hybrid &quot;web&quot; mobile apps appeared but most people realized that they were never going to be a serious solution due to the lack of features and performance issues that were inherent to non-native mobile apps.</em></p><h3>The year is 2011</h3><p>I was introduced to <strong>Appcelerator Titanium Mobile</strong>.</p><p>She had already hit her 1.0 version milestone and had quite an active development community.</p><h3>I still remember the first time I saw her.</h3><pre>Write once.  Run Everywhere.</pre><p>With Appcelerator Titanium Mobile, I could write JavaScript code and it would create a native mobile app using Objective-C and Java for the appropriate platforms.</p><h3>WOW!!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/461/0*7QjS2M-xbiECJM2w.png" /></figure><pre>Could it really be that easy??</pre><p>With the introduction of the <strong>Appcelerator Alloy</strong> library for Titanium, the JavaScript features expanded to include an MVC framework with even more options for using JavaScript to access native iOS and Android features! <strong>Titanium Alloy</strong> hit version 1.0 and everything seemed like it was going so well!</p><h3>The year is 2015</h3><p>Facebook released a new product: React Native, a mobile JavaScript platform that seemed to have a similar set of features to Titanium.</p><p>Also <strong>in 2015</strong>, another JavaScript platform, NativeScript, was also released to the community.</p><p>The plans for <strong>Titanium Alloy 2.0</strong> got pushed out and suddenly there was a lot more diversity (and competition) in the cross-platform native mobile market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*aKktRi_ZXtGznpdq.jpg" /></figure><h3>The year is 2016</h3><p>Axway acquired Appcelerator and integrated it into the <strong>Axway Amplify Platform</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/0*yS8YR1wgoPk7JpRr.png" /></figure><p>You may recognize some of the different variations used to reference the <strong>Titanium</strong> products over the next few months that followed!</p><ul><li>Appcelerator Titanium</li><li>Appcelerator Titanium SDK</li><li>Appcelerator Titanium Alloy</li><li>Axway Titanium</li><li>Axway Titanium Mobile</li><li>Axway Appcelerator Titanium</li><li>Axway Appcelerator Titanium SDK</li><li>Axway Appcelerator Titanium Alloy</li><li>Axway Amplify Appcelerator Titanium</li><li>Axway Amplify Appcelerator Titanium SDK</li><li>Axway Amplify Appcelerator Titanium Alloy</li><li>Axway Amplify Titanium Alloy</li><li>Axway Amplify Titanium Mobile</li><li>Axway Amplify Titanium</li></ul><h3>The year is 2018</h3><p>Given my ❤️❤️❤️ for APIs and Integrations -- combined with my personal experience using <strong>Axway Amplify Titanium</strong>, I joined Axway as an API Evangelist!</p><pre>Over the next couple of years, <br>I was able to get creative with a lot<br>of fun blog posts and YouTube videos!</pre><h3>Who can forget, Breaking the Build and important topics like Tabs vs. Spaces? 🤣</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FqYPupvFUpf8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DqYPupvFUpf8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FqYPupvFUpf8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/984ba578be45e6be1d61c8ec82159b10/href">https://medium.com/media/984ba578be45e6be1d61c8ec82159b10/href</a></iframe><h3>With API Cookery we covered API Management and Integrations!</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Ft43USof9K2w%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dt43USof9K2w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Ft43USof9K2w%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/73737b70b87cc3ce5897467a219bb735/href">https://medium.com/media/73737b70b87cc3ce5897467a219bb735/href</a></iframe><blockquote><strong><em>Axway Amplify Titanium</em></strong><em> features continued to be added to the SDK over the next couple of years!</em></blockquote><p>Although Axway Titanium Alloy v2.0 never materialized, I did end up forking Titanium Alloy v1 to add in a bunch of v2 type features to make Titanium easier to use with APIs and Node.js.</p><p>It kinda spun off into its own open-source product <a href="https://github.com/brentonhouse/titanium-turbo"><strong>Titanium Turbo</strong></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*driIcGzYAtzVC65N.png" /></figure><p>It was super cool and I was able to use Titanium Turbo to create native mobile apps faster than I could ever imagine doing before!</p><p>It also made integrating with APIs a snap (which was very important, given my ❤️ for APIs )</p><p>You can see an example of using Titanium Turbo in a complete API and Mobile App solution for managing the return of employees to the office, that we open-sourced last year!</p><h3>Brenton House ⭐️ API Evangelist and Strategist on Twitter: &quot;🚀 @Axway has open-sourced their Mobile App and API!!Transitioning your team back into the workplace safely can be challenging and complex but creating cross-platform native mobile apps and APIs doesn&#39;t have to be! @axwaydev #openeverything https://t.co/pfX85MkHUO / Twitter&quot;</h3><p>🚀 @Axway has open-sourced their Mobile App and API!!Transitioning your team back into the workplace safely can be challenging and complex but creating cross-platform native mobile apps and APIs doesn&#39;t have to be! @axwaydev #openeverything https://t.co/pfX85MkHUO</p><p><em>(SPOILERS: given the recent news, </em><strong><em>Titanium Turbo</em></strong><em> will probably die a nice, quiet open-source death with very little fanfare...)</em></p><h3>The year is now 2021</h3><p>We have now caught up to present day but unfortunately, it also means that we&#39;ve reached the end of our story.</p><p>A few weeks ago, <a href="https://devblog.axway.com/featured/product-update-changes-to-application-development-services-appcelerator/">Axway announced the End-of-Life for </a><a href="https://devblog.axway.com/featured/product-update-changes-to-application-development-services-appcelerator/">Axway Amplify Titanium</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*sXaLUptyE-Ajy7IG.jpg" /></figure><h3>It&#39;s sad saying goodbye!</h3><p>Although Axway will be shutting things down <strong>in March 2022</strong>, because it is an open-source product, forks of it will still live on in the community!</p><p>There are very few products I have been able to closely observe from cradle to grave. It has been a pleasure to work with such an innovative and active community!</p><blockquote><em>API Integrations are sometimes difficult for people to wrap their heads around and Titanium made it easy to be able to see the power of APIs in the palm of their hands!</em></blockquote><pre>Titanium had a great run and <br>I am grateful there are so many <br>in the Titanium community, <br>both past and present, <br>that I can call great friends!</pre><blockquote>On a personal note, I have decided that the timing was right for me to begin a new chapter in my career and I will be leaving Axway this week. I have thoroughly enjoyed my time at Axway and have worked with some truly amazing and talented people!</blockquote><h4>My love for APIs and Integrations has only grown stronger over the past few years and I am going to continue following my passion for evangelizing them to the community!</h4><p>Connect with me <a href="https://www.linkedin.com/in/brentonhouse/">on LinkedIn</a> or <a href="https://twitter.com/brentonhouse">on Twitter</a> as I continue to share what I learn about this crazy digital world we integrate with everyday!</p><h3>Keep Coding Strong!!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31a44f3671de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brentonhouse/saying-goodbye-to-axway-amplify-titanium-31a44f3671de">Saying goodbye to Axway Amplify Platform for Mobile 😢</a> was originally published in <a href="https://medium.com/brentonhouse">Brenton House — Digital Strategist and Influencer</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 API First? API First Explained!]]></title>
            <link>https://medium.com/brentonhouse/what-is-api-first-really-ccc16e8d704f?source=rss-1bbcfdf4e397------2</link>
            <guid isPermaLink="false">https://medium.com/p/ccc16e8d704f</guid>
            <category><![CDATA[api-development]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[api-design]]></category>
            <category><![CDATA[api-first]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Brenton House ️‍♂️]]></dc:creator>
            <pubDate>Wed, 17 Mar 2021 16:05:40 GMT</pubDate>
            <atom:updated>2021-11-04T13:10:47.189Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is API First? 🥇 API First Explained!</h3><p>What is API First? How can I leverage API First to add business value to my organization? Software AG’s Brenton House details what it takes to create a successful API strategy using <strong>API First</strong> principles and practices!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vYIJMzpcW-ATt5baLTvwhw.png" /><figcaption>What is API First? Software AG VP Brenton House</figcaption></figure><p>There is a lot of confusion around “What is API First&quot;, how is it different than &quot;API First Design&quot;, and how all this fits into the Full API Lifecycle Management process. Today, I caught up with Brian Otten who has a proven track record for helping enterprises on their API journey to success!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FTduSd1XfP7k%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DTduSd1XfP7k&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FTduSd1XfP7k%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0b00fbc79a35498c53bdfc2115974764/href">https://medium.com/media/0b00fbc79a35498c53bdfc2115974764/href</a></iframe><blockquote><a href="https://www.youtube.com/watch?v=TduSd1XfP7k&amp;list=PLsy9MwYlG1pdH1Q6k4tPIGjx6y1y0wOvo"><em>↑ Watch video on YouTube ↑</em></a></blockquote><h3>What is API First?</h3><p>To think about API First, you really have to start thinking about your business. How are you reimagining your business? If you have a new business, what is that business going to look like? API First is very much linked to strategy and how you want to merge your business model with the emerging technology model. For most companies, you are going to think of that in terms of creating a digital platform where you can take your world-class products and services and make them consumable. You might also think about how you want to extend your products out so that you can make them all easier to work with.</p><blockquote><em>This is where API First comes in.</em></blockquote><p>API First takes the view of your business as capabilities, with products and services that you are going to deliver. Using API First, you would then enable you to imagine those as a set of API Products or APIs working together to get the data, provide the access, and make it secure. This is the API First way. Instead of starting by building the applications or looking for backend systems of record, you start with API First. This can be a big strategic move for an organization.</p><h3>Is API First the same as API Design First?</h3><p>Short answer is no. API Design First is an essential part of the operations to create the digital products and APIs but API First takes a step back and looks at that reimagined view of your business as a set of interoperable APIs. You are asking questions like:</p><ul><li>What is the value proposition of an API?</li><li>What is the business model behind the product we are going to create?</li></ul><p>When you then go to use API Design First to create the APIs during the API First process, you can leverage the research and strategy from previous steps by asking:</p><ul><li>How did we imagine this solution?</li><li>How do we solve this business problem?</li><li>How do we get real business outcomes from this by having a good design?</li></ul><h3>How does API First work with the Full API Lifecycle Management process?</h3><p>API First feeds and powers the Full API Lifecycle Management process. The stages of an API&#39;s Lifecycle can include things such as:</p><ul><li>Designing and Planning your APIs</li><li>Creating your APIs</li><li>Securing your APIs</li><li>Documenting your APIs</li><li>Testing your APIs</li><li>Versioning your APIs</li><li>Deploying or Publishing your APIs</li><li>Monetizing your APIs</li><li>Observing and Managing your APIs</li><li>Scaling your APIs</li><li>Making your APIs Discoverable</li><li>Retiring (or Sunsetting) your APIs</li></ul><p>Throughout all the Full API Lifecycle Management process, you will view your APIs through the lens of your business strategy. API as a Product will allow every level of your organization to make API decisions knowing how this product fits into your enterprise and how it adds business value. Knowing the business value added by your APIs can make a world of difference to the success of your API Platform.</p><h3>API First, DevOps, Business Ops, Product Ops and more!</h3><p><a href="https://www.youtube.com/watch?v=TduSd1XfP7k&amp;list=PLsy9MwYlG1pdH1Q6k4tPIGjx6y1y0wOvo">Watch the full interview with API Expert, Brian Otten</a>, to hear even more about how API First enables and empowers your organization through DevOps, Business Ops, Product Ops, and more!</p><h4>Stay informed about Best Practices for APIs and Digital Transformation</h4><p>Subscribe to <a href="https://youtube.com/apishorts">API Shorts</a>on YouTube to stay up-to-date with the ever-changing world of APIs and Digital Transformation!</p><h3>About Brenton House</h3><p>Brenton House is Vice President of Digital Evangelism at Software AG. As an API and Digital Transformation Evangelist and Strategist, he has connected enterprises with API solutions and microservices, to help drive innovation and overall business growth for many organizations.</p><p>In his 25+ years of experience, he has worked across many industries including broadcasting, advertising, retail, financial services, supply chain, transportation, technology, and publishing — gaining a breadth of knowledge on all things APIs and Integrations. His diverse experience set and unique creative skill sets have enabled him to equip organizations in creating captivating and innovative products that delight users.</p><h3>Check out some of our other resources to continue learning more about APIs and Integrations!</h3><p>⭐ Software AG Blog ▪ <a href="https://blog.softwareag.com/">https://blog.softwareag.com</a><br>⭐ API Knowledge Portal ▪ <a href="https://knowledge.softwareag.com/">https://knowledge.softwareag.com</a><br>⭐ Software AG Tech Community ▪ <a href="https://techcommunity.softwareag.com/">https://techcommunity.softwareag.com/</a><br>🎬 Software AG YouTube Channel ▪ <a href="https://youtube.com/softwareag">https://youtube.com/softwareag</a><br>🎬 Brenton House’s YouTube Channel ▪ <a href="https://youtube.com/brentonhouse">https://youtube.com/brentonhouse</a><br>🎬 API Shorts YouTube Channel ▪ <a href="https://youtube.com/apishorts">https://youtube.com/apishorts</a></p><p>👇👇👇 FREE online API Maturity assessment here! 👇👇👇</p><blockquote><a href="https://www.softwareag.com/api-maturity"><em>https://www.softwareag.com/api-maturity</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccc16e8d704f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brentonhouse/what-is-api-first-really-ccc16e8d704f">What is API First?🥇 API First Explained!</a> was originally published in <a href="https://medium.com/brentonhouse">Brenton House — Digital Strategist and Influencer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Things to do NOW for Apple App Tracking Transparency API]]></title>
            <link>https://medium.com/brentonhouse/5-things-to-do-now-for-apple-app-tracking-transparency-api-be2547ac7eea?source=rss-1bbcfdf4e397------2</link>
            <guid isPermaLink="false">https://medium.com/p/be2547ac7eea</guid>
            <dc:creator><![CDATA[Brenton House ️‍♂️]]></dc:creator>
            <pubDate>Tue, 23 Feb 2021 22:19:52 GMT</pubDate>
            <atom:updated>2021-02-24T13:56:08.040Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Here are the 5 things you need to do right now to be prepared for Apple’s new App Tracking Transparency API!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PxyHe4CFRqiD5d2zcnypJg.png" /><figcaption>5 Things to do NOW for Apple App Tracking Transparency API — API Cookery with Brenton House — API Best Practices for Digital Transformation</figcaption></figure><p>In the past few weeks and months, there has been a lot of the talk and controversy around Apple’s new Tracking Transparency API. The discussions center around access to the Identifier for Advertisers or the IDFA. The IDFA is an ID that allows apps and APIs to uniquely identify a user across multiple apps and websites.</p><p><a href="https://www.youtube.com/watch?v=hXKyQ_ngTGo&amp;list=PLsy9MwYlG1pdH1Q6k4tPIGjx6y1y0wOvo">https://www.youtube.com/watch?v=hXKyQ_ngTGo&amp;list=PLsy9MwYlG1pdH1Q6k4tPIGjx6y1y0wOvo</a></p><p>🎬 <a href="https://api.cookery.dev/">Check out more API videos here!</a> (BYOP — Bring your own 🍿)</p><p>The IDFA is most commonly used by advertisers such as Facebook but it is also used by some apps for fraud detection and other non-advertising purposes.</p><p>The IDFA is why you will be looking at a product on one website or app and suddenly you see an ad for the same product in a completely different app or website. This ID allows advertisers to keep track of who you are and, when combined with additional information collected across different apps, can give a <strong>very detailed profile</strong> about a user without them ever knowing.</p><p>Apple has decided to change how the API for the IDFA works. It’s not going away, but will now require apps to prompt users and ask them if it is OK to get access to the IDFA for tracking purposes.</p><p>Here are the 5 things you need to do right now as an App or API publisher to be prepared for Apple’s new App Tracking Transparency API.</p><h3>1️⃣ If you want access to IDFA, you have to request it</h3><p>If the user says NO, you are not going to be able to access the IDFA.</p><p>Although Apple introduced this API in 2020, they have not been actively enforcing it. But with the upcoming iOS release, Apple is requiring the permission prompt and will be working to enforce this API and their policies using automated and manual processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*S4Y7qrNkHaD8ojf5Yh0jlA.png" /></figure><h3>2️⃣ Need to check your APIs and SDKs</h3><p>You need to thoroughly check your APIs and SDKs to ensure that you prompt users for permission if you are using the IDFA. If your app (or an 3rd party app that uses your API), tries to use the IDFA without permission, you could be banned by Apple. A good percentage of users will probably decline permission for this and that could cause problems for you or your users if it breaks functionality.</p><h3>3️⃣ Need to check your 3rd Party APIs and SDKs</h3><p>You may be thinking “I’m not using the IDFA so I am safe”. While this may be partially true, you may not be directly accessing the IDFA in your apps or APIs but there is a pretty good possibility that the IDFA may be being used by 3rd party SDKs or APIs that you are dependent on. You will need to do a deep look at all 3rd-party components for uses of the IDFA and that may not be an easy task, depending on the complexity and size of your mobile apps. If a third-party API or SDK is using the IDFA, you will need to contact them about an updated version of their API.</p><h3>4️⃣ Look for Alternatives to IDFA</h3><p>The tracking permission screen is kind of a scary prompt for users. Big Tech companies like Facebook, who are very depending on the IDFA and user information for their business, are creating explanation screens to try to soften the blow and to try convince users agree to letting Facebook track them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*M6pYhJSLbIXALsXUdQaaFQ.png" /></figure><p>Due to the fact that a lot of users are not going to approve permissions to track combined with the complexity of other privacy regulations, means that API Publishers are going to be looking for new and creative ways to be able to track users without the IDFA but that will not be an easy process.</p><p>Apple is pushing publishers to use the <a href="https://developer.apple.com/documentation/storekit/skadnetwork">Apple SkAdNetwork</a> as an alternative to using the IDFA. The problem with this is that now you would be using a system where Apple owns the entire process and thus your data is controlled by them.</p><h3>5️⃣ Get ready for Google changes</h3><p>Google has an equivalent ID called the Google Play Services ID for Android or <strong>GPS ADID</strong>. Be on the lookout for upcoming changes to these APIs as well, because, as rumor has it, changes to these APIs will be coming soon.</p><p>Stay informed about the Apple Tracking Transparency APIs and upcoming changes so that you and your business will not be disrupted!</p><p>In addition, you can subscribe to <a href="https://api.cookery.dev/">API Cookery</a> on YouTube to stay up-to-date with the ever changing world of APIs and Digital Transformation!</p><p><strong>💡 </strong><a href="https://www.axway.com/en/modernize/10-api-best-practices-drive-digital-success?utm_source=youtube&amp;utm_medium=social&amp;utm_campaign=api_cookery"><strong>Learn more about API Strategy and Best Practices [Free Download]</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be2547ac7eea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brentonhouse/5-things-to-do-now-for-apple-app-tracking-transparency-api-be2547ac7eea">5 Things to do NOW for Apple App Tracking Transparency API</a> was originally published in <a href="https://medium.com/brentonhouse">Brenton House — Digital Strategist and Influencer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What are API Rate Limits?]]></title>
            <link>https://medium.com/brentonhouse/what-are-api-rate-limits-67ae16ba80f7?source=rss-1bbcfdf4e397------2</link>
            <guid isPermaLink="false">https://medium.com/p/67ae16ba80f7</guid>
            <dc:creator><![CDATA[Brenton House ️‍♂️]]></dc:creator>
            <pubDate>Wed, 10 Feb 2021 20:54:20 GMT</pubDate>
            <atom:updated>2021-02-17T16:53:21.209Z</atom:updated>
            <content:encoded><![CDATA[<p>API Rate Limiting is simply controlling how many requests, or calls, an API consumer can make to your API. You may have experienced something related as a consumer with errors about “Too many connections” or something similar when you are visiting a website or using an app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9LMn5afRGJcJ_2j-3wvp0w.png" /><figcaption>API Rate Limits Explained — Master API Chef and Strategist, Brenton House</figcaption></figure><h3><strong>What is an API Consumer?</strong></h3><p>An API consumer could be a mobile app, a website, or even your doorbell or thermostat! Anything that makes a call to an API to get data is an API consumer. These are made via API Requests.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_ULOJF56XMY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_ULOJF56XMY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_ULOJF56XMY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b3281f8b8f2b0e4e2284e1f16ba3812c/href">https://medium.com/media/b3281f8b8f2b0e4e2284e1f16ba3812c/href</a></iframe><blockquote>🎬 <a href="https://api.cookery.dev/">Check out more API videos here!</a> ( BYOP — Bring your own 🍿 )</blockquote><h3><strong>What is an API Request?</strong></h3><p>An API request (or call) is where one of these consumers, say your thermostat, <em>requests</em> information from “the cloud” (or servers on the internet).</p><p>Say your thermostat wants to find out what the current weather conditions are so that it can display those for you.</p><p>That would be an API request.</p><p>The largest number of API requests, by far, come from mobile apps. A single mobile app might make between 10–20 API requests, just by you opening an app and logging in!</p><h3>How are API Rate Limits typically set?</h3><p>API Rate limits are typically setup to limit the number of requests either by:</p><ul><li>per second</li><li>per minute</li><li>per hour</li><li>per day (or 24 hour period)</li><li>per month</li></ul><p>An API is not limited to picking just one of these. You could have one API Rate limit for per-second and a different API Rate Limit per-hour. One or more API Rate Limits can be active at the same time.</p><p>API Rate Limiting might even be implemented differently depending on if you are authenticated or not. Authenticated API users (or API consumers that have included their credentials in the API Call) might be allowed more requests than users who are anonymous.</p><h3>Do I need to implement API Rate Limiting?</h3><p>Most likely, Yes. But it is important to understand the reasons why you might need them. If you are going to measure the success (or failure) of rate limits, you have to have a clear and defined purpose.</p><h3>What are reasons typically given for needing API Rate Limits?</h3><blockquote>Here are some of the reasons you might hear but not every one of these problems is best solved by API Rate Limits!</blockquote><h4>Protect your APIs from Distributed Denial of Service Attacks or DDoS.</h4><p>While these attacks are a very real threat and can take down your API (which is a bad thing), API Rate limiting is probably not the right solution for blocking these attacks. There are other, and more robust, solutions for protecting your APIs from DDoS that should be looked at first.</p><h4>Limit your backend expenses and costs</h4><p>This can be a very legitimate reason for implementing API Rate Limiting. Let’s go back to the thermostat example. Say there is a line of thermostats that go bonkers and go into some loop where they are calling your weather API over and over. While this might not take down your API, it could cost you a pretty penny because you are the one that has to pay for all the backend servers and services that make that weather API work! By limiting the calls per consumer, you could protect your resources and money!</p><h4>Work around hardware limitations</h4><p>Getting a lot of API calls could mean that your backend servers can’t keep up properly. This could lead to bottlenecks and the equivalent of driving on the highway during rush hour traffic. It could slow everyone down as requests are queued up. Slow API calls could mean things like really slow web pages and really unhappy users.</p><h3>What are my options for implementing API Rate Limits?</h3><blockquote>There are a few different ways of handling API Rate Limits:</blockquote><ul><li>Hard Stop: This means an API Consumer will get an Error 429 when they call your API, if they are over their limit.</li><li>Soft Stop: In this case, you might have a grace period where calls can continue to be made for a short period of time after the limit is reached.</li><li>Throttled Stop: You might just want to enforce a slow-down on calls made over the limit. This way users can continue to make calls but they will just be slower because they are over the limit.</li><li>Billable Stop: You might just charge the API consumer for calls made over their limit. Obviously this would only work for authenticated API users but can be a valid solution.</li></ul><h3>💡 BONUS TIPS for API Rate Limits!</h3><blockquote>If you don’t want your API Users to hate you, there are three things you need to do:</blockquote><h3>1️⃣ Don’t be greedy</h3><p>As we talked about earlier, there are several reasons for needing to implement API Rate Limits. Getting too greedy with your limits though, can keep users from being able to implement the solutions they need to help them win. You win when your users win so don’t drive them to abandon <em>your</em> API for a competitor’s API because you arbitrarily set your limits to low.</p><h3>2️⃣ Be transparent and informative</h3><p>Be transparent with users on how you implemented API Rate Limiting and what methods you choose to handle it when users go over their limit. You really want to make sure that you are up-front with your users if you are going to be charging them for overages.</p><p>Clearly document everything and educate your users, not only about your API Rate Limiting Policy, but also about steps they can take to avoid hitting those limits.</p><h3>3️⃣ Let API consumers know what the status of their API Limits are in every call</h3><p>There are a couple of different ways to implement this but most APIs will add a header to the API response that tells the consumer how many calls they have left for this period of time and when the counter will reset.</p><p>This way API Consumers can make informed decisions about when (and how many) API calls to make.</p><blockquote>💡 <a href="https://www.axway.com/en/modernize/10-api-best-practices-drive-digital-success?utm_source=api_cookery">Learn more about API Strategy and Best Practices [Free Download]</a></blockquote><blockquote>🎬 Check out more API videos here! ( BYOP — Bring your own 🍿 )</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67ae16ba80f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/brentonhouse/what-are-api-rate-limits-67ae16ba80f7">What are API Rate Limits?</a> was originally published in <a href="https://medium.com/brentonhouse">Brenton House — Digital Strategist and Influencer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>