<?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 Adeel Ali on Medium]]></title>
        <description><![CDATA[Stories by Adeel Ali on Medium]]></description>
        <link>https://medium.com/@adeel.ali?source=rss-8e67d090603d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DOu5OA4u7iwJ11SZ41v-Kw.jpeg</url>
            <title>Stories by Adeel Ali on Medium</title>
            <link>https://medium.com/@adeel.ali?source=rss-8e67d090603d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:32:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adeel.ali/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[Bridging the Gap: Modernizing Open Banking APIs in Aotearoa]]></title>
            <link>https://medium.com/@adeel.ali/bridging-the-gap-modernizing-open-banking-apis-in-aotearoa-c058de3792bd?source=rss-8e67d090603d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c058de3792bd</guid>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[api-integration]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[open-banking-api]]></category>
            <category><![CDATA[open-banking]]></category>
            <dc:creator><![CDATA[Adeel Ali]]></dc:creator>
            <pubDate>Thu, 04 Sep 2025 02:21:52 GMT</pubDate>
            <atom:updated>2025-09-04T02:21:52.720Z</atom:updated>
            <content:encoded><![CDATA[<p>On March 29, 2025, New Zealand’s Consumer Data Right (CDR) became law, marking a milestone in the nation’s digital finance journey. By December 2025, all major banks are required to have live, production-ready Open Banking APIs — ushering in a new era of consumer empowerment and fintech innovation.</p><p>The momentum is real: On May 30, 2025, ANZ, ASB, BNZ, and Westpac jointly launched Payment Initiation API v2.3. This release introduces enduring payment consent and decoupled authentication. Such advancements and technical upgrades will fundamentally reshape how Kiwis interact with their money.</p><h3>The Overlooked Frontier: Developer Experience</h3><p>Much of the Open Banking conversation centres on policy frameworks, data standards, and commercial models. But there’s a crucial, often-overlooked audience: the developers. These are the people who transform standards into real-world products — navigating OAuth flows, parsing JSON payloads, testing endpoints, and debugging cryptic errors.</p><p>For every new API version or regulatory update, there’s a developer somewhere in Aotearoa wrestling with integration challenges. Their journey — onboarding, building, and launching — is the true test of Open Banking’s promise.</p><h3>Why Developer Experience Drives ROI?</h3><p>Open Banking APIs aren’t just technical interfaces — they’re products. And like any product, the <strong>user experience matters</strong>, especially for those integrating and consuming the APIs. A seamless developer experience isn’t just a “nice to have” — it’s a direct driver of ROI for banks and fintechs. Here’s why:</p><ul><li><strong>Faster Onboarding</strong>: A huge chunk of developers time is wasted in learning how an API works, especially understanding different types of authentication schemes and writing code for them, frustrating both developers and business leaders. The quicker a developer can go from documentation to a working integration, the sooner products reach customers.</li><li><strong>Reduced Errors</strong>: Clear code samples, robust SDKs, and interactive docs mean fewer bugs and support tickets.</li><li><strong>Accelerated Innovation</strong>: When integration is painless, fintechs can focus on building value, not wrestling with plumbing.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*tDSkGkSXVcUhB_2o" /><figcaption>Developer experience ingredients (SDKs etc.) can reduce API onboarding &amp; integration time from months to hours</figcaption></figure><p>In the highly competitive fintech space, <strong>time-to-market can define success</strong> — and developer experience (DX) is a key lever in speeding up that journey.</p><h3>APIMatic: A Kiwi Solution to a Global Problem</h3><p>This is where APIMatic steps in. Born in Auckland a decade ago, the DX platform has been trusted by the likes of <strong>PayPal, Shell, Verizon, WorldPay, Akoya </strong>and many more for maximizing API adoption and prompt developer onboarding.</p><p>How big of an impact a good developer experience can create? Look at this SDKs installations curve for a world renowned merchants payments processing API, powered by APIMatic.io:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/0*1W9fixuqsRt5rIQl" /><figcaption>SDKs installations for a Fortune 500 payments processing API, powered by APIMatic</figcaption></figure><h3>A Personal, Failed Attempt with NZ Open Banking</h3><p>I discovered the<a href="https://www.apicentre.paymentsnz.co.nz/"> API Centre</a> during COVID days, and immediately went on trying it to solve an internal use case. My need was to integrate incoming wire transfer notifications from our New Zealand bank account into a Slack channel, so my sales team could access this information without needing my direct involvement.</p><p>I asked a developer to build the integration using the “Account Information API”. However, we had to abandon the project after realizing that the API was not available in production at our bank. In addition, the significant hurdles my developer faced just to access the API Centre’s sandbox made me reflect on the challenges developers might encounter in integrating Open Banking APIs in future.</p><h3>New Zealand’s Open Banking APIs — The Experience for Consumers of Today and the Future</h3><p>My failed attempt did spark the idea of modernizing Open Banking API experience in Aotearoa, but I was not sure if the banks and FinTechs are ready for it. Now, with Open Banking going live in 2025, I think this is the right time to empower developers with an experience that could save a ton of their time and energy.</p><h3>An Advanced API Portal</h3><p>Today, when you land on the API centre Sandbox, you see a decade-old<a href="https://developer.apicentre.middleware.co.nz/openbanking/accounts/v2.3"> Swagger User Interface</a> to try out the APIs. SwaggerUI was quite popular in 2010s, but today developers expect much advanced features like SDKs &amp; API Recipes in multiple programming languages. Moreover, with the recent proliferation of vibe coders, AI-native stack, and potential AI agents, features like MCP servers and API Copilots will likely to form a new norm. That’s exactly what APIMatic is building for the API consumers for today and the future.</p><p>As a demo, we generated<a href="https://api-center.demo.apimatic.io/"> an advanced portal</a> to use the “Account Information API” from PaymentsNZ’s API Centre. This portal is mainly composed of 11 elements, divided into 2 categories:</p><ol><li>API essentials such as <strong>SDKs, API Recipes </strong>and <strong>Code Samples</strong>, and</li><li>The AI additions including <strong>MCP servers</strong> and <strong>Integrate in Cursor</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GKHz7ORR6Cmya9yO" /><figcaption>Try this portal live here:<a href="https://api-center.demo.apimatic.io/"> https://api-center.demo.apimatic.io/</a></figcaption></figure><h3>I- API Essentials for Prompt Onboarding and Integration</h3><p>APIs are integrated by writing a lot of code. Smart companies realize the fact, and provide pre-built code to save over 80% of integration efforts for their consumers (watch<a href="https://www.youtube.com/watch?v=30aVCbgihuU"> this video</a> for details). That pre-built code is deterministic in nature to provide identical experience to all the API consumers.</p><h4>1. Easy Auth:</h4><p>Probably the most time consuming task to make the first API call is setting up authentication. As an experiment, we placed the authentication button on top right corner of the portal. This button performs the OAuth dance in the background, and fetches the token for a user right at the portal. The fetched token is automatically added to all the API calls from there on, and remains available throughout the session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QnwfLoU_il8v95Ruk422dw.gif" /></figure><h4>2. SDKs for the fastest integration:</h4><p>The portal is live with published SDKs in 7 languages: Java, C#, Python, Ruby, PhP, Typescript and Go. Providing SDKs in major programming languages allows developers to interact with APIs using the technology stacks they know best. This accelerates integration, ensures fewer errors, and reduces onboarding time — critical in finance, where accuracy and speed directly affect go-to-market timelines. Keen to know if you want to more languages to be added.</p><h4>3. API Recipes <strong>for self-onboarding</strong>:</h4><p>Like cooking recipes help chefs, API recipes get developers up and running with API use cases within no time. API recipes demonstrate how to combine multiple endpoints to accomplish a use case or a workflow — like initiating a payment and confirming authorization or fetching account balances and transaction histories in one flow (watch this<a href="https://www.youtube.com/watch?v=mAT0Lfok6bk"> demo video</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lPK83JP7s3qgHx5M" /><figcaption>API Recipes for step-by-step API workflows</figcaption></figure><h4>4. Idiomatic Code Samples</h4><p>Idiomatic code samples — examples that follow the conventions and style of each programming language — help developers write code that feels natural and maintainable. In finance and open banking, where security, reliability, and clarity are paramount, such code samples reduce friction, streamline understanding, and lower the chance of bugs or misuse. They empower both newcomers and experts to quickly grasp the best practices for integrating with your API.<br>The code samples in the portal can be dynamically generated, and are fully compatible with the available SDKs in all 7 languages.</p><h4>5. Interactive API Reference</h4><p>An interactive API reference lets developers explore endpoints, try out requests, and see live responses, all within the documentation. This hands-on approach is invaluable in complex financial scenarios, allowing developers to validate their understanding and experiment safely before deploying changes to production. Interactive references significantly improve onboarding speed and minimize costly integration errors.</p><h3>II- AI Additions for Next-Gen Developers,Vibe Coders and Agents</h3><p>We recently hosted a students’ hackathon, and were amazed to notice the extensive use of AI coding assistants by young developers of today — and mainstream developers of tomorrow. Moreover, the AI Agents in future will not be “reading” API documentation like developers do — they’ll interact with APIs through standardized machine-readable protocols (like MCP, OpenAPI with LLM extensions etc). Therefore, it is important to add support for the AI-driven API consumption today, and keep improving as the technology evolves.</p><h4>1- MCP Server for AI Agents:</h4><p>Model Context Protocol (MCP) servers streamline how AI agents and applications access financial data and services. They act as standardized intermediaries between AI tools and APIs — banking, trading, compliance, or analytics — ensuring secure, consistent, and efficient data exchange.</p><p>MCP enables interesting business cases for non-technical users via AI agents. For example, APIMatic recently won 2nd prize at an Open Banking conference in New York. The winning solution, <strong>“Talk to Your Bank Account”</strong>, helps users interact with their bank accounts using natural language. Instead of looking through complicated dashboards, users can simply ask questions like “How much did I spend last month on groceries?” and get instant answers. It’s like having a smart financial assistant in your pocket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1l3KDRm01lamkdUE" /></figure><h4>2- API Copilot for unlimited use cases:</h4><p>Writing integration code for API use cases typically involve stitching multiple endpoints together, resolving authentication, creating HTTP request, dealing with serialization and what not. What if you get all this code in a language of your choice by just asking? The API Copilot understands your query, and uses AI + deterministically generated APIMatic code to give you the production-ready code for the desired use case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Q3d8XUaVzhJzeEMD" /></figure><h4>3- AI Tools Integration to Meet Developers Where They Code:</h4><p>Gartner projects that by 2028, 75% of enterprise software engineers will use AI coding assistants — up from under 10% in early 2023. That’s in addition to a vast number of vibe coders — materialzing their visions into apps within a matter of hours. Therefore, we are adding support to integrate APIs right within an IDE or an AI coding assistant. The real substance are the deterministically generated SDKs, which solve the hallucinations problem and massively bring down the cost of using an AI coding assistant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/0*BAv20xsMvnXbTl95" /></figure><p>The above portal supports integration in Cursor, while support for other tools is being added as I write these lines.</p><h3>Conclusion: A Call for Modern API Experience</h3><p>It’s time for New Zealand’s API ecosystem, particularly in Open Banking, to <strong>elevate the developer experience</strong>. Please<a href="https://api-center.demo.apimatic.io/"> try out this demo portal</a> or watch <a href="https://www.linkedin.com/feed/update/urn:li:activity:7366644267135459329/">this 3 mins video introduction</a> for Account Information API, and let us know what you think?</p><p>At APIMatic, we are ready to bridge the gap by providing Open Banking APIs in New Zealand (and worldwide) with all the tools and features that developers love. Let’s make API integration faster, smoother, and more efficient — just as it should be. Let’s make API integration faster, smoother, and more efficient — just as it should be.</p><p>#OpenBanking #API #Fintech #APIMatic #DeveloperExperience #NZTech</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c058de3792bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Futures: Docs-Bots, API Assistants & OpenAPI Auto Fixing]]></title>
            <link>https://medium.com/apimatic/api-futures-docs-bots-api-assistants-openapi-auto-fixing-384b9e1ff64f?source=rss-8e67d090603d------2</link>
            <guid isPermaLink="false">https://medium.com/p/384b9e1ff64f</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[apidocgen]]></category>
            <category><![CDATA[open-api]]></category>
            <category><![CDATA[ai-assistant]]></category>
            <category><![CDATA[api-documentation]]></category>
            <dc:creator><![CDATA[Adeel Ali]]></dc:creator>
            <pubDate>Thu, 15 Feb 2024 23:04:49 GMT</pubDate>
            <atom:updated>2024-02-15T23:12:35.626Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*eAd_WjJfec91eSBYlD5o_g.png" /></figure><p>2024 marks the first decade of APIMatic incorporation. That’s quite a lot of time being part of this beautiful community of API developer tools and witnessing the API industry evolving right in front. From new API description formats popping up to old ones fading away, from the love of HATEOAS to the rise and fall of microservices, the GraphQL storm, some big acquisitions and a few sad exits, tech alliances, patent fights, standardization efforts — it’s been an exciting rollercoaster!</p><p>Where is the industry heading in the future? From the learnings of a company focused on improving the developer experience of both API providers and consumers, we pick three active areas of innovation:</p><h3>1- API Docs-Bots to Massively Reduce Developers’ Onboarding Time</h3><p>API documentation solutions have come a long way in the past few years. Features like <a href="https://www.apimatic.io/blog/2020/06/the-anatomy-of-api-code-samples">runnable code samples</a>, and <a href="https://www.youtube.com/watch?v=eQNup8UicHw">guided walkthroughs</a> help developers get up and running quickly with an API. Still, a learning curve is involved before a developer can start writing the integration code.</p><p>In future, that learning curve and long API onboarding steps will likely be replaced by Generative-AI. For example, instead of going through each endpoint, reading the docs, and writing the code for authentication flow, a developer can ask a query to an “API Docs-Bot” in natural language, and get the integration code for the desired use case in a few seconds.</p><h3>What About Code Reliability?</h3><p>At the moment, Gen-AI is good at generating syntactically correct code, but it lacks the understanding of the semantics. Therefore, a challenge would be training the AI-bot to generate production-ready integration code for different scenarios. A couple of ways to solve this problem are using:</p><ol><li><strong>An expert developer</strong>: to feed detailed prompts to Gen-AI, and keep refining until the integration code of a desired quality level is returned. It is manual and hard to scale.</li><li><strong>A sophisticated code generator for APIs</strong>: to train the AI on the SDK of an API so that its responses are based on deterministically produced code by the code generator.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/0*s3q8EQLZcgLc5WDD" /></figure><p>To test the solution # 2, we’ve conducted a few experiments using APIMatic, and the initial results of creating an API Docs-Bot by combining the two machines have been quite promising (see the demo video below). Expect to see similar attempts in 2024 by API solution providers.</p><p><a href="https://www.apimatic.io/hubfs/chatbot%20demo.mp4">https://www.apimatic.io/hubfs/chatbot%20demo.mp4</a></p><h3>2- AI Assistants to let Non-Developers Play with APIs</h3><p>Developers or non-developers, we all use APIs. The difference is, developers build apps using APIs, while non-developers use APIs via those apps. Moreover, developers can use an API for countless use-cases, while non-developers can only try limited use-cases built in an app by a developer.</p><p>Imagine, I want to know how many times I went to restaurants in the past 12 months, what was the total expense, and the average cost per visit? Today, my options are</p><ol><li>to download and look manually into my bank statements, or</li><li>find a FinTech app which offers this functionality, or</li><li>get a developer to write an app using OpenBanking APIs.</li></ol><p>Later on, what if I want to see my top expense categories of the last 2 years as a graph? Again do it manually, or stay dependent on the functionality built by a developer.</p><p>The good news is that Gen-AI is quite capable of removing this dependency, i.e. letting non-developers access an API the way they want without needing a developer in the middle using AI assistants. Because of its conversational nature, the end users can easily provide their input in natural language, and further refine the output conversationally if needed.</p><p>In 2024, we expect to see a plethora of AI-assistants. However, similar to the API Docs-Bot case, training the Gen-AI to reliably access data from an API and converting that into information takes a considerable amount of time. A quicker way would again be using a code generator to reliably and instantly get the integration code, and train the AI to process the data coming through the APIs.</p><p>During the recent holidays, we experimentally built a financial assistant using Payments New Zealand’s <a href="https://www.apicentre.paymentsnz.co.nz/">OpenBanking APIs</a>. Here are a couple of queries in the screenshot below to depict the outcome (the sandbox data has been expanded to try different scenarios):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WGw6AjTm_LdCCrQJ.png" /></figure><h3>3- Governance — from OpenAPI Ratings to OpenAPI Fixing</h3><p>As the significance of API governance and design continues to grow, we see some new tools arriving in the market with a focus on assessing the quality of an API through its API definition. Two noteworthy examples include Zuplo’s <a href="https://ratemyopenapi.com/">Rate my API</a> and Trebble’s <a href="https://apiinsights.io/">API Insights</a>. Both tools audit API definitions against certain standards/conventions and then assign them a good/bad score for various categories including design, security, completeness and more. By highlighting specific areas of improvement, these tools empower API designers to make their definitions flawless. At APIMatic as well, we try to help API designers make their definitions better for stronger SDK and documentation generation. Following is what a audit snapshot of a typical OpenAPI with some validation and linting issues usually looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*U4kxeRTkQPu8taf4KZon_w.png" /><figcaption>Audit summary of an OpenAPI definition file — auto-generated by APIMatic</figcaption></figure><h3>Why is a Flawless API Definition Important?</h3><p>GIGO (Garbage In, Garbage Out) is a familiar slang in the computer science world, meaning a flawed input would produce a nonsense output. GIGO is perfectly applicable to the processes needing OpenAPI definitions as the input. If you’re looking to <a href="https://caseysoftware.com/blog/how-chatgpt-will-solve-all-api-problems-except-yours">feed your OpenAPI definition to Gen-AI</a>, want to generate Docs, SDKs or do anything else, you either ensure a flawless API definition or don’t mind piling up some garbage. This problem is not new for API definition files (see some common mistakes from 2018 in <a href="https://www.apimatic.io/blog/2018/03/common-mistakes-developers-make-in-their-openapi-3-files">OpenAPI</a>, <a href="https://www.apimatic.io/blog/2018/09/common-mistakes-developers-make-in-their-api-blueprint-files">APIBlueprint</a> and <a href="https://www.apimatic.io/blog/2018/04/common-mistakes-developers-make-in-their-raml-files">RAML</a> definitions), but it is growing in magnitude and demands immediate attention. Based on APIMatic users we saw:</p><ul><li>20% of the total OpenAPI definitions brought to APIMatic violated OpenAPI standards and failed during the import process, whereas</li><li>50% of them conformed to OpenAPI standards but lacked the elements required to generate viable integration code.</li></ul><h3>Towards a Future of Auto-Fixing</h3><p>While an audit report helps identify the issues, somebody still has to fix those problems. This is the hard part due to the time and resources one requires to rectify a complex OpenAPI definition, especially if they are not too familiar with the syntax. Can AI help with the auto-fixing? Yes, but the reliability will remain a question unless somebody pays to train like an LLM. Till then, OpenAPI experts or man-made machines with pre-defined rules will keep on helping the API designers.</p><p>Therefore in 2024, we expect to see the audit tools moving a step forward, and help designers with (semi) automatically fixing the issues. At APIMatic, we’re running a movement with the name “<a href="https://www.apimatic.io/blog/2023/10/fix-my-openapi-vs-code-extension">Fix My OpenAPI</a>”, primarily focused on SDK and Docs generation. There is a free-to-use VS Code extension that comes with over 1200 predefined out-of-the-box rules. It not only ensures strict adherence to API standards but also recommends improvements and best practices to enhance one’s API definition. Moreover, there is an “auto-fix” feature in the extension to help remove some pesky issues with just a few clicks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/0*1s57BbDrET7xTF3B.png" /></figure><p>That’s it for today. Let’s see what new and improved tooling 2024 brings up to help API designers while they curate OpenAPI definitions, and how far does the Generative-AI wave take the API space. Feel free to reach out at <a href="/service/mailto:adeel@apimatic.io">adeel@apimatic.io </a>for any feedback, or if you want to try out the Gen-AI POCs mentioned in this blog. I also want to acknowledge team APIMatic especially <a href="https://www.apimatic.io/blog/author/muhammad-saeed">Saeed</a>, <a href="https://www.apimatic.io/blog/author/ali-raza">Ali</a>, <a href="https://www.apimatic.io/blog/author/faria-rehman">Faria</a> and <a href="https://www.apimatic.io/blog/author/sid">Sidney</a> for their valuable input and R&amp;D initiatives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=384b9e1ff64f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apimatic/api-futures-docs-bots-api-assistants-openapi-auto-fixing-384b9e1ff64f">API Futures: Docs-Bots, API Assistants &amp; OpenAPI Auto Fixing</a> was originally published in <a href="https://medium.com/apimatic">APIMATIC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome Sid to the Mission of Simplifying API Consumption]]></title>
            <link>https://medium.com/apimatic/welcome-sid-to-team-apimatic-cdc80fc364c7?source=rss-8e67d090603d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdc80fc364c7</guid>
            <category><![CDATA[api-client-libraries]]></category>
            <category><![CDATA[apimatic]]></category>
            <category><![CDATA[sdk-generation]]></category>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[api-integration]]></category>
            <dc:creator><![CDATA[Adeel Ali]]></dc:creator>
            <pubDate>Fri, 02 Dec 2022 18:14:16 GMT</pubDate>
            <atom:updated>2022-12-08T11:43:30.257Z</atom:updated>
            <content:encoded><![CDATA[<p>Xero! The success story you can’t miss if you’ve started up a company in New Zealand in the past decade. Besides getting inspiration, in the first month of APIMatic, we found ourselves using Xero for accounting, receiving advice from an engineering lead at Xero, and using Xero API to test and improve the output of our code-generator.</p><p>Years later, I met Sidney Maestre — the brains behind SDKs for Xero API — at a cafe in San Francisco, and I immediately knew that getting Sid onboard would be among the best things that could ever happen to APIMatic. Thankfully, Sid found the alignment too, and soon after we officially welcomed Sid to the APIMatic family.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_afLYqNnRGx4rzqp" /></figure><h3>Pre-built Code for Simplified API Consumption</h3><p>We know APIs and API-driven software integration for quite some time. However, the next wave of API-first companies is shaping up an exciting phase of the API ecosystem known as <a href="https://gisford.medium.com/the-third-party-api-economy-891b2a774fa5">the third-party API economy</a>.</p><blockquote>The best API companies are those that take a problem that is core to their customers’ businesses yet isn’t their core competency and provides a simple and cheaper solution …</blockquote><blockquote>developers shouldn’t need to build out a whole new payment system if their business is to sell sneakers, instead they should use <a href="https://stripe.com/">Stripe</a>, a company solely focused on building the best software for merchants to accept payments online — <a href="https://medium.com/u/c916b7af535a">Josh Nussbaum</a></blockquote><p>Some of these API-first companies such as <a href="https://stripe.com/">Stripe</a>, <a href="https://twilio.com/">Twilio</a>, <a href="https://www.algolia.com/">Algolia</a> and <a href="https://www.contentful.com/">Contentful</a> have even attained a unicorn status, thanks to their massive adoption among developers. A close look at these unicorns reveals a clear synergy among their developer experience strategies especially the API on-boarding process: they all provide <strong>pre-built code in the form of SDKs and Code Samples</strong> in a variety of programming languages. To learn more, watch this talk on-boarding practices of the fastest-growing APIs:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F30aVCbgihuU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D30aVCbgihuU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F30aVCbgihuU%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/0c902f033dff9e965257160d673afced/href">https://medium.com/media/0c902f033dff9e965257160d673afced/href</a></iframe><h3>What Makes Sid’s Arrival So Special?</h3><p>What makes me super excited about Sid is his years of experience in building SDKs at scale for multiple API companies. Sid not only understands the pain of manual API consumption from the <a href="https://www.apimatic.io/blog/2021/10/dx-of-sdks-vs-direct-api-calls/">consumer’s perspective</a> but he also realizes an API provider’s frustration of <a href="https://www.apimatic.io/blog/2021/09/the-great-sdk-battle-build-vs-buy/">manually maintaining SDKs</a>. Such wealth of knowledge is vital for APIMatic’s mission of productizing the SDK experience, especially for the APIs constituting the 3rd party API economy.</p><h3>APIMatic Mission: Productizing The Proven SDK Success</h3><p>The massive developer adoption of the API-first unicorns is a clear indication of the effectiveness of SDKs. However, that does not come without a significant cost of maintaining SDKs. For the perspective, let’s put on the shoes of an API provider and imagine:</p><ul><li>building SDKs for an API in multiple programming languages</li><li>keeping them in-sync with every new version of the language,</li><li>updating the codebase for ever-changing dependencies,</li><li>incorporating the latest additions in API specifications,</li><li>testing the code with every iteration, and</li><li>writing documentation for everything</li></ul><h4>The Devil is in the Maintenance</h4><p>Notice that in the above list, every step is a continuous process besides the first step of building SDKs. Some API owners mistakenly consider this as a one-time investment, and either try using an open source generator in-house, or outsource the generation of SDKs and code samples as a one-off project.</p><p>On the other hand, for a continuously-maintained SDK project, you would need a dedicated team consisted of developers, QAs and technical writers, either in house or as outside contractors. This HR cost is non trivial, and the manual process is non scalable.</p><h4>Code Generation As A Service</h4><p>The SDK maintenance problem propelled us towards the mission of helping API vendors via a code-generation SaaS solution. Productizing the SDK generation not only eliminates the maintenance hassle, but also allow users to keep <a href="https://www.apimatic.io/videos/docs-as-code-apimatic/">API docs as code</a>, generate test cases, publish packages and much more, right along with the API updates.</p><p>Probably the biggest hurdle in this mission is the status-quo of the manual API consumption/integration practices. Enterprises, in particular, outsource the integration projects to software houses which take months to manually integrate APIs. This status-quo is fuelled by a lack of trust on the quality of machine-generated code and the associated cost of maintaining it.</p><p>With Sid joining the crew, we’re looking forward to educate API providers with faster API onboarding and adoption strategies. The goal is to challenge the status-quo by creating awareness on two fronts: a process of generating SDKs — which is scalable, and effectiveness of the generated code — that really works!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdc80fc364c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apimatic/welcome-sid-to-team-apimatic-cdc80fc364c7">Welcome Sid to the Mission of Simplifying API Consumption</a> was originally published in <a href="https://medium.com/apimatic">APIMATIC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developer Experience Beyond API Docs]]></title>
            <link>https://medium.com/apimatic/introducing-portals-that-speak-your-devs-language-bac82a8c573f?source=rss-8e67d090603d------2</link>
            <guid isPermaLink="false">https://medium.com/p/bac82a8c573f</guid>
            <category><![CDATA[api-documentation]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[code-samples]]></category>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[sdk]]></category>
            <dc:creator><![CDATA[Adeel Ali]]></dc:creator>
            <pubDate>Tue, 30 Jan 2018 13:45:02 GMT</pubDate>
            <atom:updated>2020-12-16T02:59:24.176Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DqDR8CtrlY_H0hYt9LAI7A.png" /></figure><blockquote><em>If you talk to a man in a language he understands, that goes to his head. If you talk to him in his language, that goes to his heart — Nelson Mandela</em></blockquote><p>May I ask you to name a few APIs with a phenomenal developer experience? I have asked this question many times, and the answer was hardly any different. There is a reason why <a href="https://www.twilio.com/docs/libraries">Twilio</a>, <a href="http://algolia.com/doc/api-client/csharp/getting-started">Algolia</a>, <a href="https://stripe.com/docs/api/python">Stripe</a> etc. are loved and accessed by millions of developers. While the majority of API portals are limited to HTTP Docs and API reference, you’ll find the best ones taking the developer experience way beyond that. They do so by:</p><ol><li>Freeing up their developers from redundant tasks, i.e., provide SDKs/Helper libraries, tutorials, code samples, test cases and other features to make API consumption very simple.</li><li>Speaking the language of their developers, i.e., they keep everything from simple How-Tos to intricate SDKs in languages their developers love to code in.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uaLklt0-g6L31Xy68GFIYA.png" /><figcaption>The Common Developer Experience Ingredients Found Among APIs</figcaption></figure><p>However, providing a great experience and serving a variety of developer communities is easier said than done. API owners typically need a team of language experts, technical writers and software testers to begin with. Still, the time to market after every API update and keeping things in-sync take ages. A reason that great API portals are still rare to find. We, at APIMatic believe that this problem can be solved by maintaining a machine readable description of an API, and let automation taking care of the rest.</p><blockquote><em>One of the biggest killers of productivity is redundancy. By performing the same task multiple times, you are not only wasting time, but you are also undermining creativity and ingenuity - </em><a href="http://www.strategicofficesupport.com/reduce-redundancy/">Kathrine Farris</a></blockquote><h3>Enhancing Developer Experience via Automation</h3><blockquote>Automation works on a simple principle — keep humans focused on what’s creative, and delegate to machines what’s redundant.</blockquote><p>APIMatic mission is no different — using automation to delegate the redundant work to machines, we want developers to solely focus on what’s unique and creative. APIMatic’s<a href="https://apimatic.io/code-generation-as-a-service"> Code Generation As A Service</a> has been a great <a href="https://blog.apimatic.io/automate-all-the-things-how-dude-solutions-saved-20-000-in-development-costs-using-apimatic-f9c05118f041">success</a> for continuously integrating internal APIs. Today we’re taking our mission to the next level by <a href="https://apimatic.io/developer-experience-portal"><strong><em>introducing API portals</em></strong></a> that are automatically generated using an API description. Not only the HTTP docs, but also with features-packed SDKs, language specific docs &amp; tutorials, reactive code snippets, test cases and API transformations. These components — by taking care of repetitive problems — can become a dev’s best friend, as you&#39;ll find in a <a href="http://www.creativebloq.com/web-design/apis-developers-need-know-121518469">compilation of 15 great APIs</a>:</p><blockquote>These and other APIs will help you supercharge your abilities. With repetitive problems taken care of, you’ll be free to focus on the part of your job that only you can perform — Adam DuVander</blockquote><h3>What’s Different From Other Docs Solutions?</h3><p>There exist <a href="https://nordicapis.com/ultimate-guide-to-30-api-documentation-solutions/">over 30 solutions</a> to document your APIs, so why create a new one? The answer lies in the fact that the existing portal solutions are great in providing generic content with attractive themes, but the generated portals are not as comprehensive as listed in the table above. More importantly, the developer-engagement content (such as SDKs, Code Samples) is either missing, or requires manual efforts (imagine documenting the authentication flows for the developers of +10 languages). Thanks to the code-generation engine of APIMatic, we are able to offer a distinct and customisable solution which covers both generic and developer specific content. The notable components of the portal are the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P9eqlQHMW_-0RxfgyV3F3A.png" /></figure><ol><li><strong>SDKs for a variety of platforms:</strong> Developers love SDKs / Client Libraries — simply because SDKs lift heavy burden of communication with an API, and let developers focus on app design and business logic.</li><li><strong>API Console</strong>: Try out the API right from the docs using your input.</li><li><strong>Reactive Code Samples</strong>: The quickest way to the first hello world. Get a complete running sample code in your language containing no dummy or static content. <a href="https://docs.apimatic.io/developer-experience-portal/api-console/">Learn More</a>.</li><li><strong>HTTP &amp; Language Specific Docs:</strong> API reference in HTTP and web/mobile languages to take your API to all major developer communities.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEa8ivH2mXPUbMTD-Q5h1Q.png" /></figure><p><strong>5. Custom Sections/Guides:</strong> Help your audience by adding custom sections or guides to your portal.</p><p><strong>6. API Export in over 15 formats:</strong> Transform your API description in a format of your choice. Benefit from a wide range of tools available associated with any format, not just one.</p><p><strong>7. Deploy on Github, or Publish Packages:</strong> Don&#39;t want to download SDKs and compile by yourself? You may deploy the code at Github, or <a href="https://docs.apimatic.io/developer-experience-portal/Adding%20Packages%20to%20Portal/">publish compiled packages</a> at respective language repositories.</p><p><strong>8. Tailored Tutorials</strong>: No more manual technical writing and static/outdated screenshots for your API docs.</p><p><strong>9. Usage Instructions in major IDEs: </strong>Make your developers feel at home by providing everything in their favorite development environment. All major IDEs are supported.</p><h3>Host New, or Embed in Your Existing Portal</h3><p>From the portal design to hosting and white-labeling, we cover everything. However, you might have invested a lot of efforts in your current API portal, and love its design and content. The good news is that you can retain all of your hard work, and still enhance the developer experience of your portal via <em>embeddable DX</em> components. <a href="https://docs.apimatic.io/developer-experience-portal/embedding-your-portal/">Learn More</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dT7UQ04FoeOkh2rItokGPw.png" /><figcaption>The DX components being embedded into an existing portal</figcaption></figure><h3>The best of 2 &amp; 3 Column Designs</h3><p>The trendy 3-column portal designs are great to depict code separately to the text, while the classic 2-column ones are good to document guides and general content. We&#39;re bringing the best of both in a single portal. <a href="https://apimatic.io/api-docs/cgaas-api">Have a look by yourself</a>.</p><h3>An API to Continuously Update Your Portals</h3><p>API changes are inevitable, but reflecting those changes to your published portal is typically a nightmare. A reason <a href="https://apimatic.io/apidocs/dx-portal-api">we’ve built an API</a> to help you integrate the portal generation within your CI/CD pipeline. Now make API changes as often as you like, and get a refreshed portal ready, instantly. <a href="https://apimatic.io/apidocs/dx-portal-api">Learn More</a>.</p><h3>Customize The Way You Want</h3><p>Initially, a portal is generated with default settings, but there are two types of options to let you customize almost everything the way you want. The first type is about changing the design and appearance of the portal, while the second type deals with changing the code-generation settings using an advanced API editor.</p><h3>That&#39;s It</h3><p>Please give the <a href="https://apimatic.io/developer-experience-portal">Developer Experience Portal</a> a try, and let’s know about your experience. We’re all ears for your valuable feedback and suggestions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FwQx-wF3znOg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DwQx-wF3znOg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FwQx-wF3znOg%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/67b885d1fe50aa0e0116e7788bc5c3e7/href">https://medium.com/media/67b885d1fe50aa0e0116e7788bc5c3e7/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bac82a8c573f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apimatic/introducing-portals-that-speak-your-devs-language-bac82a8c573f">Developer Experience Beyond API Docs</a> was originally published in <a href="https://medium.com/apimatic">APIMATIC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[APIMatic Turns 3; Announcing Support of OAS 3.0]]></title>
            <link>https://medium.com/apimatic/apimatic-turns-3-announcing-support-of-oas-3-0-ac27a0e164bd?source=rss-8e67d090603d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac27a0e164bd</guid>
            <category><![CDATA[success-story]]></category>
            <category><![CDATA[apimatic]]></category>
            <category><![CDATA[api-transformer]]></category>
            <dc:creator><![CDATA[Adeel Ali]]></dc:creator>
            <pubDate>Thu, 04 May 2017 12:57:35 GMT</pubDate>
            <atom:updated>2017-07-10T06:54:23.893Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*zQvay45s17EUODiR0AhC2w.jpeg" /></figure><p>This week marks APIMatic’s 3rd anniversary. The year #3 was a special one, as we expanded our presence to 3 countries across 3 continents of the world. We now manage 3 domains: <a href="https://apimatic.io/">APIMatic.io</a> (a top-quality client code &amp; docs generator for APIs), <a href="https://apimatic.io/transformer">APITransformer.com</a> (a converter that covers the highest number of API formats), and <a href="https://sdks.io/">SDKs.io</a> (the largest SDKs repo for public APIs). Today, we’re going to make our 3rd anniversary more special by announcing the support of the well-anticipated API description format: OpenAPI Specification 3.0.</p><h3>OAS 3.0 — Why should we care?</h3><p>In the absence of a standard like WSDL, the web API community have come up with numerous varieties to describe APIs. Among those formats, Swagger, RAML (by Mulesoft) and API Blueprint (by Apiary) are the widely adopted ones. In late 2015, Swagger was renamed as OpenAPI Specification and became part of the<a href="https://www.openapis.org/"> Open API Initiative</a>, which is backed up by the likes of Google, IBM, Atlassian and many others. The OAI is currently focused on creating a vendor neutral API description format which is named as<a href="https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/3.0.md"> OpenAPI Specification 3.0</a>. With Apiary and Mulesoft also joining the initiative recently, OAS 3.0 is anticipated to be the prime choice to describe APIs in the coming future.</p><h3>What’s in it for you?</h3><p>By adding the support of OAS 3.0, APIMatic has opened up a whole world of possibilities. Let’s discuss a few probable use cases:</p><h4>Getting the Best of Every Vendor</h4><p>You keep your APIs in OAS 3.0, but also want to use a tool that is compatible with only RAML 1.0 or API Blueprint. You can do that by temporarily converting your API on-the-fly via the <a href="https://docs.apimatic.io/">Transformer API</a>. Our friends at Postman took this to another level, as now their customers are able to store their favourite Postman Collections in multiple API formats at Github. Check the story out in their own words: <a href="http://blog.getpostman.com/2017/02/15/new-postman-pro-integration-apimatics-api-transformer/">Why We Became Big Believers in APIMatic’s API Transformer</a></p><h4>Developerless Developer Experience</h4><p>You’ve designed the best API of the world, and have also described it using OAS 3.0. So far so good! Now your API is going to meet developers. Are you prepared for that? Do you have time and resources to provide a developer experience that maximises developer adoption? Do you speak all the languages of your developers? APIMatic can sort this out for you. Just import your OAS 3.0 to our <a href="https://apimatic.io/developerless-api-portal">developerless API portal</a>, and witness the magic of automation.</p><h4>Unlocking Old SOA</h4><p>Your decade old enterprise system contains hundreds of thousands of legacy WSDL files. Now you want to adopt a new micro-services architecture based on OAS 3.0, but the idea of porting all those WSDLs to OAS 3.0 gives you nightmare. No worries! APITransformer.com can do it for you in a matter of few hours.</p><h4>What’s Next?</h4><p>We’ve been closely following the development around OAS 3.0. At the time of writing, the latest version is 3.0.0-RC1, which is supported across APIMatic product line. OAS 3.0 is coming up with some <a href="http://apievangelist.com/2017/03/23/api-definition-open-api-specification-300rc0/">exciting new features</a> such as multiple hosts, other response codes, linking and examples. APIMatic’s code-gen engine already supports some of them such as <a href="https://apimatic.io/blog/post/improved-sd-ks-with-timeouts-multiple-base-uri-support-and-custom-exception-classes">multiple hosts</a>, while some others are being added to our product roadmap.</p><p>Stay tuned for more updates, and don’t forget tweeting @apimatic a cool birthday wish :-)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac27a0e164bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apimatic/apimatic-turns-3-announcing-support-of-oas-3-0-ac27a0e164bd">APIMatic Turns 3; Announcing Support of OAS 3.0</a> was originally published in <a href="https://medium.com/apimatic">APIMATIC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving Developers Success with APIMATIC SDKs for Mashery APIs]]></title>
            <link>https://medium.com/apimatic/improving-developers-success-with-apimatic-sdks-for-mashery-apis-958cade00786?source=rss-8e67d090603d------2</link>
            <guid isPermaLink="false">https://medium.com/p/958cade00786</guid>
            <category><![CDATA[code-generation]]></category>
            <category><![CDATA[mashery]]></category>
            <category><![CDATA[apimatic]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[apimatic-partners]]></category>
            <dc:creator><![CDATA[Adeel Ali]]></dc:creator>
            <pubDate>Mon, 06 Jul 2015 00:00:08 GMT</pubDate>
            <atom:updated>2017-07-10T06:54:24.852Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x4v6DawjNEfeSf-r5LYZkQ.png" /></figure><p>Do you know what developers hate the most? They don’t hate working for 12 hours a day; they don’t even hate working over weekends. What they really hate is working on non-challenging and monotonous tasks.</p><p>A classic example is maintaining SDKs or client libraries for an API, which typically happens every time a provider updates their APIs. On the API provider side, maintaining an SDK or a client library is not just time consuming, but it’s also a monotonous task. On the consumption side, a developer would much rather focus on business logic and design of an app instead of trying to figure out how to communicate with an API — especially during hackathons where every second matters.</p><h3>The solution? <a href="https://apimatic.io/">APIMATIC.io</a></h3><p>APIMATIC generates SDKs for APIs automatically in all major programming languages so that developers can consume APIs in their favourite development environment with less code, in less time, with less effort, and with more fun.</p><h3>Mashery + APIMATIC</h3><p>Mashery offers one of the best developer engagement programs in the API space. Reaching out directly to developers at over a hundred hackathons every year is really impressive, and that’s why a large number of API providers trust Mashery to showcase their APIs to the world.</p><p>APIMATIC has <a href="https://sdks.io/Search/FindSDKS?Bridge=Mashery">collaborated with Mashery</a> to provide SDKs/client libraries for Mashery powered RESTful APIs — ranging from Beats Music, Edmunds.com and many more. Automatically generated client libraries are available for iOS, Android, Javascript, Python, Ruby, PHP, Java, Go and .NET.</p><p>The idea is to make developers more productive by supplying SDKs in their favourite programming languages in addition to interactive documentation and other tools around <a href="http://dev.mashery.com/">Mashery’s I/O Docs</a>, all in a single place. This will make it easier for developers to use and adopt Mashery APIs.</p><p>Initial integration was successfully tested at a <a href="http://content.developer.mashery.com/newsletter/04-2015/index.html">developers’ event</a> with <a href="http://developer.edmunds.com/">Edmunds</a> Dealer and Vehicle APIs.</p><h3>Painless SDK Maintenance — A Relief for API Providers</h3><p>This integration mainly answers the <a href="http://trafficandweather.io/posts/2013/10/20/episode-18-this-will-be-way-easier">criticism </a>on SDKs that they are expensive to build and painful to update/maintain. Since the SDKs are automatically generated from <a href="http://dev.mashery.com/">I/O Docs</a> there’s not a single line of code required to build and maintain the SDKs. The only requirement is to keep the API description up-to-date and leave the rest on APIMATIC’s crawler.</p><h3>SDKs for Developers — The Way They Want!</h3><p>Developers love having control over the code they’re working on. That’s why APIMATIC gives them options to tweak the code they’re going to generate. From minor things such as prefixes and postfixes, to major stuff such as dynamic parameters and asynchronous code, developers have control over all aspects. The code generation settings can be accessed by exporting any API to APIMATIC. Exporting an API also enables the developers to add request and response models (schema types) layer in the SDKs, which are currently not available in default ioDocs documents.</p><p>To conclude, supplementing the Mashery repository of APIs with high quality SDKs would probably be a win-win for Mashery customers, their internal developers, and 3rd party consumers. API providers will get much faster and economical access to more developer communities while application developers will enjoy the huge reduction in workload that could allow them to focus on other challenging and important stuff, and/or spend more time with their loved ones. After all, we all love developers :)</p><p><em>This blog post originally appeared on </em><a href="http://www.mashery.com/blog/improving-developers-success-apimatic-sdks-mashery-apis"><em>The Mashery Blog</em></a><em> on May 26, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=958cade00786" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apimatic/improving-developers-success-with-apimatic-sdks-for-mashery-apis-958cade00786">Improving Developers Success with APIMATIC SDKs for Mashery APIs</a> was originally published in <a href="https://medium.com/apimatic">APIMATIC</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>