SNOW

Use the REST API Explorer to create and test inbound ServiceNow API requests. Path parameters are part of the endpoint URL.  Query parameters determine which records, which data, and the data format returned in the response body. The HTTP status code indicates the status of the transaction request and does not indicate any information about the returned data. The response body format is set in the headers. The REST API Explorer tests requests as the currently logged in user. The  Allow access to this table via web services  option cannot be tested in the REST API Explorer. Do not use the admin user in code integrations, create a web services only user instead. Disable web service access to tables with sensitive data unless web service access is required CORS rules add security to APIs CORS rules determine which cross-origin resources can access which methods.  CORS rules cannot be tested in the REST API Explorer.  Code samples provide script stubs for integratin...

  An LDAP integration allows your instance to use your existing LDAP server as the main source of user data. STEP1: Define LDAP Server Option1: LDAP Server with MID Server This is the most common method as it is the easiest to configure and doesn’t require much effort from a company AD admin. You’ll need to setup a  midserver  to use this method. Please note that you can’t authenticate (login) using this method and you can’t use a SSL connection. For authentication, an  SSO connection  is often configured. So you use the LDAP Integration to pull in users/groups and SSO to authenticate (login). Option2: LDAP Server with VPN For this method, you need to ask ServiceNow for a VPN Request though HI Support. This method isn’t that preferred is that you are relying on the ServiceNow VPN to work and other maintenance concerns. Option3: External IP Address For this method, you expose an external IP Address to ServiceNow. Option4: LDAPS with PKI Certificate Most companies...

Inbound means that other applications make calls to ServiceNow's REST API to get information from SN ,   basically when some other tool hits your instance(wsdl) with a payload and you process it and acknowledge it. EG, if an incident gets created in a third party tool then an incident gets created in a service now . Here we accept the request and process it. - Direct Web Services - Web Service Import Sets -Direct Web Service API : Servicenow by default creates a webservice api for every table in the system, if you create a custom table system will provide SOAP and REST api to perform CURD operations. - Web Service Import Sets Staging web-service/Web Service Import Sets: this staging allow third party to send data to import table and then we do transform map by qualifying the data to send into the Servicenow.

1. Configure OAuth provider on instance 1 (OAuth Application Registry -> Create an OAuth API endpoint for external clients) Create unique provider profile name. We need to generate client ID along with Client Secret. Both can be generated by system normally. Token lifespan are optional, generated by default system policy. 2. Configure OAuth consumer on instance 2 (OAuth Application Registry -> Connect to a third party OAuth Provider) Create unique consumer profile name. (very important, script will need pass in this consumer profile name as parameter) Client ID and Client secret are the values were generated from step 1. Grant type. Value can be either "password" or "refresh_token". Suggest to use password since you won't have refresh_token info initially. This refresh_token only will be generated during first time when access token is generated. Token URL will be provided by OAuth provider. In this example, it would be the  https://oauth_...

1) Endpoint This is the URL or Address where the SOAP request is delivered. It must be able to reach that endpoint over the network in order for the communication to succeed. 2) Action String that is often optional with the SOAP web service. However, some services do require this to be set. The string is often descriptive of what action should be performed by the web services. 3) Headers/Attributes Found within the HTTP request. They contain information regarding the protocol being used as well as other custom information such as session IDs, authentication token, etc. 4) Envelope Actual document that describes the details of the SOAP request. This is written in XML format. Has a header and a body similar to an HTML webpage. Header and body details are dictated by the web service and explained in a corresponding WSDL document