API Case Studies, Success Stories
Wednesday, October 27, 2021
Gartner predicts that by 2025, more than 80% of organisations identify themselves to have implemented advanced or expert level API strategies. Surely, APIs are not just technical services or programs anymore. APIs that are conceptualised and managed end to end as a product can do wonders for the business. In this talk, Sreeram Narayan will take cues from running a successful API platform program for managing over 450+ Open APIs for an enterprise fintech solution and also take a look at the key strategies that can be counted as best practices in defining, developing and scaling the next generation API experience that can unlock digital revenue opportunities for business. You will learn about how to productize the API development program across multi dimensional and cross functional teams, prioritisation lessons for API roadmap, taking right decisions on open source and API tools, API monetisation techniques and using rich APIs as the sales enabler for your community.
In this session we will see how to assign a phone number to a chatbot created using Dialogflow, Google Cloud Platform, Node.Js and the Vonage API integrations. The architecture shown will allow the user to call your agent by phone with a user experience similar or equal to that possible via the web.You can use Dialogflow and Google Cloud Platform for many reasons, we can create interactions to be used within your own communities, may it be a conversational application for families, companies, sports; to help workflows for both customers and businesses. Sometimes it can be a bad thing to talk to an automated conversation, if it is not well-designed.These pieces of technology can also help you escalate the conversation to a real human, as it can help you detect when human intervention is needed by using the ability of sentiment analysis, leveraging both sides of AI and Machine Learning in one computer-human interaction platform!
The good news is you've built an amazing API for your customers and partners, but the bad news is that's the easy part. The hard part is getting them to actually use the API, ensure they are successful, and create advocates to tell others about how incredible your platform is. So how do you go about building a vibrant ecosystem of developers around your API? Where do you invest? Do you hire a Developer Relations team? A Developer Marketing team? Technical Writers? Sponsor a million events? And how do you manage budget and expectations to ensure long term success??? In this session we'll take a look at some of the most successful communities, how they've become successful, and how you too can build a vibrant developer ecosystem without breaking the bank.
Thursday, October 28, 2021
Standing up an API on the internet is straightforward – many tools and services exist to bring up a functional endpoint. The picture gets more complicated, however, as scope inevitably begins to creep. Sooner or later, every service provider has to consider requirements such as routing requests to multiple backend services, rate-limiting to protect the service from badly-behaved API clients, and consolidating cross-cutting functions such as authentication. Not only that, but, as clients adopt its API, and usage increases, the service provider must avoid becoming a victim of its own success, and collapsing under the load. In building a cloud platform to host and administer services such as Citrix Workspace and Citrix Virtual Apps & Desktops, the Citrix Developer Ecosystem team implemented an API Gateway, providing third-party developers with a secure, uniform interface to a range of backend services. In this session, Director of Developer Evangelism Pat Patterson will share the lessons that the Developer Ecosystem team learned as it built the API Gateway. Pat will explain how the team selected tools for the gateway, created an authentication service to provide a consistent experience to API consumers, and worked with product teams inside Citrix to onboard their services.
In today’s data-driven era, enterprise businesses use more data than ever before, and yet most companies are stuck behind the eight ball using monolithic on-premise databases. Enterprise companies often still store customer data on-premises, requiring them to build out data teams to handle the complex extract, transform, and load processes behind people data, putting their most sensitive data at risk of breach and limiting their ability to tap into third-party data sources. Forward-looking enterprise-scale companies are moving toward pushing their data to other tools and services through the use of APIs, enjoying the advantages of offloading the complexities of loading, de-duplicated, and enriching data; without the risk of security failures or the headache of data storage. In this session, we will outline the shifting world of MarTech, highlight the way in which APIs increase consumer privacy, and discuss specific case studies that highlight the value of moving to off-prem in terms of cost, efficiency, and security.Takeaways:•How APIs help offload and simplify sensitive customer data storage•How APIs increase consumer privacy through anonymization •Discover tools and best practices for moving beyond on-premises databases •Discuss how modern data companies are helping build a “source of truth” for customer data
Over the past two years at SAS, we've concentrated on growing our API program. Open source developers and data scientists have increased their adoption and usage of our APIs. Our microservice APIs serve specific, sometimes low-level functions. We realized we needed to provide aggregated APIs to cover more complex use cases. We formed a cross-departmental collaborative team, identified common scenarios, and created code packages in covering various open source languages for analytics, modeling, job execution, etc., and placed them on GitHub. This presentation outlines our process, from how we identified uses cases, to forming the team, to creating the standards for our GitHub template repository. I'll also discuss our release and marketing strategies to promote the repository and soliciting contributions from users.