“#APIs can boost business because it prepares you for digital ecosystems” - @KoenAdolfs. If you would like to know… https://t.co/Y9l5IGI37w
This talk was presented at API The Docs Virtual 2022 event series on 9 November. We are glad to present the video recording, slide deck and talk summary below. Enjoy!
Visit the talk listing page for an overview of all presentations!
Developer Advocate at Superface
The most expensive part of API integrations isn’t coding or figuring out how to connect the SDK, it’s the analysis: understanding how the API works and how to use it. In this presentation, Jan talks about APIs from the developers’ perspective, how developers perceive the API, and what API providers can do to help them.
To solve their problem. Developers will use the API to fulfill a use case for their application. A use case is a scenario where the API is useful to implement some part or feature in the developer’s application.
The developer is building a registration system (including login, sign up, and password reset). They need to send a password reset email with a link for the user, so they need to look up some email API providers.
As a developer, Jan is trying to match his use case with some features of the API, its capabilities, and what the API can offer.
The developer wants to know how their open source project is doing, they want to know who gives a star to their project. Although the metric of popularity on both is stars, the two have different concepts (GitHub has “repositories” and “stargazers”; GitLab has “projects” and “starrers”). They also both offer REST and GraphQL APIs, so the developer has to decide which one to use to translate their use case to API calls.
Developers have to do a lot of mapping when integrating an API.
Because they can’t understand it.
Typically, the API documentation includes references of end points, data models, product tutorials or even an API specification. These are all great to understand the capabilities of the API, they can serve as a map, they give the developer an idea where they can go with the API but it’s up to them to find their way around.
Solutions and guides, explaining use cases can act as a sort of turn-by-turn navigation. If the API provider also gives the developer a use case tutorial, that would be like giving them a vehicle to get faster towards their goal.
“#APIs can boost business because it prepares you for digital ecosystems” - @KoenAdolfs. If you would like to know… https://t.co/Y9l5IGI37w
What should be the purpose of your #APIprogram? When does it become successful? Stay tuned because the new podcast… https://t.co/Z1GmsLUnA5
RT @APItheDocs: 🥁 Early-bird tickets are available for #APItheDocs #Amsterdam🥁 Save your spot and register for the 2-day conferenc… https://t.co/rFieLnreop
🥁We're launching a new #podcast series🥁 @kvantomme interviews guests from leading #API teams to explore a more hol… https://t.co/CT7UUXAxFc
They airdropped me $GPT WTH @wild_trent @SADA @Bitathon1 @SolarBrad14 @sainathyarra @pronovix @LFlecchia @luqmaansu… https://t.co/R5TSa9RGf2