It Is Difficult To Know Where To Begin With APIs

It Is Difficult To Know Where To Begin With APIs

The API landscape is huge. APIs are being used to power desktop, web, mobile, and device applications across almost every business sector. While there are many common patterns used across the leading APIs, APIs still come in many shapes and sizes, making it difficult to know where to begin when first learning about APIs. This isn’t an exclusive situation with people who are just learning about APIs, it is the state of things for most people working with APIs on a regular basis. No matter how experienced you are with APIs, there is always some new approach emerging, and some evolution in how things are done that might just be out of view. Leaving us all struggling to keep up, stay aware of latest trends, while perpetually working master what we already know, always refining our approach to getting things done with APIs.

Adding to the mix of complexities to articulate about the world of APIs, there are many different capacities in which you can engage with APIs. Opening up a handful of opportunities for developers, and non-developer individuals to roll up their sleeves and get involved. Many discussions around APIs will center on being an API provider, someone is making APIs available, or you are an API consumer, and you are putting APIs to work. The consumption of APIs is where most people start, but then learning about developing and operating APIs also dominates the conversation because of the commercial opportunity that has evolved over the last decade, making it a popular place to begin. Additionally, there are a handful of other doors we like to open when it comes to introducing people to APIs

Focusing Just On Consuming APIs

Using an API is the easiest place to begin when beginning your API journey. You are more likely to find your way forward with APIs if you get started with a single API provider, or category of APIs that align with interests you already have, helping connect your desire to learn more about APIs with things that already drive you. One of the biggest challenges with helping the API curious navigate this layer of the web, is that there are so many APIs out there. Putting the responsibility on each API curious individual to pick a handful of topics that interest them. Sit down at their favorite search engine, type in each of these words, appending the acronym API before hitting submit. Continuing your quest for knowledge about how APIs can be put to work in your daily workflow.

  • Discover New APIs - Search for APIs online using keywords and phrases that are relevant to you will introduce you to a whole new world of how data, content, media, and other resources are made available in the layer of the web that interests you. Search, and explore the results of your API searches, then bookmark the APIs that look interesting to you. Don’t stop with just a handful of APIs, explore many different keywords, breaking out your thesaurus to help expand your vocabulary, while also expanding your API horizon.
  • Play With APIs - As you are learning about the APIs you’ve discovered, go ahead and sign up for an account, obtain API keys, and play around with the APIs. Even if you don’t know what you are doing, you will learn a lot along the way. Most APIs do not have limitations about who can sign up for APIs, and anyone can make an API call using client solutions like Postman, no coding necessary.
  • Build With APIs - If you have the ability to write code, or are fearless enough to begin playing around, hacking, and learning to code, you can begin building something on top of an API. Most APIs provide you with code snippets, software development kits (SDKs), and starter applications, providing you with the basics of learning how to build something useful on top of an API. Even if you do not intend on delivering an actual application, there is nothing stopping you from learning how it all works.
  • Help Improve APIs - Most API providers are looking for feedback on their creations, and are grateful when developers play around with, build things, and provide feedback on how easy, or hard the APIs are to use, and what other APIs might be interesting to offer. Entire communities have emerge around individual APIs, and APIs in general, producing a wealth of knowledge out there when it comes to putting APIs to work, offering an opportunity for hobbyists all the way up to professionals to get involved.

Using other people’s APIs is the best gateway to the world of APIs. The best API providers, are also API consumers, and having an awareness of how popular APIs like Twitter, Twilio, Stripe, and others work is an asset. If you want to learn more about APIs, always start with just playing with APIs that already exist. There are endless API lessons available out there, all you have to is seek them out, and work to discover and play with new APIs—repeating on a regular basis. Learning the best patterns, as well as the mistakes made by interesting APIs you probably are already using on the web, or on your mobile phone. Expanding your awareness of how APIs are used, while also cultivating and stimulating your own interests all along the way.

Learning To Integrate Using APIs

Going one step further with your knowledge of APIs, and kicking the tires when it comes to consuming APIs, you can invest more time understanding how developers, SaaS providers, and other API savvy folks are connecting services, applications, and platforms together, taking advantage of API integration opportunities that exist. This doorway to the world of APIs presents another opportunity for developers and non-developer individuals to not just learn about APIs, but put them to work automating the syncing, triggering, and accomplish a variety of integration tasks using the services, applications, and platforms they already depend on.

  • Discover New APIs - Software as a Service (SaaS) provider integration pages, and next generation integration platform as a services (iPaaS) provide a rich opportunity discovering new APIs, ready to go with low-code or no-code integration capabilities. Once you begin to look for integration pages for SaaS providers you will see them everywhere. Opening up a whole new dimension of API-driven capabilities that have always been with reach of both developers and non-developers, but were just out of view.
  • Platforms - With the number of APIs emerging over the last ten years an entire ecosystem of low-code and no-code solutions have emerged to connect the dots between existing API-enabled services. All of these services are well within reach of the average developer, and even non-developers. Opening up a wealth of API-driven capabilities assoociated with the applications, services, and platforms we already depend on.
  • Workflow Orchestration - SaaS and iPaaS integrations go well beyond simple API reference based opportunities, and tend to reflect more meaningful workflows for common everyday business tasks. Using one or more APIs to accomplish a specific objective, using the services we are already using—all we have to do is authentication, and connect the dots in our worlds.
  • Knowing What Is Possible - Those who are familiar with SaaS and iPaaS integrations, and regularly employ them to accomplish tasks tend to be more aware and in command of what is possible with the applications, services, and platforms they depend on. Showing how APIs can empower individuals to get things done, augment the tools and services they already use with additional capabilities, and establish more control over their digital presence.

API integration opportunities are everywhere once you begin to scratch the surface. You do not need to be a coder to become proficient at navigating the world of APIs, and putting them to work. SaaS and iPaaS integrations are being used to average business users to orchestrate data, content, and media across the web. Some API curious individuals might end their journey here, finding everything they need to know about APIs by walking through the API consumer and integration doors. Being able to not just understand what APIs and what they are used for, but actually be able to put them to work. Making APIs the critic tool in our business toolboxes, allowing us to be in control of our own data, then dictate and execute the business workflows enable us to be more success in our daily work.

Being a Steward Of Open Data With APIs

One step beyond just being an API consumer and integrator, moving towards the world of providing APIs, many data stewards are realizing the benefit of publishing their spreadsheets as simple APIs, allowing them to be access by many different consumers, and used in a variety of applications. While also allowing data stewards to maintain a level of control and quality over their data, ensuring they remain the source of truth when it comes to the source of the valuable data we use in applications, visualizations, and even additional API powered spreadsheets. Software as a Service (SaaS) providers have opened up a new realm of services and tooling to help data stewards better manage their data in the could, complete with a suite of tools for helping publish data as simple, intuitive web APIs.

  • Spreadsheets - Microsoft Excel and Google Sheets both have APIs to expose data within spreadsheets, and they both have the ability to make calls to existing APIs to populate data within spreadsheets from APIs. Making APIs the preferred way of data stewards when it comes to opening up access to data, using the tools they already depend on to get the job done.
  • CSV & JSON - Beyond the spreadsheet there are numerous tools for helping data stewards convert and export spreadsheets into CSV and JSON formats, providing the preferred data format for publishing APIs. Allowing stewards to quickly publish spreadsheets as machine readable data, which is the most simplest form of an API out there—no expensive infrastructure needed.
  • Publish Data APIs - Most API management providers have solutions for turning your spreadsheets, CSV, and JSON files into APIs, quickly publishing data as an API that can be properly secured, managed, measured, and made available to a controlled audience. Leveraging APIs to make data more accessible and usable across many different applications, while allowing data stewards to stick with the tools they know best—the spreadsheet.
  • Maintain Quality - API consumers can just take data from an API and use within their applications, or they seamless integrate the API directly into their application, allowing data to be updated whenever the data within he API is updated. It is common to limit the terms of service for data APIs to limit how data can be stored and cached, requiring consumers to treat the data API as as source of truth, giving data stewards much more control over how it is used.

APIs and data are synonymous. Most APIs are just about providing access to data within databases, or within spreadsheets. APIs help reduce the number of times in which a spreadsheet are emailed around or duplicated. APIs provide centralized access to the data within a spreadsheet, allowing it to quickly be used in visualizations, and other ways of displaying information across web and mobile applications. APIs open up opportunities for data stewards go provide wider access to dat with more control over what is done with it, and even potentially opening up additional revenue opportunities through commercial access, and the development of new products and services around the data being provided.

Becoming A More Capable API Provider

Once you have your footing in the world of APIs, how they are consumed and integrated within applications, you can begin to explore the opportunities around becoming an API provider eternally within your organization, externally with partners, or eventually by making an API publicly available to 3rd party developers. Providing APIs requires a much higher level of understanding around how to do APIs, but there are plenty of opportunities for business stakeholders to get involved in the process, especially when it comes to defining, designing, developing, and publishing modern APIs, which provide more areas for non-technical folks to contribute, without having to have the deep technical experience required to actually deliver the API itself. Providing a handful of places anyone can get involved in moving the API deployment conversation forward at their organization.

  • Know Your APIs - The place to start within any organization when it comes to APIs is know what APIs are currently available for consumption inside or outside the firewall. Every company, organization, institution, and government agency has APIs—they just might not be actively deploying and supporting them. Most modern software and open source tooling have APIs, which should be included in the list of your API capabilities. Beyond these starting points, if your organization does deploy and support APIs, spend the time to get to know them, understand what they do, and what the process is to deliver them-know your organization APIs.
  • Know Your Teams - Next, understand the teams behind the APIs being developed, and if your organization isn’t formally delivering APIs, then explore and find out the APIs that different groups are putting to use in their applications and system integrations. Understand the capacity for knowing about and using APIs across different teams, and spend the time to map out the strengths, weaknesses, assets, and liabilities that exist across the teams you have to support an API conversation.
  • Know Your Stakeholders - Beyond teams providing and consuming APIs, spend the time to identify other potential stakeholders in the API conversation. Who will make decision around what software gets used, which application get developed, and the integrations that get tackled, or maybe are in most need of being done. Have a good understanding of the technical and business stakeholders that exist who can help, or hurt the API conversation at your organization.
  • Know Your Applications - Beyond the APIs themselves, understand what applications are operating which depend on APIs If applications are being developed on top of the APIs your organization develops, spend the time to understand how they are used, and what metrics are in place to better understand their API dependencies.
  • Know Your Capabilities - Understand where the API resources are, but also develop a strong understanding of ho those APIs can be put to work in common workflows that benefit your business, and empower your teams. Know the capabilities of your organization, and develop your understanding of what capabilities will be required to get your organization where you want it to be. APIs are the key to understanding what your organization is or isn’t capable of today, and tomorrow.
  • Define Your Lifecycle - Cultivate your awareness of how APIs are defined, designed, developed, documented, tested, and supported in production. Document the life cycle of the existing APIs in operation, understand more about how they came to be, and what it takes to keep them alive. Work with team members and other stakeholders to standardize the definition you establish of your API lifecycle, then work to share with as many other individuals as you possibly can, repeating as necessary to get desired results.

There are many ways to define, design, deliver, support, and integrate an API without writing code. Most of the steps in this process are within reach of business users. Many developers are unaware of modern approaches to delivering APIs within large enterprise organizations, leaving a pretty large vacuum for technical or business leadership to step in and guide the process. Helping teams become more capable API developers and providers, helping them refine their skills and participate in a much more streamline API lifecycle. Establishing a repeatable series of steps that everyone has agreed upon to help deliver APIs from start to finish, repeating as necessary, standardizing and optimizing how APIs are delivered across an organization, turning it into a shared effort between business and IT, or development groups—leveraging what you have learned about APIs to ensure healthier outcomes for your organization, and the teams that work there.

Stepping Up To Evangelize APIs

The final doorway we will welcome you in when it comes to learning about what is next for your API journey is all about stepping up to help evangelize APIs within your organization, or possibly the industry you operate in. API evangelists, advocates, and champions are needed within every company and team. Passionate individuals who understand the API opportunity that exists, as well as those who are willing to wrestle with the challenges are desperately needed across almost any industry. Passionate evangelists who are obsessively curious and passionate about connecting people within an organization or industry are one of the most sought after resources in the space today. Representing a pretty significant opportunity when it comes to apply the API knowledge you have, while also investing in it, by stepping up to be and API advocate.

  • Discover New APIs - Take the time to find new, interesting, and useful APIs that your organization and customers can put to use. Be vocal about the process, and what you find. Share the stories of what APIs exist, how they are being used, and being applied to solve real business problems. Be the go to person within your organization for knowing where the best APIs exist, and who across your organization and industry is doing the most interesting things with APIs.
  • Play With APIs - Be API literate. Play with APIs, understand how they work, and how they don’t. Be an advocate for API consumers, while also being an advocate for API providers. Understand what it takes to put an API to work, and be the person who develops the most meaningful integrations and workflows with the APIs that already exist.
  • Tell Stories of APIs - Tell endless stories about what you are learning about APIs. Write blog posts, tutorials, white papers, and share you story in any meeting, meetup, or conference you can think will matter. Be the API storyteller who is shining a light on what matters, helping your organization, teams, and customers be more successful.
  • Shine A Light On People - Don’t make your evangelism about you, make it about the interesting things other people are doing with APIs. Listen to other stakeholders, team members, and consumers. Keep notes on what is being worked on, and think about the most positive ways in which you can share information, push for collaboration, and encourage reuse of quality work you find across your organization and API community.
  • Develop Relationships - About 35% of your evangelism work will be about the technical details of APIs, the rest of your work will be about developing relationships with different groups, teams, partners, and individuals. Work overtime to develop relationships the individuals who matter the most, and will have the most positive impact on the API conversation, acknowledging that some relationships will be more difficult than others.

Evangelism, advocacy, and the championing of APIs within an organization can make or break the effectiveness they have on operations. It doesn’t matter how good the technical details are for how you deliver APIs, if you don’t address the human side of things, it will fall apart. Technology is comfortable with us operating within silos, business is not so accommodating. Doing business online in a global business climate requires everyone working in concert, and when teams exist in different buildings and geographic locations, investing heavily in evangelism, advocacy, and collaboration is essential. Always requiring a passionate champion who’s job is to simply connect people, tell stories, and strengthen relationships, which will help keep the API gears turning and always moving forward towards a common goal.

APIs Aren’t Just For Developers

It has been said several times so far—APIs aren’t just for developers. This is a legacy way of thinking that has been pushed out of companies who have made progress in their digital transformations. We’ve clearly identified several ways in which APIs can be put to work by non-developers, and that modern approaches to integrating services, applications, and platforms with APIs can be deployed and managed entirely without the assistance of a developer. While there are technical pitfalls that still exist across the API landscape which will ensure business stakeholders, there are increasingly services, tooling, connectors, and plugins to help bridge the gap—all you ave to do is spend the time looking for the right API-enabled solution. We can’t emphasize enough that APIs are for everyone. We see APIs like the banking system, you don’t have to have full knowledge of how it works, but you should be able to manage your finances, know who has access to your accounts, then be able to connect and integrate the various services you spend on. Which by the way, is all API enabled—demonstrating another way in which APIs will help you further master the orchestration of not just your professional world, but your personal life as well.

APIs Help Build Our Awareness

Most large organizations do not possess an awareness of where all of their digital assets live, and what their organizations are capable of on any given day. APIs help quantify these resources and capabilities, and if done right, provide us with a way to define, document, share, collaborate, and integrate using these digital resources. Inviting more people to the discussion, making API an organizational wide affair, helps develop awareness of what is possible. It helps break down the walls that exist between organizations, and externally with our partners and customers. APIs help us standardize how we provide access to data, content, media, and our most valuable algorithms. A modern API lifecycle is how streamline the design, development, and delivery of our organizational capabilities, injecting more agility, flexibility, and efficiency into how we deliver API infrastructure, but also open up access to them and develop desktop, web, mobile, device, and network applications on top of this infrastructure. The health of our APIs depend on developing this awareness, making this quest you are on to understand more about APIs, and where you should be starting one of the more critical things you should be doing today.

APIs Give You A Stronger Voice

Equipped with an awareness of what your organization is capable of, and what the process is to add to that arsenal, you will develop a much strong voice when it comes to contributing to the direction your organization is headed. The more you understand about how applications are developed across your organization, and how the APIs behind these applications and other integrations are brought to life and evolved, the more tables you will have a seat at. Understanding not just how APIs are developed within your organization, but also how they are consumed and integrated with will give you a command over the landscape that will transcend your traditional organizational boundaries. What you know about APIs is applicable across groups, and will be valuable in making a bigger impact in the business sectors you operate. You will have access to the resources and capabilities of your organization, but also access to the most relevant data, content, and media from 3rd party APIs that exist behind the applications, services, and platforms you’ chose specifically because they hav eAPIs—leveraging APIs to shift the balance of power within your organization, and amongst your customers when it comes to them realizing what you are capable of.

APIs Equip You With New Capabilities

Your API journey will lead you towards a new future will you will be much more confident about what you currently possess, what you will need to equip your organization for the future, and how you will deliver the next generation of capabilities that are need to get you where you want to be. Each API represents a valuable resource your organization possesses, and when orchestrated alongside other resources, you begin to establish processes and workflows that shift how work gets done. In the last couple of years more mainstream businesses are waking up to how much they depend on APIs to get business done today, while also demonstrating the importance of APIs to what they will be able to accomplish in the next decade. Realizing that if they don’t go all in on investing in their API capabilities today, that they won’t be able to keep up and deliver new capabilities fast enough, crippling their overall ability to innovate and compete as the business world continues to march forward as part of this wider digital evolution.

Image Credit: "starting here - numbering" by atibens is licensed under CC BY-NC-ND 2.0

Owen Rubel - API EXPERT

Original Amazon team (95-98) / Creator of API Chaining(R)

5 年

Not really. You can always use a framework like BeAPI (https://beapi.io) that handles oauth, webhooks, batching, rate limiting, caching, api doc creation and more.?https://www.youtube.com/watch?v=tzuNczkedhw

回复

要查看或添加评论,请登录

社区洞察

其他会员也浏览了