Your API is So 2006 - Dreamforce 2011

Sep 8, 2011Download as PPTX, PDF6 likes1,004 views

Don't expect internal, partner, and open developers to build 2011 apps and integrations with 2006 API formats, chatty protocols and outputs. PuSH! RESTful! JSON! oh my.

Your API is So 2006Delyn Simons@delynator, @mashery#df11August 2011

7Accelerating Growth of APIsTotal APIs over timeBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

Who are developers?What do they want?How can you help them get what they want?

Developers are 21st century craftsmenPhoto Credit: flickr.com/tom_w_bn

Developers build stuffPhoto Credit: flickr.com/mashery

Developers solve problemsPhoto Credit:flickr.com/delynator

Developers tinker and prototype Photo Credit: flickr.com/techcrunch

Developers rely on tools to practice their tradePhoto Credit: © Eric Roth

Who are developers?What do they want?How can I help them get what they want?

Tools and terms of service they can rely onPhoto Credit: © Eric Roth

API Integration Pain SurveySurvey conducted by YourTrove, Inc. August 2011

Results Chart by ProgrammableWeb. Survey conducted by YourTrove, Inc. August 2011

Treat your API like a core part of your business“It’s not what we set out to find, but it deserves to be said again: API providers are doing a horrible job of serving their developers well. This is a huge problem.”Survey conducted by YourTrove, Inc. August 2011

Modern API management trendsPlease Drop the SOAPChat Less, Do MoreInteractive DocumentationGrowing of internal and partner API usageMainstream API Success

REST vs. SOAP: Simplicity wins again32Distribution of API protocols and stylesBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

33REST vs. SOAP: Simplicity winsDistribution of API protocols and stylesBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

JSON Rising: 55% of new APIs support JSON34Percentage of new APIs with JSON supportBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

20% of new APIs support only JSON35Percentage of new APIs with only JSON supportBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

1 in every 5 new APIs: “goodbye XML”36Percentage of APIs with XML supportBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

Chat Less, Do More with Push Notifications

Mashery I/O DocsInteractive DocumentationAll methods and parameters clearly displayed

Ability to make live API calls within documentation

API call, HTTP header and response displayed

Useful for exploring, learning, testing and debugging

Restructuring for Internal, Partner Growth

This document discusses the growth of APIs since 2006 and trends in their development and use. It notes that the number of APIs listed on ProgrammableWeb has grown significantly since 2006. REST has become the dominant API design pattern over SOAP, and JSON support is rising dramatically. The document advocates that API providers think like platforms by dropping SOAP, using push notifications to engage developers, providing interactive documentation, and focusing on internal and partner usage to achieve mainstream success.

Proxying api callsVisuality

This document discusses using a gateway app to proxy API calls from multiple providers and stabilize an application. It notes problems with some providers having unstable or undocumented APIs. The proposed solution is to create a gateway app that standardizes API calls to different providers, increasing stability while decoupling the application from external databases and inconsistent APIs. Pros include increased stability and consistency, while a con is a more complex architecture. It suggests using this approach when integrations are unstable, interface like APIs, or when multiple providers offer the same service.

Postman Webinar: "API Governance with Postman"Postman

State of the API: Insights Into the Future of APIsPostman

The document discusses the state of APIs based on a survey of over 13,500 API professionals. It finds that while developers make up over half of API professionals, non-developers are also significant users. The top obstacles to producing and consuming APIs are lack of time for production and lack of documentation for consumption. The future of APIs is predicted to include continued investment and focus on microservices and serverless architectures.

Common Security API Issues and How to Mitigate Them Using PostmanPostman

KPIs for APIs (and how API Calls are the new Web Hits, and you may be measuri...John Musser

How do you measure API success? What KPIs do APIs need? What mistakes should I avoid? Find out what you should, and shouldn't, be measuring as part of your API program in this Business of APIs Conference NYC talk. Dive into a breadth of API metrics, the 6 keys to better API metrics, and the traps to beware of (the important do's and don'ts). Also real-world API case studies show who measures what.

API Security with Postman and QualysPostman

This document discusses API security testing with Postman and Qualys. It notes that APIs are widely used but often built without security in mind. It highlights some of the top API security risks from the OWASP API Security Top 10, including broken object level authorization, broken user authentication, and broken function level authorization. The document then outlines Qualys' web application scanning capabilities for APIs and how it can utilize existing Postman collections to quickly scan APIs for vulnerabilities. It concludes by emphasizing the importance of API security and recommending the OWASP API Security Top 10 as a resource.

Ten Reasons Developers Hate Your APIJohn Musser

APIs are everywhere today and can be a great building block of modern applications. But all too often APIs are not truly great. Rather than love your API, developers curse it. How can you avoid that fate? In this session we'll look at the most common mistakes API providers make and you can avoid making them too. Do you offer a bad developer experience (DX)? Poor, inconsistent API design? Unreliable services? This talk is a deep dive on not just what to avoid but what to do instead. And you'll leave knowing how to get developers to love your API, not hate it.

What's an apiJacques Ledoux

Postman Public Workspaces: The First Massively Multiplayer API Experience | W...Postman

Postman Platform Overview: Be API-First, Not API-LastPostman

This document discusses the concept of API-first development versus API-last development. API-first refers to designing an API before developing the applications or front-end interfaces that will use the API. This allows the API to drive development and ensures the API is properly designed, documented and supports the needs of both internal and external developers from the beginning. The document suggests that leading technology companies now follow an API-first approach and provides resources for learning more about implementing API-first practices.

Postman for EnterprisesPostman

This document provides an overview of Postman's enterprise capabilities from Sanjeev Sisodiya, VP of Customer Success at Postman. It discusses how Postman can accelerate key business processes by providing a developer experience platform, ensuring API quality, security and governance. It highlights some of Postman's enterprise customers and describes how the combined capabilities around developer productivity, quality, security and governance form Postman's API platform. The document encourages attendees to reach out if their organization could benefit from an enterprise API platform.

Why You Need a Developer Relations Team for Your APIPostman

Developer Relations teams focus on three key areas: 1) improving the developer experience through SDKs, documentation, demo apps and support, 2) building a developer community through events, conferences and an online community, and 3) collecting feedback across multiple channels to understand developers and improve the API. Having a DevRel team leads to a happier developer community, easier onboarding, more successful customers, and making the API a leader in its market.

API as a Growth Tool3scale

Api typesSarah Maddox

This document classifies and describes different types of APIs. It discusses web service APIs like REST and SOAP, library-based APIs that interface with programming languages like JavaScript, class-based APIs for platforms like Java and Android, OS APIs that allow access to system functions and hardware, and object remoting APIs like CORBA. Examples are provided for many API types. The document is intended to provide an overview of the various ways that software applications can communicate through defined programming interfaces.

Search and Discovery With Public and Private API NetworksPostman

Sapna Nayak discusses how Postman provides both public and private API networks. The public API network allows developers to discover and connect with APIs from various developers and organizations. It acts as a map or directory. The private API network allows teams to share important internal APIs, provide discovery within the organization, and details on how to use APIs. Both networks allow connecting APIs in Postman workspaces. Search is also introduced to help find APIs across Postman collections.

Enterprise ecommerce-webinar 1Postman

10 things you didn't know about PostmanPostman

The document outlines 10 things to know about Postman, an API development tool. It lists features like running API calls easily with an HTTP client, visualizing response data, debugging with the console, intercepting cookies, controlling code generation, testing APIs, integrating with continuous deployment, collaborating with teams, maintaining API specifications, and publishing APIs. The document encourages providing feedback to help improve Postman.

API design principles for accelerated developmentJonathan LeBlanc

Audio from this presentation is available at https://archive.org/details/api_design One of the largest issues in API architecture development is that the task is often driven by the pragmatic indoctrination of a specification into a product rather than designing around the speed and ease of development, usually due to a separation between the engineering teams and their core developer user base. Extending upon the ideas of API design around developer accelerated development, we will take a deeper look into some of the great techniques delivered to us through the RESTful specification, applying them to developer API consumption practices with the intention of creating efficient best practices for rapid development. Within this talk we will explore what we have learned through reconstructing our API backbone at PayPal for our developer community, including: - API automation practices for code reduction and application longevity - Open security standards that promote developer integration ease and maintain strict security practices - RESTful API architecture best practices for developer centric accelerated development

Enterprise E-commerce Webinar Series, Episode 2: Deploying and Monitoring You...Kin Lane

Note: This webinar is the second in Postman's three-part webinar series on implementing an API-first strategy in enterprise e-commerce. The series, hosted by Postman Chief Evangelist Kin Lane, will walk you through key topics and how-to content via a hypothetical e-commerce enterprise, Union Fashion (see it on GitHub). Continuing with our series, the second webinar will dive into actually deploying and monitoring an API using the Postman platform. We will take the API we developed as part of our previous API-first webinar, and actually bring it to life by focusing on the following areas: - Versions - Monitors - Mocks - Environment - Documentation - Feedback Loops The full video for this session can be found at: https://www.youtube.com/watch?v=jO2M_kqb-jo&t=1659s

Clickslide Datadipity Beta V1Gabriel Ortiz

Sign up for our beta today! http://datadipity.com/register Datadipity reduces time to launch by promoting the “Virtualized API stack” with a set of APIs in place, there is no need to architect complex distributed systems. 3rd party APIs are leveraged so that the architecture can be reduced to one code base. This reduces development time. Usability is much easier to maintain during beta release and user acceptance changes are easier to apply.

Postman Visualizer Webinar SlidesPostman

Postman Visualizer lets you render a custom view of the data returned from your APIs. You can turn complex API responses into beautiful, interactive visualizations, right within the Postman app. These can then be easily shared with collaborators via Postman collections. In this webinar, you will learn how to: - Import a Visualizer template - Map your data to a graph or chart - Create and share Visualizer templates

APIs explained for product managersRichard Holmes

Distributed Systems Development on the API Powered Web3scale

This document discusses how software development is increasingly moving to a distributed systems model where web APIs allow software components to be distributed across networks and accessed remotely. It notes that while this provides more powerful and flexible development, it also introduces new complexities compared to traditional standalone software. The talk recommends adopting a "distributed by default" mindset and practices like failure tolerance, discovery frameworks, and standardized service descriptions to help developers navigate these challenges.

Postman Galaxy Tour - Keynote PresentationPostman

This document discusses the rise of APIs and the Postman platform. It notes that APIs are now essential due to trends like mobile and cloud computing. Postman started in 2012 to help with API testing and has since grown significantly, with over 500,000 organizations using it. The document outlines Postman's platform services for API lifecycle management, collaboration, and runtime functionality. It also previews many new features and highlights Postman's continued focus on the API-first approach.

POST/CON 2019 Workshop: Design, Develop, and Mock APIs with PostmanPostman

Learn how to collaboratively plan and design APIs to establish a single source of truth for your API lifecycle. This workshop will focus on building Collections to represent APIs from the point of view of both producers and consumers of an API. We will show how you can use API schemas (OpenAPI/RAML/GraphQL) in Postman, manage versions of collections, and document them. We will also deep-dive into Mock Servers, and show how you can use them in your development.

API Best Practices Webinar: Metrics - What to MeasureApigee | Google Cloud

Api testingvcubesoftsolutions

API TESTING:Application programming interface (API) testing is a sort of software testing that involves testing APIs both directly and as part of integration testing to verify if they fulfil functionality, reliability, performance, and security expectations. API testing is done at the message layer since APIs lack a graphical user interface. The API is directly related to their functionality, performance, and security.

SVPMA API Panel | April 2013Delyn Simons

TwilioCon 2013 API Panel with Capital One, ESPN, Accenture, MasheryDelyn Simons

More Related Content

What's hot (20)

What's an apiJacques Ledoux

Postman Public Workspaces: The First Massively Multiplayer API Experience | W...Postman

Postman Platform Overview: Be API-First, Not API-LastPostman

Postman for EnterprisesPostman

Why You Need a Developer Relations Team for Your APIPostman

API as a Growth Tool3scale

Api typesSarah Maddox

Search and Discovery With Public and Private API NetworksPostman

Enterprise ecommerce-webinar 1Postman

10 things you didn't know about PostmanPostman

API design principles for accelerated developmentJonathan LeBlanc

Enterprise E-commerce Webinar Series, Episode 2: Deploying and Monitoring You...Kin Lane

Clickslide Datadipity Beta V1Gabriel Ortiz

Postman Visualizer Webinar SlidesPostman

APIs explained for product managersRichard Holmes

Distributed Systems Development on the API Powered Web3scale

Postman Galaxy Tour - Keynote PresentationPostman

POST/CON 2019 Workshop: Design, Develop, and Mock APIs with PostmanPostman

API Best Practices Webinar: Metrics - What to MeasureApigee | Google Cloud

Api testingvcubesoftsolutions

What's an apiJacques Ledoux

Postman Public Workspaces: The First Massively Multiplayer API Experience | W...Postman

Postman Platform Overview: Be API-First, Not API-LastPostman

Postman for EnterprisesPostman

Why You Need a Developer Relations Team for Your APIPostman

API as a Growth Tool3scale

Api typesSarah Maddox

Search and Discovery With Public and Private API NetworksPostman

Enterprise ecommerce-webinar 1Postman

10 things you didn't know about PostmanPostman

API design principles for accelerated developmentJonathan LeBlanc

Enterprise E-commerce Webinar Series, Episode 2: Deploying and Monitoring You...Kin Lane

Clickslide Datadipity Beta V1Gabriel Ortiz

Postman Visualizer Webinar SlidesPostman

APIs explained for product managersRichard Holmes

Distributed Systems Development on the API Powered Web3scale

Postman Galaxy Tour - Keynote PresentationPostman

POST/CON 2019 Workshop: Design, Develop, and Mock APIs with PostmanPostman

API Best Practices Webinar: Metrics - What to MeasureApigee | Google Cloud

Api testingvcubesoftsolutions

Viewers also liked (6)

SVPMA API Panel | April 2013Delyn Simons

TwilioCon 2013 API Panel with Capital One, ESPN, Accenture, MasheryDelyn Simons

Discussing Software through the art of the Hong Kong Umbrella MovementAarhus University

Transforming Products into PlatformsDelyn Simons

Manage your Public API Like a ProtocolDelyn Simons

As the number of public APIs available to developers skyrockets, developers are increasingly asked to evaluate dozens of API providers based on their market opportunity, ease of integration and stability of service - then choose a winner to integrate with. You can quickly communicate that your company is interested in providing opportunity to developers by managing your API like a protocol. Discover why good versioning practices, incorporating developer input, participating in developer meetups and hackathons, and adopting existing standards whenever possible makes good business sense for both API developers and API providers.

Hicheel 4 angi Eb Ganaa

SVPMA API Panel | April 2013Delyn Simons

TwilioCon 2013 API Panel with Capital One, ESPN, Accenture, MasheryDelyn Simons

Discussing Software through the art of the Hong Kong Umbrella MovementAarhus University

Transforming Products into PlatformsDelyn Simons

Manage your Public API Like a ProtocolDelyn Simons

Hicheel 4 angi Eb Ganaa

Similar to Your API is So 2006 - Dreamforce 2011 (20)

Open APIs - State of the Market 2011John Musser

This document summarizes key trends in the open API market based on data from ProgrammableWeb.com. It finds that the growth of APIs is accelerating, with over 3,200 APIs currently listed. The most competitive categories have dozens of APIs. It also discusses the rise of simplicity in APIs, with REST and JSON becoming increasingly dominant. Finally, it explores business models for APIs, noting some companies are focusing exclusively on their API as the product rather than accompanying websites.

Open APIs: State of the Market, May 2010John Musser

Open APIs and the Semantic Web 2011John Musser

1. The document discusses the state of the market for open APIs and semantic web technologies. It notes that REST has become the dominant API design approach over SOAP. JSON support is growing and has surpassed XML for new APIs. 2. While there are over 3,300 APIs tracked, semantic API adoption remains low with only 1% of APIs supporting RDF. The growth of invisible APIs and APIs as products is also discussed. 3. Key trends include the rise of APIs as core products and business models, with some companies abandoning websites in favor of monetizing their APIs. Developer ecosystem cultivation and support is also cited as important for API success.

Open API Ecosystem Overview: December 2010John Musser

The document summarizes the state of open APIs in 2010. Some key points include: - Open APIs have grown rapidly in recent years, with over 2,400 APIs listed by 2010 compared to just 105 in 2000. Growth has accelerated. - Successful APIs have a business model baked in, are easy to adopt, and provide good developer support. Common models include pay-per-use, affiliate marketing, and software as a service. - REST has become more popular than SOAP due to its simplicity. JSON is also growing as an alternative to XML. - Major tech companies are increasingly dependent on APIs, with billions of API calls per day powering services like Facebook and Amazon.

API Product Opportunity Responsibility Nicolas Sierro 2015.pptxBlockchainizator

The document discusses the history and evolution of APIs, including early examples from Salesforce, eBay, and Amazon in the late 1990s-early 2000s. It notes that APIs allow companies to unlock the business potential of their data and services by making them available to external developers and partners. Successful API strategies treat the API as a product in its own right, with clear business models, pricing, and onboarding support for developers. The growth of APIs has accelerated in recent years, driven by trends like mobile, cloud computing and the desire to build platforms.

The New API: Apps, Partners and Incomeduvander

The document discusses business models and strategies for APIs. It notes key metrics for several major APIs and their growth over time. It also provides examples of how companies invest in and partner with developers to build APIs into profitable products and platforms that generate revenue through various monetization strategies like ads, affiliate programs, and commerce APIs. The document advocates for APIs to be a company-wide priority and strategy rather than just an engineering initiative.

Business of APIs Conference 2011 - ProgrammableWebMashery

The document discusses the growth and state of the open API market. It notes that the number of APIs has grown exponentially in recent years and is now over 4,000 tracked by ProgrammableWeb. It also discusses the diversity of API types across sectors like ecommerce, travel, music, enterprise, shopping and social. Additionally, it outlines the evolving business models for APIs, noting a shift towards APIs being the product themselves rather than an extension of existing products or websites.

Making an API Developers LoveFrank Denbow

The document discusses how to build APIs that developers love. It emphasizes solving developer pain points by making APIs simple to use with predictable resources and common standards like REST and JSON. It also stresses the importance of thorough documentation with code samples, explorers, and multiple languages, as well as reliable and responsive support from API providers. Examples are given of successful APIs from companies like Netflix, Twitter, Foursquare, Stripe, and Twilio that exemplify these best practices.

API Testing Interview Preparation and MethodsVivekanandaSamantra2

Opening Keynote at BMMP 2011 - OMA API ProgramMusa Unmehopa

Opening keynote presentation at the 3rd workshop on Business Model for Mobile Platforms (BMMP), 7 October 2011. Topic: How Business Model Considerations Impact the Standardization Process. The presentation makes the point that business considerations and market requirements should drive technology standardization. The presentation uses the API Program of the Open Mobile Alliance (OMA) to illustrate these points, and demonstrate how business model considerations impact the standards processes for application programming interfaces. Presentation by Musa Unmehopa, Chairman of the Technical Plenary in OMA, senior manager of standardization at Alcatel-Lucent

Creating killer location-based mobile apps Jean-Luc David

API Trends: What to expect in 2012Apigee | Google Cloud

This document discusses trends in APIs to expect in 2012. It predicts that enterprise APIs will go mainstream, with 30% of enterprises implementing APIs and 60% considering them. It also suggests that APIs will become the default access point for backend systems, and that API-centric architecture will focus on integration with apps and developers rather than people or processes. Additionally, it proposes that data will be brokered through APIs using free and paid models, and that enterprises will enable their data through RESTful APIs.

Understanding REST APIs in 5 Simple StepsTessa Mero

This document summarizes the 5 steps to understanding REST APIs: 1) Understanding the purpose of APIs and their importance and growth, 2) Learning that REST defines functions to communicate via HTTP verbs and nouns, 3) Knowing that APIs use requests and responses, 4) Relying on documentation as the reference, and 5) Using debugging and testing tools to prevent issues. It provides examples of requests, responses, API documentation, and tools like Postman for working with REST APIs.

Kin Lane - Gluecon - Whats Next for APIs?Kin Lane

Kin Lane discusses predictions for the future of APIs in several areas: 1. Modular tools and platforms will emerge for building and deploying APIs as services. 2. Embeddable widgets and plugins will become widespread, making APIs more accessible to non-developers. 3. Developers will gain more control and influence within API ecosystems through organization and social coding. 4. New monetization models like affiliate programs and prepay options will help API providers manage costs and monetize APIs.

Understanding REST APIs in 5 Simple StepsTessa Mero

This document summarizes a presentation on understanding REST APIs in 5 simple steps. It explains that APIs allow software to communicate via HTTP requests and responses, and REST defines using HTTP verbs and nouns to make requests. The steps are: 1) understand the purpose of APIs for developers to benefit users, 2) learn that REST specifies making HTTP requests to perform functions on a server, 3) recognize that requests elicit responses, 4) use documentation as a reference for available verbs and nouns, and 5) leverage debugging and testing tools to prevent issues when working with APIs. The document emphasizes that documentation is key to understanding an API and recommends Postman as a useful GUI testing client.

Maintaining the Netflix Front Door - Presentation at Intuit MeetupDaniel Jacobson

Top 10 Lessons Learned from the Netflix API - OSCON 2014Daniel Jacobson

The document discusses lessons learned from Netflix's API strategy over time. It notes that Netflix started with a focus on growing a community of public developers but now prioritizes ensuring subscribers can stream. It also discusses separating concerns between API providers and consumers, embracing differences in audiences, being pragmatic over dogmatic in API decisions, enabling fast iteration, planning for failures, and scaling infrastructure to match growth.

Business of APIs Conference 2011 - SalesForce.comMashery

The document discusses Salesforce.com's API journey. It notes that Salesforce currently services 500 million requests per day, with 60% (300 million) being API calls. It then outlines Salesforce's strategy to keep APIs simple and flexible while enabling integration, custom application development, and parity with platform features. The document also discusses the historical evolution of Salesforce's APIs from 2001 to present day and the addition of REST APIs to align with modern technologies like HTML5 and mobile platforms. Finally, it covers the Chatter API's shift to returning full object graphs via REST to improve performance over individual object calls.

How to use Donuts and Onions for Scaling API Programs3scale

Why API? - Business of APIs ConferenceDaniel Jacobson

Many API programs get launched without a clear understanding as to WHY the API should exist. Rather, many are focused on WHAT the API consists of and HOW it should be targeted, implemented and leveraged. This presentation focuses on establishing the need for a clear WHY proposition behind the decision. The HOW and then WHAT will follow from that. This presentation also uses the history of the Netflix API to demonstrate the power, utility and importance of knowing WHY you are building an API.

Open APIs - State of the Market 2011John Musser

Open APIs: State of the Market, May 2010John Musser

Open APIs and the Semantic Web 2011John Musser

Open API Ecosystem Overview: December 2010John Musser

API Product Opportunity Responsibility Nicolas Sierro 2015.pptxBlockchainizator

The New API: Apps, Partners and Incomeduvander

Business of APIs Conference 2011 - ProgrammableWebMashery

Making an API Developers LoveFrank Denbow

API Testing Interview Preparation and MethodsVivekanandaSamantra2

Opening Keynote at BMMP 2011 - OMA API ProgramMusa Unmehopa

Creating killer location-based mobile apps Jean-Luc David

API Trends: What to expect in 2012Apigee | Google Cloud

Understanding REST APIs in 5 Simple StepsTessa Mero

Kin Lane - Gluecon - Whats Next for APIs?Kin Lane

Understanding REST APIs in 5 Simple StepsTessa Mero

Maintaining the Netflix Front Door - Presentation at Intuit MeetupDaniel Jacobson

Top 10 Lessons Learned from the Netflix API - OSCON 2014Daniel Jacobson

Business of APIs Conference 2011 - SalesForce.comMashery

How to use Donuts and Onions for Scaling API Programs3scale

Why API? - Business of APIs ConferenceDaniel Jacobson

Recently uploaded (20)

How Can I use the AI Hype in my Business Context?Daniel Lehner

𝙄𝙨 𝘼𝙄 𝙟𝙪𝙨𝙩 𝙝𝙮𝙥𝙚? 𝙊𝙧 𝙞𝙨 𝙞𝙩 𝙩𝙝𝙚 𝙜𝙖𝙢𝙚 𝙘𝙝𝙖𝙣𝙜𝙚𝙧 𝙮𝙤𝙪𝙧 𝙗𝙪𝙨𝙞𝙣𝙚𝙨𝙨 𝙣𝙚𝙚𝙙𝙨? Everyone’s talking about AI but is anyone really using it to create real value? Most companies want to leverage AI. Few know 𝗵𝗼𝘄. ✅ What exactly should you ask to find real AI opportunities? ✅ Which AI techniques actually fit your business? ✅ Is your data even ready for AI? If you’re not sure, you’re not alone. This is a condensed version of the slides I presented at a Linkedin webinar for Tecnovy on 28.04.2025.

Cybersecurity Identity and Access Solutions using Azure ADVICTOR MAESTRE RAMIREZ

What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat

The MCP (Model Context Protocol) is a framework designed to manage context and interaction within complex systems. This SlideShare presentation will provide a detailed overview of the MCP Model, its applications, and how it plays a crucial role in improving communication and decision-making in distributed systems. We will explore the key concepts behind the protocol, including the importance of context, data management, and how this model enhances system adaptability and responsiveness. Ideal for software developers, system architects, and IT professionals, this presentation will offer valuable insights into how the MCP Model can streamline workflows, improve efficiency, and create more intuitive systems for a wide range of use cases.

UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity

Join this UiPath Community Berlin meetup to explore the Orchestrator API, Swagger interface, and the Test Manager API. Learn how to leverage these tools to streamline automation, enhance testing, and integrate more efficiently with UiPath. Perfect for developers, testers, and automation enthusiasts! 📕 Agenda Welcome & Introductions Orchestrator API Overview Exploring the Swagger Interface Test Manager API Highlights Streamlining Automation & Testing with APIs (Demo) Q&A and Open Discussion Perfect for developers, testers, and automation enthusiasts! 👉 Join our UiPath Community Berlin chapter: https://community.uipath.com/berlin/ This session streamed live on April 29, 2025, 18:00 CET. Check out all our upcoming UiPath Community sessions at https://community.uipath.com/events/.

Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan

This is a Quick Research Guide (QRG). QRGs include the following: - A brief, high-level overview of the QRG topic. - A milestone timeline for the QRG topic. - Links to various free online resource materials to provide a deeper dive into the QRG topic. - Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic. QRGs planned for the series: - Artificial Intelligence QRG - Quantum Computing QRG - Big Data Analytics QRG - Spacecraft Guidance, Navigation & Control QRG (coming 2026) - UK Home Computing & The Birth of ARM QRG (coming 2027) Any questions or comments? - Please contact Arthur Morgan at [email protected]. 100% human made.

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

Build Your Own Copilot & Agents For DevsBrian McKeiver

HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda

Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-und-verwaltung-von-multiuser-umgebungen/ HCL Nomad Web wird als die nächste Generation des HCL Notes-Clients gefeiert und bietet zahlreiche Vorteile, wie die Beseitigung des Bedarfs an Paketierung, Verteilung und Installation. Nomad Web-Client-Updates werden “automatisch” im Hintergrund installiert, was den administrativen Aufwand im Vergleich zu traditionellen HCL Notes-Clients erheblich reduziert. Allerdings stellt die Fehlerbehebung in Nomad Web im Vergleich zum Notes-Client einzigartige Herausforderungen dar. Begleiten Sie Christoph und Marc, während sie demonstrieren, wie der Fehlerbehebungsprozess in HCL Nomad Web vereinfacht werden kann, um eine reibungslose und effiziente Benutzererfahrung zu gewährleisten. In diesem Webinar werden wir effektive Strategien zur Diagnose und Lösung häufiger Probleme in HCL Nomad Web untersuchen, einschließlich - Zugriff auf die Konsole - Auffinden und Interpretieren von Protokolldateien - Zugriff auf den Datenordner im Cache des Browsers (unter Verwendung von OPFS) - Verständnis der Unterschiede zwischen Einzel- und Mehrbenutzerszenarien - Nutzung der Client Clocking-Funktion

Splunk Security Update | Public Sector Summit Germany 2025Splunk

Heap, Types of Heap, Insertion and DeletionJaydeep Kale

Manifest Pre-Seed Update | A Humanoid OEM Deeptech In Francechb3

TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc

Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency. This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data. Attendees will learn: - Consumer awareness around data brokers and what consumers are doing to limit data collection - How businesses assess third-party vendors and their consent management operations - Where business preparedness needs improvement - What these trends mean for the future of privacy governance and public trust This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.

Into The Box Conference Keynote Day 1 (ITB2025)Ortus Solutions, Corp

TrsLabs - Fintech Product & Business ConsultingTrs Labs

Hybrid Growth Mandate Model with TrsLabs Strategic Investments, Inorganic Growth, Business Model Pivoting are critical activities that business don't do/change everyday. In cases like this, it may benefit your business to choose a temporary external consultant. An unbiased plan driven by clearcut deliverables, market dynamics and without the influence of your internal office equations empower business leaders to make right choices. Getting things done within a budget within a timeframe is key to Growing Business - No matter whether you are a start-up or a big company Talk to us & Unlock the competitive advantage

Rusty Waters: Elevating Lakehouses Beyond Sparkcarlyakerly1

Spark is a powerhouse for large datasets, but when it comes to smaller data workloads, its overhead can sometimes slow things down. What if you could achieve high performance and efficiency without the need for Spark? At S&P Global Commodity Insights, having a complete view of global energy and commodities markets enables customers to make data-driven decisions with confidence and create long-term, sustainable value. 🌍 Explore delta-rs + CDC and how these open-source innovations power lightweight, high-performance data applications beyond Spark! 🚀

Semantic Cultivators : The Critical Future Role to Enable AIartmondano

tecnologias de las primeras civilizaciones.pdffjgm517

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

At InData Labs, we have been keeping an ear to the ground, looking out for AI-enabled digital transformation trends coming our way in 2025. Our report will provide a look into the technology landscape of the future, including: -Artificial Intelligence Market Overview -Strategies for AI Adoption in 2025 -Anticipated drivers of AI adoption and transformative technologies -Benefits of AI and Big data for your business -Tips on how to prepare your business for innovation -AI and data privacy: Strategies for securing data privacy in AI models, etc. Download your free copy nowand implement the key findings to improve your business.

ThousandEyes Partner Innovation Updates for May 2025ThousandEyes

How Can I use the AI Hype in my Business Context?Daniel Lehner

Cybersecurity Identity and Access Solutions using Azure ADVICTOR MAESTRE RAMIREZ

What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat

UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity

Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

Build Your Own Copilot & Agents For DevsBrian McKeiver

HCL Nomad Web – Best Practices und Verwaltung von Multiuser-Umgebungenpanagenda

Splunk Security Update | Public Sector Summit Germany 2025Splunk

Heap, Types of Heap, Insertion and DeletionJaydeep Kale

Manifest Pre-Seed Update | A Humanoid OEM Deeptech In Francechb3

TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc

Into The Box Conference Keynote Day 1 (ITB2025)Ortus Solutions, Corp

TrsLabs - Fintech Product & Business ConsultingTrs Labs

Rusty Waters: Elevating Lakehouses Beyond Sparkcarlyakerly1

Semantic Cultivators : The Critical Future Role to Enable AIartmondano

tecnologias de las primeras civilizaciones.pdffjgm517

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

ThousandEyes Partner Innovation Updates for May 2025ThousandEyes

Your API is So 2006 - Dreamforce 2011

1. Your API is So 2006Delyn Simons@delynator, @mashery#df11August 2011

4. <you think?>

7. 7Accelerating Growth of APIsTotal APIs over timeBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

8. APIs since 2006

9. “Their API is so 2006.”

10. “Their API is so awesome.”

12. Who are developers?What do they want?How can you help them get what they want?

13. Developers are 21st century craftsmenPhoto Credit: flickr.com/tom_w_bn

15. Developers build stuffPhoto Credit: flickr.com/mashery

16. Developers solve problemsPhoto Credit:flickr.com/delynator

17. Developers tinker and prototype Photo Credit: flickr.com/techcrunch

18. Developers change the game

21. Who are developers?What do they want?How can I help them get what they want?

23. API Integration Pain SurveySurvey conducted by YourTrove, Inc. August 2011

24. Results Chart by ProgrammableWeb. Survey conducted by YourTrove, Inc. August 2011

25. Treat your API like a core part of your business“It’s not what we set out to find, but it deserves to be said again: API providers are doing a horrible job of serving their developers well. This is a huge problem.”Survey conducted by YourTrove, Inc. August 2011

26. Who are developers?What do they want?How can I help them get what they want?

28. “Their API is so 2006.”

29. Modern API management trendsPlease Drop the SOAPChat Less, Do MoreInteractive DocumentationGrowing of internal and partner API usageMainstream API Success

31. Photo Credit:flickr.com/delyn

32. REST vs. SOAP: Simplicity wins again32Distribution of API protocols and stylesBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

33. 33REST vs. SOAP: Simplicity winsDistribution of API protocols and stylesBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

34. JSON Rising: 55% of new APIs support JSON34Percentage of new APIs with JSON supportBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

35. 20% of new APIs support only JSON35Percentage of new APIs with only JSON supportBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

36. 1 in every 5 new APIs: “goodbye XML”36Percentage of APIs with XML supportBased on directory of 3,200 web APIs listed at ProgrammableWeb, May 2011

37. Modern API management trendsPlease Drop the SOAPChat Less, Do MoreInteractive DocumentationGrowing of internal and partner API usageMainstream API Success (upside + downside)

38. Chat Less, Do More with Push Notifications

41. Modern API management trendsPlease Drop the SOAPChat Less, Do MoreInteractive DocumentationGrowing of internal and partner API usageMainstream API Success (upside + downside)

42. Mashery I/O DocsInteractive DocumentationAll methods and parameters clearly displayed

43. Automatic key/credential retrieval

44. Ability to make live API calls within documentation

45. API call, HTTP header and response displayed

46. Useful for exploring, learning, testing and debugging

48. Modern API management trendsPlease Drop the SOAPChat Less, Do MoreInteractive DocumentationGrowing of internal and partner API usageMainstream API Success (upside + downside)

49. Restructuring for Internal, Partner Growth

50. Modern API management trendsPlease Drop the SOAPChat Less, Do MoreInteractive DocumentationGrowing of internal and partner API usageMainstream API Success

51. APIs since 2006

52. Mainstream Success

53. Mainstream Success – Who’s Next?

54. Modern API management trendsPlease Drop the SOAPChat Less, Do MoreInteractive DocumentationGrowing of internal and partner API usageMainstream API Success

55. Thank you!Your feedback is a gift. Delyn Simons@delynator, @mashery#df11August 2011

Editor's Notes

#24: ,,
#43: [ go over bullets ]Sample calls are no longer static pieces of documentation that can get outdated. With live API calls available within the documentation, you are guaranteed never to have non-functional outdated examples.

Your API is So 2006 - Dreamforce 2011

Recommended

More Related Content

What's hot (20)

Viewers also liked (6)

Similar to Your API is So 2006 - Dreamforce 2011 (20)

Recently uploaded (20)

Your API is So 2006 - Dreamforce 2011

Editor's Notes