41–49 of 49 posts
Earlier quoted context omitted.
Might want to look at https://rocketship.it/ ; not an API, but a set of libraries for working with the various carrier APIs.
Developer of RocketShipIt here. Thanks :)
Is it safe to assume that the developers have forgotten that there's a very big world beyond the US borders? The title doesn't say so, the blog post doesn't either, and the website makes no reference to the countries supported. But as the API doesn't take a country field, it's the only conclusion I can come to.
It's nice to see startups tackling shipping APIs - they really are ugly. What I'd really like to see is something that reaches down to the inventory level, I.e. I'm shipping these 5 SKUs, what's the best price among the carriers I support. It's a complex problem (from experience) but it would provide real value to smaller shops who want to implement economy shipping but don't want to deal with all the APIs.
The idea is awesome, but handling products via a SKU is hard. For instance, if you had the SKU 517030000077284 (a Gibson Les Paul) how would you determine the package size that each customer individually uses? Or determine how much extra weight was added by packaging to keep the guitar safe? I would love to solve this problem but it is definitely a hard one to solve.
A general solution would be much harder, but if it had existed we would have forked over money without too much thought.
To be clear, is this CASS/DPV-style validation? Is it certified CASS/DPV? If so, that would be awesome. Any info on usage limits for the free tier, etc? Can we use this for address verification only or is it required to purchase as well?
Indeed it is! And there's no usage limits
Is there any US equivalent? What data do you use to back the address verification?
What are the units here? Says -d 'parcel[length]=10.0' \ -d 'parcel[width]=5.0' \ -d 'parcel[height]=8.0' \ -d 'parcel[weight]=100.0'
I am curious how you guys are getting around the terms of use of the carriers especially address validation as it strictly forbids serving that information for others not associated with the developer key.
Perhaps they are using some other address validation service/data that allows for it.