Transform Your Workflow with InvoiceBus for Product Management

Invoicebus for Product Management

hello everyone and welcome back today we are going to talk about a very important topic known as apis or application programming interfaces so let's go ahead and start the session this is going to be the agenda for today we are first going to introduce you to what API is we are going to talk about what are apis what are some common example of apis and then we'll also talk about what are the use cases of API in any kind of business then we'll talk about uh some details of the apis where we'll talk about what is a request response what is payload and endpoints we'll talk about the status and body and we'll talk about we'll create an API together like a specs of an API together for the LinkedIn API and then we'll talk about API product management as in if you are a product manager what are the responsibilities that you have like a high level overview of responsibilities that you might have as an product manager who is managing an API and then I'll also give you some kind of resources to so you can go ahead and take your learning to the next level so this is going to be the agenda for today let's go ahead and start the session so I'm sure you might have seen these kind of products or apps so the first example is from Uber or you can consider any kind of cab service out there cab aggregator service out there so what happens is that this is the Uber interface where you could see that there is a map and there is also a payment option so you could see that this app is possible because there are certain kind of service or systems working together the in the Uber interface this app is being feted from Google Google Maps while an API such as brain tree API or the PTM API or the stripe API is used for payments so multiple systems are working together to make sure that Uber is able to function similarly if you take any of the banking app or an app such as cred which helps you understand your credit score there you'll understand that cred does not know your credit score the credit score is actually coming from a third party service which is also known as the Civil or cff or experience these are the services which maintain your credit score these are also known as credit bureaus similarly on the third type of very popular application is the booking.com or PMS of the world where you could book flight tickets at one place like you can go ahead and choose any of the flights and you can book it from one place here also all of these flights such as Indigo go a lansa a Asia they have made sure that they are able to integrate with the PTM system so that they are able to get the like get the bookings from the system and also give the status updates to the PTM system so understand here the moral of the story is in order to make sure that the Uber is working various systems have to work together similarly in a fintech app various system has to work together in order to make sure that this functionality is available similarly in any of the booking site or there are so many examples where various system work together in order to make sure that the use case is delivered to you as a user so that is the use case of API okay how do they work together with each other is through an API API is the application programming interface because of which different kind of tech systems are able to work with each other so Google Maps might have given an API to Uber through which they can fetch the Google Map data into their system brain tree stripe or PTM might have given a payment Gateway API to Uber in order to make sure that they a they are able to collect payment across the credit cards and banks of the world similarly booking.com is using the API that is given by different kind of Airlines different kind of hotels to make sure that they are able to go ahead and take the bookings and give the status updates to these kind of original suppliers so this is what API are useful so apis are a way for the tech systems to communicate with each other there has to be a common system through which these people can talk with each other and that is made possible by apis or the application programming interfaces so how are apis useful one use case is very obvious to you that in order to make sure that the complete functionality of the product is there apis are used for example at Uber crad booking.com in order to go ahead and fetch information from different websites or different products you need to use your apis Uber is using Google Maps cred ising using Experian or C or any other credit bureau similarly the the booking.com is using different kind of Airlines website airline apis in order to give you the one seamless experience the Second Use case of API is to communicate with internal systems yeah so in the three tier architecture we have talked about how back end front end and database are working together in a system now if these three also need to work with each other they need to talk with each other they also have to have a standardized F there also apis are used so a back end will give an API to the front end which which it can use in order to go ahead and make sure that data is passed from and across the front end to the back end similarly the Third Kind of use cases there are many businesses such as Google Maps such as Stripes which are actually going ahead and giving their API as a service as a business okay so there are so many examples you could see that Google Map API is available to so many location based services such as Uber such as booking.com such as Airbnb such as SGI such as Ola and so many examples out there so Google is actually making a lot of money from the similarly if you want to buy any stock from zerodha or Robin Hood or ICC director anywhere they should be using some kind of API that is given by the NASDAQ or the National Stock Exchange so that they can go ahead and fetch the data and get whether the trade is possible or not so all of the details are given by for the share market so all the data for the Indian stock market to Zera is given by the National Stock Exchange or the Bombay Stock Exchange apis okay so three use cases of apis first it makes sure that the complete functionality of the product is there then it makes sure that various systems within your product are able to talk with each other such as back end front end and the database and third is you can also go ahead and offer your business all together as an API so that you can go ahead and have some kind of business model based on the same now this is like a elaborated example of the first part which is booking.com is going ahead and they are connecting with Indigo spice Lans and other kind of Airlines and then you as a user are able to see this so so this is the API provider and this is the API consumer similarly for second example you can see that the front end back end are connected to each other through an API so you can take an analogy to a waiter and to a chef and to you as a consumer so you are the consumer who is giving instruction to an API that go ahead and get this information for me or go ahead and store this information for me okay this API is going to go ahead and take the requirements or the instructions from you and they are going to give it to the back end and back end will decide whether they have to go ahead and acknowledge or complete your instructions or not so a very good analy is the is the restaurant example out there and then the third part is API as a business so there are so many businesses which are offering their product as apis so for example WhatsApp business API is is one that is making a lot of wealth through their business API that they have created because so many people use WhatsApp second is stripe stripe is a payment Gateway there are other payment gateways as well which are actually their main business model is the API that they offer so that you do not have to talk if you are a business looking to sell something and if you want to accept money then you do not have to talk to so many banks because people can have different kind of banks accounts out there you can only talk to stripe and stripe will make sure that all the backend Integrations are possible through a simple to used API and then we have algolia algolia is a company which actually offers an API through which you can Implement search on your website out of box search in your website and various websites such as Hacker News and all are actually using algolia API in order to build search on their platform so just to repeat application programming interface or a apis are a way for Tech system to talk with each other Uber can talk to Google because of API your front end can talk to your back end because of an API this is the use case of API now what are the pros and cons of API so pros of API are very simplistic to understand so it reduces the time to ship so imagine a situation when Uber has to go ahead and do all the Imaging of the world and create these kind of maps in order to just build a cap service on the top of it so it is going to be a lot of work so Google Maps have made sure that this solution the map solution is provided to them out of the box they don't have to do anything about the same they just have to pay so it reduces the time to ship that's the first part second part is you get an added functionality without going ahead and committing a lot of money and then standardization is you go ahead and get some kind of standardized principle that yes if someone has to go ahead and talk to your product they have to use these standards it also helps you build internal systems and scalable systems and have sync between your developers because there is standard that you are following okay similarly the cons of who having an API is that it is going to be an cost because now Uber has to pay incrementally to Google when you when they are going ahead and using the Google Map API into their system and it actually was an event that happened in 20178 when Google has suddenly increased their cost of their apis by almost like 4X or 14x I'm not remembering the number but they have increased substantially so that is also like challenge for your that could be a challenge for your business similarly dependency when we are using certain kind of apis in your product you are actually creating dependencies so it happens is that you want to buy something but the payment Gateway is down that business has created the dependency on the payment Gateway so this is going to be there these are some of the cons of apis okay and even because of like this is such a big problem that there are solutions such as just pay which are going ahead and aggregating all of these payment gateways so they will understand which payment Gateway is likely to work which is not down and they are going to suggest you a better Gateway so there is an API which is actually sitting on a lot of apis of payment Gateway so so many things are possible with apis so now let's talk about how an API Works before I go started let me tell you that what I'm telling you is an standardized way the developers can decide how the apis are going to talk with each other but this is one of the standardized ways which is used across the globe okay so now let's go ahead and talk about the same so this is how an API works there are two parties one is the API consumer the person who is going to consume the API the system that is going to consume the API and then there is a second party which is going to providing the API okay so for example if Uber wants to use Google Maps then Google Maps is the API provider who is providing the data and information while Uber is someone who is going ahead and using this particular piece of information similarly if we talk about booking.com then booking.com is a person who is actually consuming the API while Indigo and lansa and Air India are people who are going ahead and giving their API providing the API to IND to this particular company booking.com so how does it work so there is going to be an API consumer who consumes the API there is going to be an API provider who is going to provide the API and they are going to talk to each other talk to each other in order to exchange information in order to build up a use case so a API consumer has to send a request that I want this okay so a request would contains an endpoint as in this is the location through which the API response would be generated second is type so you can do four things in an API either you can go ahead and create some data to yeah the second type is yeah the second component of an API is the type so you can do four things in an API you can either add data you can addit data you can delete data or you can fetch some data okay so these four things are possible and for that we have four terms so an API can either post which is used for adding the data to the API get could be it is used to fetch some data from the API it is put if you want to added some data to the API and then if it is deleted that means you want to remove some data from the API provider so these are the four types of calls that API that an API can make then we have header authorization so understand an API might contain some additional information that will help the API provider to understand if this request is coming from the right place or not for example if I'm trying to edit my profile on LinkedIn or if I'm I trying to go ahead and book a seat for myself on IRCTC website then the IRCTC website or the the LinkedIn should know that if it is the correct user who is allowed to make make these changes or make a booking or not okay and for that they need to identify and that is why we have header which contains additional information to make sure that the right person is being authorized to do this particular action and then in the end we have payload data so in order to make your request more contextual you have to send some kind of data for example if you want to added information what is the information that you want to add it if you're looking to get some information what is the information that you want to get if you want to put some information on the API then what is the kind of information that you are putting if you want to delete something what is it that you want to delete all of this information would be contained in the payload or the data so this is how the request works so this information this request will be sent to the API provider the API provider based on whatever the use case is they are going to run some algorithm do some kind of data changes and give the response back to the API consumer understand API consumer does not need to be aware of what the API provider is doing at the back end that is none of their concern the API provider has to take care of of all of this and API consumer is only taking care of what is the data that they need in return so request has been sent for this particular thing now the API provider will generate a response for the API consumer so the response might contain the status which is whether your request was successful or there was some kind of error or there was some kind of issue and then there is going to be a Content or message as in yes you have asked for this data and this is the data that you have got if it is an error they will throw an error message if the request is successful they will generate you give you some kind of data that you have asked for so this is how this is structured to give you a bit more detail so this is a terminology that is related to apis I have talked about endpoints request and response endpoint is the place where the API has been hosted so that you can you know that yes this is where the real code or the real provider of the API is then we have the request the request that is sent by the API consumer to the API provider then we have the response that based on the request whatever is the response generated by the API provider is going to be sent to the API consumer then the request might contain the type as in if it is a post request then it is going to add a resource if it is a put request then it is going to edit a resource if it's a delete request then it is going to delete a resource and then if it's a get request it is going to get a resource then there are headers they are used to make sure that the right kind of person is going ahead and accessing the same and also if there is any additional information that has to be sent with each and every request that would be contained in the headers and then we have a payload so payload is the data that has been sent along with the request so it could be in the form of Json or XML in the initial session I have already told you what Json or JavaScript object notation is and talking about the response so the response also contains two parts first is a header okay so the header will contain status status is what is the status of your response what is the status of your response so it will have four things so every time a status request is going to start from a particular number it could be 200 200 134 and all and it could also start from 5 4 and three okay so if it starts with two that means that your request has been successful and this is the data that you have if it is an error that is starting from five that means that there is some error at the server maybe they are not able to connect with the database maybe this kind of information is not available on the database or maybe it could be possible that at this point of time API is not available you might have seen that when you try to go ahead and look at a website that is having a lot of load it is going to show you some kind of 500 or 5001 error out there okay okay similarly 4xx 4xx error such as 400 4001 4003 4004 error is occurring when the client itself has sent the wrong kind of uh request for example the request does not contain right kind of authorization headers or the resources that you are asking for is not available for example when you go ahead and type a mistype URL or if you type a wrong URL in your Chrome browser it is going to tell you that there is a 44 error which means that your request was wrong this URL does not exist on the server okay so that is the fourxx error and then there is 3xx error which is 30 30 1 302 these kind of errors are used when the resource that you are asking for has been displaced to some other resource so initially yes this resource was there but now this API has became older so now you should go ahead and go to the new API or go to the go to the new resource in order to get this information so these are the four kind of status messages that the API can throw at API provider can throw at the API consumer in its response now there is body so based on whatever information that you are asking if you're asking for maybe Google Maps then it will give you a map sheet if you're asking for a credit score then it will give you the credit score if you're asking for maybe how much is the availability of seats in your Airlines and it can give you the required kind of data okay so that is all content in body body could be in the form of Json XML or any of the data that has been communicated that has been uh decided among the API provider and the consumer now we'll go ahead and try to create LinkedIn API okay so we'll only consider four use cases we'll first talk about if someone signs up on LinkedIn what are the possible apis that are called then we'll talk about edit profile if someone wants to go ahead and edit their profile on LinkedIn what is going to happen at the API if I want to see all of my friend requests or connection requests out there what is the kind of API that is being built over there then we'll talk about create post and delete post okay so this is going to be a very simplistic exercise so that you understand how API creators are thinking out there now the first thing is create user okay so you know that whenever you want to go ahead and create an account on LinkedIn this is the form you have to fill okay so you have to fill your first name last name email and password okay so this is how it is going to look from the Viewpoint of an API okay so this API would be provided by the back end okay and the front end will have to make sure that they are calling this API so here the front end would be the API consumer while the back end would be the API provider okay so this API would be provided by the back end out there okay so this is going to be the information so endpoint would be we have just taken an example endpoint this is not correct LinkedIn could have choosen any endpoint that they want okay okay so here the API endpoint is api. linkedin.com creatore user okay this is the URL that the API is resting at after this there has to be a payload as then I have to make sure that I'm able to give LinkedIn what is the data has to be added so I put in my name Anish Shukla and I have put in the email ID over there understand this information will be fed from this particular form okay so this is the payload and then there has to be a method method is post because I'm going ahead and adding some data to LinkedIn okay and then I'll send this request to the uh to the LinkedIn API and once the LinkedIn API has got this information it will understand first that whether this information is for a new user or not if it is not for a new user it is going to throw an error that no this user already exist you should go ahead and tell them to login if it is a new user exactly a new user then it will go ahead and enter this in the database but from the API it will only send a response that yes 200 this request has been successful and now this is the new user ID of the person so this is how the create user API is going to work on LinkedIn so you need need endpoint payload and Method and then you need body and Status okay now the second part Second Use case is edit profile if I want to edit my profile on L I'll go ahead and go to edit profile on section and then I can go ahead and change my name and all of these information out there what is going to happen over there from an API let us understand so here the endpoint could be different maybe the endpoint is added underscore user this is going to be an URL then there has to be a header understand everyone should only be able to go ahead and edit their own profile not anyone else's that is why you need some kind of authentication code that is generated uniquely for that particular user okay so that when this information is being sent to the API API should be able to understand if this is the right user or not after this there will be a payload as in in the payload I'll mention whatever is the name change that I have done okay and then my user id will also be there user ID is important so that I know for which user I have to go ahead and change this information and this user ID should at least match with this authentication code that yes the user ID that is being sent to me is actually authorized to go ahead and do this in do this particular change and then the method would be put the method is put because we are editing a resource so there are four methods post put delete and get so here we are using put which is used to edit some information now this information will go to this request will go to the API and API will generate a response okay it will go ahead and say that name now new name is anit Kumar Shukla and now the status is 200 so I've just gone ahead and changed my name from anit Shukla to anit Kumar Shukla on LinkedIn and this is how the API is working at the back end after this let us consider one more case I want to show all connection request from LinkedIn okay whatever I I should go my network and I should be able to see all of the connection requests that are out there okay so in order to get this information what I will do I will create this kind of API okay so whenever I go ahead and go onto that page this kind of API is being called so what is happening here so in order to make this API of show connection all connection request this is going to be the request so in the request there is an endpoint okay so the endpoint would be this like we have just taken an simple endpoint which is connection _ R which should be there on the LinkedIn server and then authorization authorization is important over here because I should be able to see only my connection request and everyone's connection request is going to be different so identification is very important after this the payload the payload would contain the user for which I'm looking for the connection request and also the count am I looking for five connection request 10 connection request 20 connection request there has to be there will be a default number but you can also send a count over there similarly the method is going to be get I am just getting some information I not editing or adding any kind or delete any kind of information so the method is going to be get then the response would be so what will happen over here is that the API will get this information it will get the user ID then it will search in the database who are the people who have gone ahead and recently sent this person a connection request it will go ahead from the database it will fetch all of the IDS profile pictures and account links for these people because all of these are mentioned over here okay it will go ahead and create a response so all of this is happening at the API at the back end the consumer does not have to to think about all of this okay you just have to make this request and send it and everything is going to happen at the back end at the API and the API will send you a well prepared list of all of these things and then there is the data scores of 200 so the now the client consumer can take all of this data and it can put it together in the form of a nicely written HTML page so this is how the all connection request uh page is going to be created with an API and now let us see how do we create a post so in create a post I have this popup I can go ahead and write the text out there right now for the Simplicity we are only considering the text based post not images or something else so what is that going to happen over here so the request would be api. linkedin.com create post it could be anything just a sample that I'm giving you payload would be post text and user ID which user is posting it and where is the what is the post text understand there is there will always be authoriz there will always be authorization for things that are going to happen after login this is going to happen after login so there will be an authorization okay so then there would be a method okay method is post because I'm adding some post po to linkedin's database okay and then the body would be yes this is successful so the body would be maybe the text would be return return for the particular response and then the status would be 200 if this is a correct if this is the correct request if for example I go ahead and put some characters which are not allowed or if I go ahead and put maybe I think LinkedIn only takes about 500 characters if I'm putting 600 characters then it will throw an error that no it is not possible so this is how the create post will be created after this we have delete post if I go ahead and click on delete post what will happen so I can click on this three uh icons three dots then I can click on delete post then I'll have to understand what happens after that so here the request would be this delete post I have created new endpoint authorization should be there because I should only be able to go ahead and delete my particular uh information out there and then payload is post ID I'll enter a post ID that yes for this post I have to go ahead and make sure that I'm deleting something and there is Method known as delete okay there could also be user ID in the payload okay and the method is delete this is the important part because I'm going ahead and deleting some information from LinkedIn and then the body response would be success or failure based on whether it is deleted or not and Status could also be 200 500 400 depending on what it is correct or not okay so for example here let us go ahead and understand some more things so if for example the end point that I'm looking to talk to does not exist okay for example I've made a spelling error over here so the status would be something 404 because the client has sent a wrong request similarly if I go ahead and uh give an error such as if I go ahead and maybe try to if thousands of people or millions of people go ahead and try to delete the post at once then server would be flooded so here it will send a 500 or something error that no right now server does not have banded to go ahead and entertain your request okay so these could be some of the errors out there this was an overview of apis okay so so far we have talked about few things I'll let me go ahead and revise so we first talk about what are some examples of apis we talked about Uber we talk about cred we talk about PTM and booking.com then we talk about what are the three kind of use cases on API then we talk about three example that I have given you and then we talk about what are the pros and cons of API so apis will help you reduce time to ship it will give you added functionality without committing to all the development resources it will also go ahead and provide you some kind of standardization the cons are it will it will be an added cost like an added operational cost and also there are going to be dependency on different apis then we talk about how API works every API should have a request a response Whenever two uh people are connecting together through a form of an API there will be a API consumer who consumes the API there is an API provider who is providing the API so here there would be a request there would be a response the request will contain endpoint type header and payload while the provider will go ahead on the basis of the request it is going to send the response which contains the status and also the content on the message that is delivered as a result whatever has happened at the back end of the provider the API consumer does not have to think about the same okay it will just send the request in the particular format and then we'll receive the response in a particular format okay and we have taken example of Linda's internal API so far so this has been the revision now we will go ahead and talk about an important thing which is API product management okay understand API product management could be different at different kind of companies but I'll take some kind of inspiration from this really wonderful book written by Marty Kegan and in this book he mentions that as a product manager your responsibility is to take care of four risks the first thing is valuable you have to make sure the product is valuable second is you have to make sure that the product is usable then you have to make sure whatever product or experience that you are creating is actually feasible and fourth is viable I'll go ahead and try to Define all four of these to you and it's a very good Compass to understand what is your job as a product manager is okay so let's go ahead and talk about the same so valuable means that the product that you are creating is actually useful for the audience okay so the consumer needs your product it has it will only be avilable it it solves an important problem in the life of the user and customers are willing to exchange money or attention in the exchange of this particular value so that's the first part your product should be valuable the yeah the second part is usable so the user should be able to go ahead and use the product really well so here mostly designers are going to play a very important role but you as a product manager can do the right kind of user research and bring your point towards the designer so that they can go ahead and use this data in order to create better products the third part is feble okay here you have to understand that your engineers are going to go ahead and create these kind of solutions or products and Engineers play an important role in making sure that if it is feasible to create this kind of product or not okay here you as a product manager can go ahead and talk about how the software development life cycle works understand it really well understand the developer empathy understand performance scalability and security if you're talking about an API okay similarly if you if you again go back to the usability if you are a product manager of an API you have to make sure that the documentation is correct so that other people can use it and also the ease of use your API should not be very complicated to go ahead and use there has not to be like a lot of setup costs out there otherwise other developers will not use your API and then the last part is viable okay so you have to understand the business objectives okay whether the API that you are creating aligns with the long-term and short-term goals of the company and different departments in the company or not so these are the four thing that you need to take care of while you are going ahead and becoming an API product manager here understand that valuable part is important for you is the most important for you to consider as a product manager because here the developers are going to be your consumers and you need to make sure that you can empathize with them okay now to give you a case study or an example so we'll take an interesting example of open ai's API okay so open AI has created chat GPT and in order to make sure that you can use these kind of apis in our own application they have recently launched open AI API okay so we'll try to go ahead and break this API into these four components which is valuable usable and feasible and viable and we'll try to understand what what is the role that the product manager might have played over there okay so let's go ahead and talk about the same so first is valuable so in terms to understand whether this product is valuable for the developers and bigger Community or not people who are going to be the consumers of this API we have to understand what are the use cases so if you understand the use cases of jobs to be done really well then you'll be able to understand that yes this is going to be useful or not okay so these are some of the jobs to be done that these the the developers that are going to use this open AI API are going to have okay so jobs should be done are as a developer working at notion this is a Persona I want to use chat GPT API so that my users can autogenerate content okay so notion has been using the developer of notion have gone ahead and they have integrated open AI API to make sure that they are able to autocreate content like autogenerate content on the fly at least the draft of the content okay so this is one use case and as a product manager at open API open AI you should be able to understand these kind of use cases that is only you are going to go ahead and make sure that the product is useful for this audience or available for this audience then as a developer working at Alexa I want to use chat GPT API so that my users can get real life answers from their voice commands Okay so this is what an alexas developer would have in mind when they are looking to integrate chat GPT in their own interface and then the third part is maybe I'm an indie developer I'm a independent developer I want to use chat GPT API so that I can go ahead and create a small chatbot business I can go ahead and send uh like go ahead and create a small business which creates chatbot through openi API and then send it to small businesses out there okay so as a product manager this is your Prime responsibility understand the use cases of the thing that you are creating in API you have to empathize with the developers what they would want to create with these kind of apis okay so this is the valuable part so you should be understanding what your API does how it helps content what is how it helps your users what is the context and then what is the Persona of your particular audience and job should be done is a very good framework to go ahead and understand all of these things the second part is usable you have to make sure that people even if they are Developer they should be able to go ahead and make sure that they're able to understand and use your API really really easily okay so here they have done very beautiful things if you go to open a open a API page you are going to see that they have created so many helpful guides okay that you can go ahead and quick start we have gone ahead and given some kind of sample applications to you already so that you can go ahead and get started as soon as possible similarly they have made sure that no matter what kind of language that you code in like all the common languages such as Java python Javas scpt script they have made sure that their libraries open a library are available in the same so no matter what language you use there is like a bundle of open AI functions open AP open AI API that you can go ahead and use in your own language so that is also like thought through from the usable angle of an API so this is also like something that the product manager can pitch in now the third part is feasible okay what is the role that you as a product manager can play in feasibility when Engineers are working okay where because understanding feasibility most of the time engineer have to play a role so you can go ahead and assist the engineers help them make better decisions okay so first you have to understand what is the application of large language models okay so the core technology behind open open AI say that it helps it is a large language model which is able to go ahead and talk almost like humans okay so now you have to understand that yes we have created the large language model what are the applications of the same so that is could be your responsibility as a product manager then you have to make sure that the thing is scalable you have to make sure that it is performance oriented like people are able to get results quickly because you are talking about user experience then you have to talk about security as in chat GPT whether it is using your own data to train itself whether the data is secure or not so this is going to help create a better experience and more like a secure experience to the user that you have to tell to the developer that yes this is how we are going to go ahead and do the same after this you have to manage the whole software development life cycle at some of the companies the product owner or product manager or an engineering lead would be available to to you to manage this but you also need to sometime step in in order to observe if things are going in the correct direction or not and you can also go ahead and Lead experimentation okay understand chat GPT has not created the best version of GPT in the first Cod they understood that it is a far-fetched cold we first have to make sure that we are releasing something understanding the market segment and parall we'll keep on improving the system so they started with like gpt2 I think couple of years ago or one year ago and then they started with gpt3 in September and then very recently they have launched gp4 so they have been moving rapidly but there is a thought process behind the same so you can as a product manager play a very important role in understanding this experimentation and then taking action based on the same now the last part is viable okay so viable is also an important part so understand viable talks about whether this business this product decision makes sense for your business or not okay so now here you have to understand is the cost of running model viable with pricing so they are charging around $20 for one subscription of chat GPT and for API I think they are charges around few cents for particular requests out out there so they have to make sure that the cost of running this model because it is very costly in terms of computing resources is actually balanced with the price that we are charging and there is a hope for the company to become profitable so that is something that a product manager a business product manager could bring in then you also have to understand if we have a distribution model do we know enough developers do we have partnership with so many companies such as figma nocean which have been like initial adopter of these apis so that our API could be going ahead and be used by and made popularized by these kind of people so distribution is very important yeah in terms of viability you can also consider that if your partnership with Microsoft is in sync with free API access okay so you can go ahead and provide all of the services that we are offering on the top of Microsoft Azure so that people are willing to go ahead and spend some money in Azure and maybe both of you parties are making some kind of money in the long term and there is a sensible business model at place okay so this is all about apis so we have gone ahead and considered what apis are we have talked about what are the technical parts of API the request response headers and uh and the type of the request that you can send put post get and delete and we also talk about like an LinkedIn example API and then we talk about how as a API product manager you can go ahead and consider four important things which is whether your product is valuable usable feasible and viable and we have taken an example of chat GPT and or open AI API okay so this is about this session guys and I'll make sure that I'm in including a quiz in the at the at the bottom of this video go ahead and attemp the quiz so so that you make sure that you have understood this concept really nicely and I'll also include some resources such as these so these are few resources that I'm going to attach here you can find like a like a playground through which you can go ahead and play with different kind of apis like understand what request responses are then we will I have also included a resource where you can go ahead and get a list of interesting apis which you can go ahead and try most of these are free apis and then I have also included like a resource through which you can learn a very important tool known as Postman which will help you test AP understand as a product manager you might need not need it but it's good to go ahead and know this kind of information if you love tinkering around things and then last part is I have also included a Blog where someone has mentioned like some cool use cases of the chat GPT or the Open Eyes API okay so that is all for today's session we'll see each other very soon thank you and take care