listTransportationOptions is too slow - it needs a filter option

[JonLaliberte]

There are old issues for this that were closed due to inactivity:
#4169
#4238

This API really needs a filter option, and/or it needs to be much faster.
It takes us 5-8 minutes to figure out the best placement/transport option right now for each shipment.
This should be like, 20 seconds. It slows the warehouse down a lot.

It may help, but not solve the problem to return more/all transport options in one call. Right now we get 20 max, so have to keep calling and waiting for listTransportationOptions to go through them all until we find the option we need.
Again, a filter just makes the most sense here.

[JonLaliberte]

I'd guess that the majority of us want to do one thing: Specify how we're going to ship (small parcel, LCL, FTL) and have Amazon tell us the cheapest combined option of placement/transport options. If you had one call that did all of this, it would eliminate a lot of extra code (and API calls) most of us are duplicating in our own codebases.
I don't suggest that the existing methods go away of course (some clients may need to book their own carriers, maybe compare specific Amazon carriers, consider SPD vs LCL, etc), but a convenience API would be useful here to handle the 80% use case.