Suggestions for Table API vs. Import Set API

[Jordan Alcock]

Hi Everyone,

Wondering if anyone can provide any insight around using Table APIs vs. Import Set APIs.

Looking specifically at REST, and publishing a set of REST endpoints for users to consume.  GET is pretty straightforward, but PUT/POST seems a bit more complex.  

If we're using Table APIs it looks like we would have to write business rule scripts to validate reference fields, whereas this is built into the import set - I think we could also cover off audit with a business rule.    We've heard from quite a few people that import sets are preferred but I'm trying to understand exactly why so we can make the right decision.

These aren't generally going to be bulk transactions, more transactional in nature.  I would generally assume that bulk we would want to funnel into import APIs regardless.  

[Ankur Bawiskar]

Hi Jordan,

If you are exposing end points to 3rd party users better to go with scripted rest api where you can have custom request and response as json or xml.

Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.
Thanks
Ankur

[Jordan Alcock]

Thanks for your suggestion Ankur!

To clarify, we're planning on exposing internally only, but to teams outside of our core platform team.

We anticipate a lot of integrations with other systems, particularly in the IM, CMDB and catalog spaces so we're looking for a solution that we can standardize a set of offerings for general consumption.  Would scripted rest apis still be the right approach for something like that?