Hi Jose,
We faced this issue during a rather complicated integration.
SHORT ANSWER
No, you can't use the Import API for multiple import rows sadly. Unfortunately, it's not a simple task.
METHOD 1 - Custom Scripted SOAP / REST
Using a custom-written soap & rest endpoint that you'd create yourself, you can have it read a payload (XML, JSON, whatever your favourite flavor is) and write script to interpret it, and return a result.
e.g. lets assume your POST body parameter is called 'payload' and is a JSON array of results, and the response is in JSON
var responseMessages = {}; //New messages go in here
var payloadParsed = JSON.parse(request.payload); //JSON is native to basic Javascript, and works in ServiceNow
for (var i=0; i < payloadParsed.length; i++) { //Loop through the payload array
//Do stuff with each result
responseMessages[i] = "I did the thing to that line"; //Add some verbosity about that line. Did it work? Did it fail?
}
response.some_response_parameter = responseMessages; //Objects will automatically be 'JSON.stringify()'-ed, turning a Javascript object into a JSON payload string
METHOD 2 - Processor Script
Along the same line, you can make your own Processor. This is basically an endpoint, not strictly JSON or XML, that's callable like a UI page. E.g. instanceABC.service-now.com/my_processor.do
Note that this is really advanced, but gives you the most control. Again, I'd make it read through the payload that gets passed, and do stuff to the rows.
METHOD 3 - Email & Scripted Inbound Email Rule
Using some sneaky script, you can have an inbound email that meets specific requirements check for a CSV attachment, and load that as a Data Source, then run the import & transform. I haven't tried this myself, but here's some to get you started:
Data imports from email attachments
A big downside to this one is that there's no verbosity or response that gets sent back to the initiator like an API call would.
I wouldn't recommend one giant 'payload' field on your import staging table and having the transform read that, I tried it and ran into all sorts of limitations like JSON and XML translations stripping out essential characters, and errors that don't look like errors so your script doesn't know that something's gone wrong.
Hope this helps!
