Core Concepts of Inbound REST API


  • 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 integrating into ServiceNow from third party applications. 
  • Developers must update credentials in the code samples. 
  • Code samples are available in multiple standard languages used with integrations. 

Comments

Popular posts from this blog

Background Scripts

Glide Record Cheat Sheet

Setup OAuth2 authentication for RESTMessageV2 integrations