Table API or Web service import set/Scripted Rest API? Whats recommended?

[Suggy]

We have a requirement to allow external tool to create/udpate Incidents in our instance. No custom fields, no validations required. Its straight forward create/update.

Person 1 argues that he wants to use Table API, as its simple, straight forward and that is why ServiceNow has exposed APIs for ALL tables.

Person 2 says Table API should NEVER be used, its not a best practice, Irrespective of whether you need validation etc or not, you should instead use Web service import set/Scripted Rest API should be used. 

Person 1 again says then why ServiceNow exposes table API for all tables etc 

So I am actually looking for if there any Authoritive Source of REST API Best Practice out there that explains various scenarios and how to reach the best solution using the various techniques available in ServiceNow.... should Table API never be used or can be used? Rationale behind that etc.

Thanks in advance!

[Saurav11]

Hello,

The scripted Rest API gives you much more control and flexibility. Surely it helps you to customize your code more. You can check the below thread:-

https://www.servicenow.com/community/now-platform-forum/table-api-vs-scripted-api/m-p/1137613

Please mark my answer as correct based on Impact.

[Elijah Aromola]

I think this just boils down to what the requirement is. There are use cases for both. Does your project or team require more granular control over the entire integration? Probably better off with a custom scripted API. Is this just a quick integration to pull records daily from a table? Table API is more than sufficident.

I'm not sure there is a "best practice" around which direction to take. It's just going to come down to what you need out of the API.

Hope this helps.

[Suggy]

Hi, I just updated my question with more details. All that I wanted to know is, as a best practice, is it ok to use Table API or not.

[Saurav11]

Hello,

Yes it is completely fine to use Table API , but more than best practice it is defined by the business use. If you want more control and flexibly go for scripted rest API other wise Table API too does not have any harm.

But as per my experience if they are going to use a POST/PUT/PATCH method better to go with Scripted rest API.

Please mark my answer as correct based on Impact.