I think your way of doing that is too complex. If you have the list of shipment nbrs you need to confirm, you can just do it directly via API with the default API endpoint, can’t you?

The problem with that is we need to confirm anywhere from 500-2000+ shipments a day. We have a limit on how many API calls we can make. If you use the default API, you can only do one at a time. That is why I am trying to get the import scenario to work, so we only have to make one call. 

Well, I see what the issue is. But, I think, if your API limit does not allow you to process that many documents, maybe it’s also going to be out of the license limits even if you work around the API limitation. It’ll just hit the limit in a different place, e.g. number of CPU cores used or something else.

Also, 2000 shipment confirmations a day is like 40-60 minutes of processing with the smallest API license*. So, maybe you just do it overnight and it’s fine.

*Depends on the size of the shipment too.

*if you don’t have any other API integrations running 

I see what you are saying. This would be something that would run at night. The size of the shipments are usually one line. We are already running these import scenarios manually with the same number of shipment confirmations. I am just trying to find a way to automate it.

​@LALBAUGH if you already run those import scenarios, then maybe you can just schedule it. Let it grab the new version of the file and import based on a schedule.

But either way, my point is that if you are fine running it via import scenario overnight, it should also be fine running it via API one by one overnight. 

You can also look at the option of CSV with a FTP and file sync. You would need an FTP server as you middle man to drop off and pick up the file.