 Hello everyone. I am Sanjay Gupta. I welcome you on Sanjay Gupta Tech School. I hope everybody is doing good. And as you know, this is day 62 of Salesforce Learning Bootcamp. And this week we are learning integration with Ankit. So today we are having part three of integration. So some more concepts and functionalities Ankit will be demoing you. So welcome Ankit on the channel and please introduce yourself to the audience. Yes, Ajay. Thank you for having me on this platform. A quick introduction about me. My name is Ankit Jain. I do have more than 10 plus years of experience in the Salesforce ecosystem where I worked as a Salesforce architect. Moreover, I am also a certified Salesforce instructor too. In addition to that, I also conduct the corporate trainings where I have conducted around 30 plus corporate trainings for the different corporates. On the different topics including the admin, PD1, PD2 integration, sales cloud service cloud and few more. Moreover, I am also very much active on the different Salesforce communities including the stack exchange as well as the dev community too. That's all from my side. Please, Ajay. Okay, this is great. So like, I hope everybody got to know like how much experience Ankit is having and what kind of training he has done already. So I am happy like he's on this platform and sharing his knowledge on integration. Now, if you want to become a part of community where lots of beginners and experienced folks are connected and you want to discuss your doubts so you can join this telegram group. And you can become part of the community and you can discuss your doubts. Okay, so moving forward like, like this is week 17, I guess so Ankit, can you please? Yeah, so this is week 17 and we are learning integration. So this week we'll be having only three sessions and next week also we'll be having three more sessions on integration. Right. So these two weeks are dedicated for integration and after completion of integration, we'll be having a development project. And after that we'll jump on the lightning WAP component and lightning or a component sessions. Right. So do follow Sanjay Gupta Tech School on YouTube, telegram, Instagram and LinkedIn so that you can receive all timely notifications. And all the important links are available in the video description. Right. So share the link with as many people as you can because all the sessions are happening free of cost. And every week we are having sessions and I have also planned like in future I will be inviting more experts related to different clouds. Right. So share Sanjay Gupta Tech School YouTube link with as many people as you can so that they all can be benefited. So with this I pass my to Ankit so that he can share his knowledge on integration and continue the session. Over to you Ankit. Thank you, Sanjay. Thank you for helping the community in all the possible way. Again, I welcome you all. Good morning, good afternoon based on your geographic location. So yesterday we covered what is remote site setting, what is name credential, what is connected callback, right? Or what is connected app. In addition to that we also talk about few of the APIs we talked about how we can perform the authentication as well. Right. Now, in today's session we'll be talking more specifically about the REST API. Okay. If you see this diagram, this diagram basically represent a kind of a C where we do have the different types of APIs available in the Salesforce, right? In Salesforce we do have the more than 10 or 15 plus different types of API, right? Like few of them are the REST API, SOAP API, Bulk API and the PubSub API. In addition to that we do have the API like the metadata API, analytics API, we do have the Einstein related API. We do have the platform specific APIs as well. But in this boot camp we are specifically covering those APIs which deals with the data. So we have decided to cover the four different APIs which directly interacts with the Salesforce data. That is nothing but the REST API, SOAP API, Bulk API and the PubSub API. So today we'll be focused more on the REST API of the Salesforce. Again, we already briefed about the REST web service. Now we are moving toward the REST API. What is REST API basically? REST API is kind of a simple and the powerful web service which works on the different RESTful principles. REST API is a simple and powerful web service which work on the different RESTful principle. Now there are different RESTful principles which are available with the help of which the REST API works. Few of them are whenever you have to work on the REST API, you need a URI, you need the different REST methods. REST API is always stateless. Again, this is a very important point folks to remember. Whenever you are dealing with the REST API, REST API is a stateless. What it mean by the stateless? For example, let's say you are making a request from the client to the server, right? Whatever the request that you are making to the client, client will not save your request. Right? Our client will not save your request in any form on their server. So anytime, every time whenever you have to make the request, you have to send all the data in your request to get the response from the server. As for the REST API, we use HTTPS protocol which is again a stateless protocol and that is the reason RESTful or the REST API always follows the stateless structure. Moreover, all the different functionalities that we do have in the Salesforce. For example, if you take the Salesforce objects or the Salesforce grid, all these fields or all those Salesforce objects, they all are REST enabled. Right? You do not have to write down any additional logic to get the data directly from the Salesforce object. Salesforce have already exposed their objects and fields as the REST enabled. So you can directly invoke, make an API call and access that data. How to do that that we will see in a while. We already discussed REST API does support the both SML as well as the JSON format. Again, next few point about the REST API is REST API is a kind of a lightweight. Right? And because of this lightweight structure, REST API is more recommended whenever you are creating the lightweight applications. For example, if you are creating the applications for the mobiles or for the web apps where the processing speed is a key, you can go for the REST API. So the way REST API works is in the REST API, you always send one request and you can expect the response from the server. But while sending the request, you have to specify the different resources as well as you have to mention the different methods. Whenever you are making the request from the REST API, you have to specify the different REST resources. Moreover, you have to also specify the different methods. Now what are the different REST resources that we have to specify? The first REST resource that you have to specify is the resource URI. Resource URI is basically the endpoint from which you are expecting the response. So whenever you are using the REST resource, the first thing that you have to go and define is your URI. That is nothing but the endpoint. You already discussed in the previous session what is endpoint, how to find out the endpoint. As I said, every documentation, they do provide the endpoint that you have to hit. Salesforce is again not an exception. Salesforce have their own documentation where they are providing the different endpoints that you have to hit. In addition to that, you have to specify the HTTP methods. These parameters are common across any integration. If you are doing the integration from the Salesforce or from any other technology, you have to define all those parameters. Like first is the endpoint, second is the HTTP method. We do have the four types of HTTP methods available. First is the gate, second is the post, third is the patch and fourth is the delete. Gate we used whenever we have to get the data from the third-party system. Post we used whenever we have to write the data or insert the data in the third-party system. Patch we used whenever we have to update the data in the third-party system. And the delete we used whenever we have to delete the data from the third-party system. As I mentioned earlier, these methods are common across the web standard. Either the oracle is implementing the integration or the Salesforce is implementing the integration. They do have to follow these rules while implementing the integration. They have to use the gate method to get the data. They have to use the post method to insert the data. They have to use the patch method to update the data. Or they have to use the delete method to delete the data. Next thing that we do have here is the request head. In the request header, we have to specify the details in the map form. For example, in the request header, you will specify the authentication details. What kind of authentication that you want to do. Whether you are doing the error authentication or you are doing the API key authentication. What kind of authentication that you have to do, you have to go and specify in the request header. Moreover, in what form you are expecting the response. As I said, the REST API deals in both XML and the JSON. Moreover, it also deals in the plain text form or in the HTML form as well. So in what form you are expecting the data, you have to go and specify in the request header. That we specify as the content type. Moreover, there are few additional parameters that we also set in the request header considering the timeouts and different things. I will show you how we, what are the different headers that are applicable in the Salesforce 2. And the last parameter that we do have here is the request body. Again, request body is not a mandatory parameter. However, if you are using the post or you are using the patch in this scenario, we have to specify the request body. Request body is not required whenever you are using the get or whenever you are using the delete. However, it is mandatory to specify the request body. In the request body, you will put all those details which you have to send to the third party system. Request body is mandatory whenever you are making the post request as well as you are making the patch request. Let me navigate you to the few important documentation that we do have in the Salesforce. Let me exit my full screen. The first thing that I am navigating you. Again, we do have the information available regarding the REST API. I will also navigate you the complete documentation. But before we dive into the full documentation, which have lots of information, I will take this documentation first. As I said, for the REST API, what we have to specify, we have to specify the different resources. The resources is the URI as well as the HTTP method. We do have these different types of HTTP methods available. All the resources that we are accessing using the REST API, they will be accessed over the HTTP. And as it will be accessed over the HTTP, REST API is a stateless. REST API is the stateless. Moreover, REST API does support different types of authentication. It does support the API key authentication. It does support the OAuth authentication as well. Moreover, REST API deals with the different types of data, JSON as well as XML. In case you are not specifying the content type that you are expecting, JSON is the default whenever you are dealing with the REST API. So if you have to go and perform the operations on the data, this is how you have to go and pass the endpoint. So this is your endpoint basically. If you see the endpoint, the endpoint, whenever you have to interact with the data, it's kind of a common till here. Where the first you have to specify the instance. Instance means your Salesforce org. Instance URL. For example, if this is my org, this is my instance. Till this lightning.force.com, this is my instance. Till here, I will get the instance. So the first thing that you have to specify is the instance, followed by the Salesforce.com, followed by the services, and followed by the data. This is your base URL. This is your base URL. Followed by that, you have to also specify the version. So till version will be your base URL. If you go and refer any type of endpoint till here, you will find the common. Till version, you will find the common thing. So what is your endpoint? Your endpoint is instance.senseforce.com, followed by the services, followed by the data. If you follow this documentation, you will see that we have explained the different parameters in very detail. Again, we'll put the link in the description. Again, we'll put the link in the video detail so that you can access that documentation easily. Again, the next, as I said, whenever we are dealing with the REST API, we have to set the different types of headers. And this is the list of headers that we can set. Again, based on the integration documentation, you have to figure it out what type of headers that you have to set. So in case you are dealing with the specific content type, then you can go and specify the content type here. So whenever you are setting the header, you have to always set the header in the map form. How the map form works, like in the map, we do have the key and we do have the value. Similarly, the REST API headers works in the same way. Here we do have the key and we do have the value. Every time we do have the key and we do have the value. These are the different REST headers that we do have. Based on the documentation, you have to go and set all these different headers. In case you are accepting the response in the form of XML, then you go and put the application in XML. In case you are sending the request in the form of JSON, then you can go and put the content type as JSON. In case you have a specific authorization, then you go and specify the authorization here. Moreover, you can also specify the authentication as well. So these are the different list of headers that is supported by the Salesforce. Uncle, by any chance, can we share this link in the chat right away? Because folks are saying they are not able to read the content properly. Let me paste it to you. Let me figure it out a bit. How we can do that. You can just paste in the chat of this Zoom. Okay, let's move forward. We have to go and define the different HTTP methods as well. We talk about this HTTP method, gate method, head method, patch method, post method as well as the delete method. As I said, we use the gate method whenever we have to retrieve the information. We use the head method whenever we have to retrieve the resource metadata. We use the patch whenever we have to update the record. We use the post whenever we have to insert the new record. Similarly, we use the delete whenever we have to perform the delete operation. Similarly, we use the delete whenever we have to perform the delete operation. Again, I am repeating whatever the HTTP methods, whatever the data that I am talking about, it is not specific to the Salesforce. Any type of integration, any system is doing, you have to follow these rules. These are the rules defined by the web standards. Okay, now whenever you are sending the request, you might get the different types of response codes from the system. Whenever you are sending the request, you will get the different types of response code from the system. Again, there is a complete list of the response code. In this documentation, they are covered only few. If you want to have the list of the complete response code, you can go here and you can put here HTTP response status code. You will get the complete link either from the Mozilla or from the Chrome. You can see here, we do have the complete list of the response code. The response code starts from the number 100 and it ends with 600. For each response code, we do have the specific message. For each response code, we do have the specific message. Most of the folks, when you observe the web, you might have heard about the error response code as 404. What the 404 says, 404 says that the request is not found, or the resource is not found. You can see here, from here, 404 is coming up. The server is available or the request is not available. Each and every response code will be logical. In this documentation, they have shared the few response code like the 300, 400, 400, 100, 300, 400, 400. How to identify whether you are getting the successful response or not? The successful response we do have in the range of 200 and 299. In case you are getting the response code from the system in this range, that means you are getting the successful response. However, if you are getting the response code in some other range, then basically you are not getting the successful response from the third party system. Generally, we use this for the informational response, but whenever you are retrieving any request or making any request to the third party system, we either get the response in this range or we get the response in this range. In case the server is not available, then we get the response in this range, or in case for the client-specific error response, most of the integration teams, they use this kind of range. So they do have to follow this convention as well, whenever they are sending the status code. This documentation is again a breach of information, where you do get a complete overview about the REST API. In case you want to complete deep into the REST API, what you can do here is you can navigate to this documentation. Again, this is the API guide that Salesforce have provided, where they have specified all the different details about the REST API. They have put here tons of examples that also you can use to practice the REST API as well. They have put about the different architectural guidance that we already talked about. If you guys can go and follow this link here you can see, I talked about the REST resources and the REST request where we talked about the URI, HTTP methods, headers and the request body. We talked about the REST full resources architecture where I said that the REST API is a state list. REST API works in the client server mode. With the REST API we can perform the authentication with the help of OAuth 2.0. This is the complete guide that you can prepped to perform the in case you want to deep dive into the REST API. But for the starting, I believe this kind of a cheat sheet will be very helpful to get the overview about the REST API. I will also put this link in the chat box so that you guys can follow this link and have this link with you too. Sanjay, can you also please paste this link in the chat? Yeah, sure. Now, we talked about the REST API. We understand the different terminologies with respect to the REST API. Let's move into the practical mode now. What we will do now is, we will we will hit this different APIs that Salesforce have offered with the help of a tool called Postman. So what is Postman basically? Postman is a kind of a application or you can say it's a kind of a tool that is used in different organizations to test your APIs. Whenever you are creating the API, if you want to test your API from any third party system, Postman is one of the famous tools that most of the organizations are using. In Salesforce, we can also use or we can also test the different APIs that Salesforce offer with the help of this tool called Postman. In case your organization does not have a Postman Salesforce also provided the alternative that is the Workbench. However, Salesforce strictly mentioned that whenever we have to test the API over the Workbench also we should go and use the Postman. Because whatever the platform APIs that Salesforce is developing, they are exposing all these APIs on the Postman itself. If you go over this Postman, there are more than 25 million registered users who are using the Postman and on the Postman, you do have more than 75,000 open APIs available. Indexed 5,000, we do have the open APIs available from the Salesforce as well. So how to use the Postman? Again, it's a free tool. You do not have to pay a single penny to download the Postman. Postman is available in two different versions. It is available in the web version and moreover it is also available in the desktop version as well. So what you have to do, you just have to search and search the Google that is the Postman download and here you will get the link. As I said Postman is available in two versions in case you want to use the web version you can directly sign in here and start using the web version. Again, quick note, as of now the web version is not stable. The Postman team is still working on their web version. The consistency is not there in the web version. So for the time being, I will recommend that you guys go and download this Postman tool here. You just have to, in the Google you have to search for the Postman you will get the first link to download the Postman. You just have to click on this button and the Postman tool will be downloaded for you. You have to install the Postman software the way you install any other software. You just have to go and click on next, next, next and install the Postman. After that you have to go and create the account on the Postman tool. The way we sign up for the Salesforce developer org the way we sign up for any other account like the LinkedIn or the Instagram, simply you have to also go and make a sign up to the Postman application. Basically what you are doing is you are creating the applications on the, you are creating your account on the Postman. After that, if you go and launch the Postman this is how the Postman will come up. After that, if you go and launch the Postman, this is how the Postman will come up. Now, the question is how we can integrate this Postman tool with my org so that I can perform the integration. Now, the question is how we can integrate with this Postman tool with my org so that, sorry, here is my org this is my org so that I can perform the integration. Salesforce have put a very good trailhead document with which you can easily connect the Postman to your org. Salesforce have put a very good document with the help of which you can easily connect you can easily connect the Postman as a tool with your org although I will be showing you in live how we can do that but in case you guys are stuck somewhere while doing the integration or while practicing you can go over this trailhead module and you can follow the steps. They have given the steps point by point what are steps that you have to follow to make the connection of your Postman with your org so the first thing that you have to do here is you have to go here and create your workspace. What is the first thing that you have to do? You have to go here and create your workspace so to create the workspace you have to navigate to this workspace step. Sorry to interrupt Ankit, can we zoom in like text sizes are there? No, the Postman I am not sure whether we can. Okay, can you try control plus maybe if it works. Yeah, I tried. Okay. Now it is better. Okay, so what you have to do you have to navigate to the workspace in the workspace you have to take the option of the create workspace that is the first step that you have to do so let's go and create the workspace here it is not launching right so what you have to do here you can go and create any names to the workspace so let's say I am giving the name to this workspace as integration demo. I am giving the names to the workspace as the integration demo. As I am creating this workspace only for me I am selecting the personal here in case you want to share the APIs with your org you can go and set up the team as well I do not have a team here you have to first go and set up your team in the Postman again that's about Postman concept for the time being I am just selecting the visibility as personal and creating my workspace after you have created the workspace now you can see here your workspace is available here in case you missed your workspace you can go here and you can just select the workspace from here and your workspace will be launched so this is the first step that you have to do as a part of next step what you supposed to do here is you will go here and search for the Salesforce developers what you will do you will go and search here for the Salesforce developers or you can search for the Salesforce platform API in our scenario platform API will be more logical you can have the Salesforce platform API available in case you guys are working on the B2C cloud or the B2B cloud or the marketing cloud accordingly you can select the type of API that we have to deal with but here as we are dealing with the core platform I am selecting here the Salesforce platform API and what I have selected here they are the Salesforce platform API so this is the different list of APIs that are available from the Salesforce this is the different list of APIs that are available from the Salesforce I have selected here the platform API now the next thing that you have to do here is again this is the API offered by the Salesforce we cannot directly modify this API so what we have to do here is we have to clone these APIs for our own usage so how you will clone that for example here I have to clone this platform API I will go to the end and I will see these three dots here just have to go and click on these three different dots here you will get option called create a fork in postman whenever we are perform the clone operation basically what we are doing is we are creating the fork so I am selecting the option here called create fork here you can go and do any label to the fork right let's say I am giving the label to the fork here as the integration demo fork and where you are creating this fork you are creating this fork in the workspace that we have created in the step one where you are cloning this you are cloning this in the workspace that we have created in the step one again I am repeating first you have to go and create the workspace after that here you have to go in the global search and search for the Salesforce developers after that you go and fillet the Salesforce developers or the Salesforce platform API after that what you have to do you have to just go and click on these three dots click on create a fork you will be on this screen so here I am naming this fork as an integration demo fork and click on the fork collection now what you have done here is in your workspace you have copied the APIs provided by the Salesforce in your workspace what you have done you have copied the APIs provided by the Salesforce so Salesforce is providing these different types of API to us Salesforce is providing these different types of APIs to us for today we are discussing only the REST API but in case if you guys want to explore any other APIs you can definitely go and explore these APIs or the different platform APIs from here now what we have done we have downloaded this and we have put this on our local workspace now the next step that we have to do here is now the next step that we have to do here is we have to connect the postman with my org how we will do that to do that you will go to this authorization tab by default we are on this overview tab so I am selecting this on the parent folder and after being on the parent folder I am navigating to this authorization tab I am navigating to this authorization tab now here you will see the different details what type of APIs sorry what type of authentication what type of authentication this platform this postman is using the postman is using the OAuth 2.0 authentication what type of authentication that it will use to connect to the Salesforce it will use OAuth 2.0 authentication again you do not have to disturb anything you have to make sure that the header prefaces barrier you do not have to disturb anything just have to scroll down in the bottom you do not have to disturb anything you just have to scroll down into the bottom this button called get new access token you just have to click on this button called get new access token as soon as you click on this button a request will come to your Salesforce org a request will come to your Salesforce org in case you guys are doing it for the first time you will get a popup or you will get a block popup blockup from the chrome right so you have to make sure that you are allowing this popup blockup to request to come up successfully I have observed in my past training that whenever we perform the integration for the first time on most of the machines we get a popup blockup again it's completely up to the chrome version that you are using but just an FYI what you have to do here now is you just have to click on allow you just have to go and click on allow now you can see here your authorization is done successfully and you have to click on open postman from here your call is authenticated that means your authentication is successfully and you have to go and use this browser again at the backing it is still doing the authentication or you can see here I am getting the option here as authentication complete now automatically after the three seconds it will move to the next screen automatically after the few seconds it will move to the next screen what it now you can see here at the backing what this is doing whenever we are making this integration what the platform have done the automation is they are sending here the client ID as well as the client secret key right so what you have to do here is from this screen you have to copy this instance URL from this screen what you have to do is you have to copy this instance URL so I am just doing the copy here what I have done I just make the copy here of my instance URL and without fail what we have to do here is we have to click on this button that is the use token I have copied this instance URL you can put this copied instance URL on your notepad or on your sticky note wherever you want and after that without fail what you have to do here is you have to click on this use token now if you again follow this authorization you can see here the different types of parameters are populated like your access token is populated this is the URL that it has been used right this is the authentication URL that has been used your client ID is populated over over it and you can see the different values right you just hover over it and you can see the different values now what we have done here is we have copied the token this is the token basically that we got from the sales force okay we do not have to again do anything we have copied the instance URL now the next step that we have to do here is we have to go to this variable section the next step that we have to do here is we have to go to this variable section and scroll down where you will get the end point you just have to scroll down where you will get the end point what you should do here is you will go and paste your end point in the current value what you will do here is you will go and paste your end point in the current value and without fail go and save your changes by hitting the control s because as of now the changes are not saved whatever the value that we have populated here it is not saved you have to make sure that you are hitting the control s here so that your changes will be saved just without fail what you have to do here is you just have to use the control s to save your changes any question? so guys if you have any question you can just post your question in the chat box so that Ankit can ask all the important links are already available in the chat box so you can just copy and have those with you so we will wait for 1 or 2 minutes for the questions so Ankit will be answering otherwise we will be moving forward and Ankit I can say there are few questions if you can see the chat box like previously we will ask some questions there is a question from the fearers that so different race APIs would ask the different headers in the documentation they will specify what all headers that you have to pass so according to the documentation we will ask the different headers Rutuka part will have a question can we have a request body in the get method again Rutuka we cannot have the body in the case of get method because your get method only deals with the URL part although you are setting the body it will be of no use Deepak I could not understand your question what a redirection message means Amar it's again a company to company scenario most of the companies based on my past experience they use the postman again in case they are not you can also insist to use because it's a free and open source software that anyone can use for the API testing and you can also make your point that it is a free software which also Salesforce is recommending for their integration testing if you see the postman we will see in a while most of the things are automated in case you are using the workbench but you have to remember the complete URL moreover the UI of the workbench is also not friendly so in case if anyone is asking you to use the workbench you have to ask for the reason why they are specifically looking for the workbench and not for the postman right because if you log into the workbench the workbench also Salesforce have put the notification that we have to use the postman rather than the workbench what is grant type I'm not sure where this question is coming up grant type is nothing but the different types of authentication that we are doing there are different types of grant type this is also available I believe in the name credential as well by default whenever we are making the integration from the postman it is using the implicit grant type you can also in case you have the in case you want to do the integration based on the password username and password you can use the password credential as well in case you want to do the integration based on the pkc nothing but a primary key I cannot recall the exact form in case you want to do the integration with the help of that primary key then you can use this pkc again you have to follow the documentation to figure it out what type of grant type that they are supporting yes endpoint URL is the Salesforce org URL we are directly getting this URL whenever we are making the authorization request so just to avoid the confusion you can directly copy that instance URL from the authorization and go to the endpoint and put that in point here yes I have not given the Salesforce org username and password because for the demo purpose I am already logged in into the org in case you are not logged in into the org and you are making the request from the postman then the Salesforce will first ask you to put the username and password and then it will ask it will do the authorization with your org so yes you are correct first we have to login into the Salesforce username into the Salesforce org before we go into the request from the postman otherwise it will be navigating first to the login screen Sunil I will come back to the real-time scenarios in a while like postman if we are using some other platform then how we can get the client secret and the client token again what you have to do here is I will also take an example for this most probably in the next week where we are connecting from one system to another system and there I will show you how you will get the client key and the client secret in case for example if oracker is connecting with the Salesforce then you can get the client ID and the client secret and the token from the connected app Vinay that we discussed yesterday in case Salesforce is connecting with LinkedIn or Facebook or the Google or the Gmail everywhere we do have the option to create the app so for example if you have to make the integration with the Gmail you just have to type down the Google developers and there you will get the option to create the app first from where you get the client ID and the client secret key Pratik call out related question I will take in the next week when we go and talk about the column Acid no that's a completely wrong statement where you mentioned that integration is nothing but the Salesforce API testing integration is not more that integration is much more complex at the start basically more it will also be a complex scenario for the most of the architectures too in integration there are too many factors that we have to consider we have just touched the tip of the iceberg as of now can you just exist integration user for the multiple integration if you don't know the password and the security token you can do that but Salesforce does not recommend that you should go and reuse the existing integration user for the multiple integration the reason being you might have to set the different type of authorization for the different types of integration so based on your business requirement you can go and create the different types of integration users and provide the different types of authorization okay now let me quickly show you as we have made the connection right again I am repeating what we have done we have click on the authorization we have requested the access token we got the access token and we have updated the endpoint this endpoint thing you have to do only once whenever you are making your first connection every time you do not have to go and save the endpoint because this will be common every time however your token it will be expired in suit there is a time out has been set I have to check the exact parameter where the timeout has been set but whenever we are using access token we do have the timeout defined in case you are keeping the system idle for some time before you make the integration for the testing you have to go and create the new access token right I believe the access token is not expired now let me go and paste my few of the APIs I have very first API that I am testing here is the limits API what this limits API will do this limits API it will validate whether what what are the different governor limits of your org what this limits API will do this limits API will validate what are the different governor limits of your org here you can see we to have the different APIs available how we will understand the usage of each and every API again for that you have to go and follow the Salesforce documentation if you have this API developer guide for which the link is already shared in the chat box you can see here we do have the different types of REST APIs available let me just zoom again you can see here we do have these different types of REST APIs available according to your requirement you can go and open any type of REST API here we are talking about the list limit type of get API so let me search here for the limit right so again if I do this documentation you will get the complete details as I said for every integration we have to follow the documentation right so this is the as we are making the integration with the Salesforce Salesforce will also not accept it this is the end this is the API that we have to use what is the URI that we have to follow this is the URI that says services slash data followed by the virgin and follows by the limit so this is our endpoint that we have to use this API accept the data in the JSON as well as in the XML form what type of HTTP method that we have to use we have to use the get method next thing is what is the authentication mechanism that we are using authorization followed by the PRR token authorization is your key PRR followed by the token means nothing but your session ID how to dynamically generate the session ID again we will talk in detail when we go and connect the tools in our example for now we already generated this token by using the auth so we already have this token right and when we make this request we will get the body in this form right these are these are different parameters that we will get whenever we are making the request so let's go and make this request from the postman so again if you navigate this the advantage with the postman is to do not have to do anything everything is configured for you you just have to make sure that everything is correct you can see here we are using the get method as per documentation in the documentation they mentioned about the get method so we are using this right the format if you go and follow this headers as I said we have to go and see the different headers here if you follow this right these are the different headers that they have said authorization PRR followed by the token ID right if you again follow this they are expecting the again it is accepting the output in all the different form in case you are specifying this slash means you can expecting the output in all the different forms right here as we talked about the json and xml we can expect the output in any different forms here so these are the different places where you go and set the headers whenever you are using the postman right this is your complete URL that we talked about so we talked about this URL like slash services slash data followed by the version followed by the slash limits right this is the one we talked about slash limit you can see this is our URL till slash limits this is our URL till the slash limits right we have already configured the end point as you can see it is coming up correctly let's go and send the request by now you can see here what is the response code that we are getting the response code that we are getting is 200 200 stands for the successful response code and these are the different limits that we are getting from our org these are the different governor limits that we are getting from our org right you can see we do have the different types of APIs available I will request each one of you in your available type you hit right hit different types of APIs top parameters that you have to pass you just go for the documentation documentation is again very simple you have also given the use cases as well for example let's say I have to count the records so I am testing another API now I am just using the different APIs okay so what they have to do in this what the account account API will do again let's say I am a fresher and I am completely and I am not aware about this API will do so I will go here and look for the record now so I am opening the record account API from here let's try to understand what this API will do this is how you have to go and do the self learning right so what this API will do this API will return you the counts of an object that you are passing right this what this API will do this API will return you the count of a record count of the objects that you are passing so what you have to do here is you have to use this endpoint this is the format the HTTP method is get authorization we are a token what all parameters that you have to pass here you have to go and pass the s objects what you have to do is you have to go and pass the s object again if you follow this they have given an example how you should go and pass the s objects here they have given an example how you should go and pass the s object here so here in this URL they mentioned that we could go and pass the s object as account as contact for the demo purpose here they are using another tool that is called like we do have the postman we do have another tool available that is the call tool okay for the demo purpose we have selected the postman because most of the organization do use the postman but in case your organization is also using the call you can do you can go and test the API by using the another tool called call tool as well so again I will be going here this is my this is the method this is the endpoint in this method I have to go and pass the different types of values you can see here s objects that is the parameter that I have to pass let's say I want to get the record count of the account as well as the contact so I am just putting this values here account as well as contact they have clearly mentioned in the description whatever the values that we have to pass that value will be the comma t limited comma t limited means the values will be separated by the comma and just go and click on the same you can see here we are getting the result here so on my account object I do have the 13th record on my contact object I do have the 20 records I am getting this count here not only that you can also go and write down the query from here not only that you can also go and write down the query here again you can follow the documentation as I am aware about your documentation as I have used the documentation in the past you have to use this gate method this is the URL as here you go and define your query let's say my query says that select id comma name comma industry from account object where let's me get the account object and here I am getting the 10 records so I am putting this here the limit as 10 so here I have put the query and click on set you can see I am getting the 10 records here and this is the different records that we are getting as I requested for the id name and industry field I am getting the id name and industry field from the system you can see here everywhere I am getting the id name and industry not only that you can also go and create the record as well to create the record you have to look for the API to create the record I will look for the creation we do have the API available in the as object folder here you can see as object create with the help of this API what you can do you can go and create the record into the system again if you follow this documentation and put here that the create let's say create record I just want to make you folks enable so that you guys can go and use the documentation and start writing your own APIs for the testing right what this API will do this API will help you to create the record right again if you follow this documentation right directly given an example I believe here they might have put all those details you just have to check different links they definitely have put all those details what kind of method that you have to use right what kind of parameters that you can pass they are just given the different example but for the time being as we do have the limited time let me quickly cover to create the record here we have to go and use the post method right this is the end point that we have to use here we have to in the URL we have to go and specify the object API name let's say I want to go and create the record in the account object so I am putting the object now while creating the account I have to go and pass the different types of parameter so where I will go and pass the parameter in the body where I will go and pass this parameters in the body so here I am putting the different parameters let's say I am putting here the account create name I am putting here is account created from the postman likewise you can go and pass the different parameters as well for example I have to go and pass the industry let's say I am putting here the industry as energy another thing that I have to pass for example is the rating whatever the values that you are putting here on the left hand side you have to make sure that you are all putting the API names of the account object because you have to go and create the records in the account object all these things must be the API name of the account object fields so here I am putting the rating value as hot let's say another thing that I have to pass here or let's have only three for now you can definitely try out with more than one field there are lots of examples available here not only that you can also go and create the child records as well for example if you have to go and create the contacts with this different attribute you just have to follow this documentation there are n number of examples that they have shared with the help of which you can go and create the multiple records so what I am doing here is I am just putting all those details here right my parameters is also set where I put the s object name behind name as an account and clicking on the send button you can see here for the successful account creation we are getting the response code s201 for the successful account creation here we are getting the response code s201 right so we have seen this response and the account has been created see the output there is a tab I have displaced it just let me quickly check ok you can see here this is the output this is the id of the record which is created the success operation is true and we are not getting any errors moreover if you want to save this request for the future reference right moreover for example if you want to save this key and this body for the future reference that also you can do here you just have to click on save as an example and you can go and save your api from there right so this changes will be saved on your local machine so this is the example that has been shared and that will be with you always whenever you are there you have to go and hit the same api for some another testing right so let's go and validate in our org whether the account has been created or not I will go to the accounts tab here and check whether the accounts is created or not you can see here the account is created here account created from the postman whatever the values that we have passed like we have passed rating value as hot or we have passed the industry value as energy everything will be available here you can see rating is available as hot and the industry value that we passed as an energy it is also available here this is how you can go and play with the postman by simply following this documentation and simply hitting the different apis only thing that you have to do is you have to just read the documentation understand the parameters that you have to pass understand the method that you have to use you can directly start using these different apis right this is how you go and use the postman this is how you go and integrate your postman with your Salesforce org and perform the testing of the platform apis that Salesforce have offered right I believe that's all we do have today let me quickly take the questions if we do have any so the first question is what data we need to collect from other system for call out again Pratik as I said we will talk more about the call outs in another session so I am not taking the call outs related question now Ravi Shankar if you do not want to share the username and the password with the client to perform the integration then what you can do here is you can go and create the connected app on your Salesforce org and share the client ID and the client secret key yesterday we have covered how to create the connected app and how to access the client ID and the client secret key you can go and share those details with your client so that they can integrate with your system with the help of your circuit in the variables tab all the variables will be auto populated except the end point you have to manually go and populate the end point as your instance URL so Ravi Shankar have a question by sharing the client secret and the token which you will get while creating the okay so when I already answered that sir I didn't get your question in the key and value what we can pass if you have read your question more will be helpful this is how we have covered this is the real time scenario only in the real time we use the APIs to check the limits we use the APIs to check the count we use the APIs to create the record similarly we use the APIs to get the different properties of an object this is kind of a real time usage of using the Salesforce platform API as of now we are not created any platform APIs but now we can go and use the as of now we are not created our own API that we will be doing in our next session but this is how you can use the APIs provided by the Salesforce Madhu asked a brief about the header again Madhu to understand the header as I said let me again navigate to that cheat sheet there are different types of headers are available according to the integration documentation that you have to perform you have to go and add different types of header as we are integrating with the Salesforce for example here we do have this type of header right so whenever anyone is making the integration with the Salesforce for example there is Oracle system who is making the integration with the Salesforce so what all parameters that they have to take care they have to get the endpoint from this documentation they have to understand what kind of method that you have to use here they have to go and set this header authorization is the header that they have to set every documentation they will provide you the complete details what kind of headers that you have to set so if the Oracle is connecting with the Salesforce they are using this authorization header only with the BRR token like this we do have the multiple types of headers that you have to use according to the integration requirement you can also use the put method Pratik put method we use it is same like the upset operation that we do have like upset means in case the record is available it will go and perform the update operation or the record is not available it will go and perform the insert operation similarly you can also use the put operation as well so if you follow this right here you do also get the different types of methods are available one of the method is also available as the put method so yes you can also use the put method here but as per my knowledge Salesforce platform API they does not support the put method but in case you are creating your own API definitely you can use the put method might be they are supporting I am not familiar with the Salesforce platform API they do supports the put method or not as of now I am not I am not interacted with any of the platform API which does support the put method so Sarla asked this question suppose we have to integrate the Salesforce with the weather API where does the postman tool comes into the picture so for example let's say without implementing or without writing your code on to the Salesforce part first you want to test whether the API is that your developer have provided whether it is working correctly or not right so what you can do without writing the complete Salesforce logic or complete Salesforce class you can go and put your end point you can ask the method you can set the different headers and check whether it is working or not you can set the different headers and check whether what type of what type of output that weather API what type of output that you are getting from the weather API right so you can understand the response from there and accordingly you can go and build your own API into the Salesforce right again I am repeating we use the postman only for the testing purpose we use the postman only for the testing purpose in real time if you have to make the integration from Salesforce to from another system you have to go and write down the code in the Salesforce only can you perform the undelete operation through the postman as per my knowledge I never used it but we have to go and check the documentation whether we do have the API available for the undelete or not so let's go and quickly try this out as one of the friend ask this question we do not have any APIs for the undelete operation Prashant so you cannot perform the undelete operation with the help of standard APIs provided by the Salesforce you can definitely write down your own logic in your API resource but Salesforce by default platform API does not provide that functionality I believe I have covered all the different questions that we do have in the chat box again I want to thank you all for attending this session for giving us your precious time and I hope I have made the justice and I have added a few learnings in your Salesforce journey thank you all thank you for your time thank you so much Ankit for sharing all the knowledge and thank you all the attendees for being patient audience and those who are watching the recording so if you have any question you can ask in the comment section or you can just ask your question in the telegram group right so next session on integration like part 4 will be done next week Monday so till then whatever today Ankit demonstrated so you can just practice go through the recording and just implement and I hope next week more demonstrations will be there so next week we will be completing 3 sessions and then in total 6 sessions all the main concepts of integration will be covered as Ankit told like it is a vast topic so we will be trying to have all the concepts covered in 6 sessions right but if there is like more learning will be required so I would request Ankit like if he can share some links from where you can just do some practice so that would be great sure so thank you Ankit for your time thank you everyone see you on Monday thank you all have a good time bye bye