That's great Chuck! Difficult topic but explained in very simple way. You are star!!! Thank you. All the best for your future videos on Integrations and other topics.
@@ChuckTomasi For some reason I used to be scared of the scripted REST API but after watching this video it seems manageable. Thanks a lot , you have always been a guiding force for so many of us working on ServiceNow development.
Thanks Chunck.. One query, what if we need to get all the data's which are all available in the Incident Table?? Only max of 10 data i can able to get as a response.
The REST API Explorer will limit you, but the scripted REST API will not. The concern about getting a lot of data (e.g. the entire incident table) becomes a matter of time to get the response and processing a very large payload. For that, you should consider pagination to get a page of content at a time. For example, 50 records, then another 50. With an incoming scripted REST API you can put parameters for the start/count and then use the GlideRecord method chooseWindow() to get just that page of content. For outbound REST services, consider using a data stream to get paginated data from another service.
I am trying to create an outbound call to a microsoft api. However, in the endpoint field, servicenow does not accept all my URL with parameters. When trying to add the query params he apparently failed to authenticate, but one of these params is just my token. Do you know the reason for this?
how do i create the developer account that you mentioned? so that i can get access to the api. its not showing up in my snow. sorry im new to snow and was given no proper training lol.
@@edwinfeliz9986 By default, you need either admin or web_service_admin to access the System Web Services menu. The REST API Explorer module additionally requires the rest_api_explorer menu. So technically, you do NOT need admin if you have both those other roles to access the REST API Explorer.
That's great Chuck!
Difficult topic but explained in very simple way. You are star!!! Thank you. All the best for your future videos on Integrations and other topics.
Thank you. I wish I had more time on this one. I may have to mark a "Part 2". I feel there is so much more to cover about scripted REST APIs.
@@ChuckTomasi Interact with us for a couple of minutes in every live stream, will be fun!! Haha
@@ChuckTomasi For some reason I used to be scared of the scripted REST API but after watching this video it seems manageable. Thanks a lot , you have always been a guiding force for so many of us working on ServiceNow development.
13:31 Begin
The best in the game. Your videos are great, Chuck. Thank you.
Thank you for your kind words.
I love your energy Chuck!
Thanks
You awesome Chuck}
I really love your tutorials..
Thank you. I'm glad you find these useful.
Thanks for the video! Informative and engaging.
This recording still has actuality in 2022 as well.
brilliant vid, give this man a raise
Thanks Chuck! I needed this today!
Thanks Chunck..
One query, what if we need to get all the data's which are all available in the Incident Table??
Only max of 10 data i can able to get as a response.
The REST API Explorer will limit you, but the scripted REST API will not. The concern about getting a lot of data (e.g. the entire incident table) becomes a matter of time to get the response and processing a very large payload. For that, you should consider pagination to get a page of content at a time. For example, 50 records, then another 50. With an incoming scripted REST API you can put parameters for the start/count and then use the GlideRecord method chooseWindow() to get just that page of content. For outbound REST services, consider using a data stream to get paginated data from another service.
Can to tell me how to pull data from servicenow to excel/powerBi
I am trying to create an outbound call to a microsoft api.
However, in the endpoint field, servicenow does not accept all my URL with parameters.
When trying to add the query params he apparently failed to authenticate, but one of these params is just my token.
Do you know the reason for this?
how do i create the developer account that you mentioned? so that i can get access to the api. its not showing up in my snow. sorry im new to snow and was given no proper training lol.
Hi William, You can go to developer.servicenow.com and get your own personal developer instance to experiment and try things. Good luck!
@@ChuckTomasi thank you sir! I will check it out.
Hello ChucK . I am trying to dot walk the location field in the CMDB table somehow I am failing to get the report through to SPlunk.
Sounds like a great question for the community. Have you posted you issue there? community.servicenow.com
This is cheating Chuck, it literally took me a month to master this stuff 4 years back!! Aaahhh
Experience is the comb that life gives you after you lost all your hair
24:10 practice
I don't see the rest api setting on myside would this be only for dev account?
I'm not clear what you mean by not seeing the REST API setting on your side. Can you be a bit more specific?
@@ChuckTomasi Yes, I am trying to connect to the rest API just like you when I search for rest API on the search bar. I am not getting anything?
Ensure you have admin role. If it still doesn't show, check for any disabled modules.
@@ChuckTomasi if I don’t have admin role, I can’t have access to the api am I understand this right?
@@edwinfeliz9986 By default, you need either admin or web_service_admin to access the System Web Services menu. The REST API Explorer module additionally requires the rest_api_explorer menu. So technically, you do NOT need admin if you have both those other roles to access the REST API Explorer.