The rate shop returns no rates and the shipment fails with an SDK.PreRate error when the address check that runs before rating cannot finish. This usually means the address-validation service reached its daily request limit. The carriers are fine; rating never starts.
Problem
No carrier rates show in the rate shop for small parcel or LTL, and the shipment fails with an SDK.PreRate error. The address-validation service returns a message like:
Account's Developer API limit has been reached. Please upgrade to execute more REST API calls.
Cause
Address validation runs as part of the checks that happen before rating (the pre-rate step). If the address-validation service reaches its request limit, the pre-rate step cannot finish. Rating does not start until pre-rate finishes, so no carrier returns a rate. It looks like every carrier is down, but the carriers are not the problem. The limit usually resets on the service's next cycle, often the next day.
How to check: Look at the pre-rate or process message for a limit message such as "Account's Developer API limit has been reached." If you see it, this is the cause.
Fix
- As a quick workaround, rate using services that do not run the pre-rate address check, if you have them.
- Wait for the address-validation limit to reset, usually at the start of the next day, then rate again.
- If rating still returns no rates, or this keeps happening, email support@shipstore.com. Include your company name, when it started, and that the pre-rate address check is returning "Account's Developer API limit has been reached." Support can temporarily remove the address-validation step from your process flow and review how often it is being called.
What you should see
The rate shop returns carrier rates again for small parcel and LTL, and there is no SDK.PreRate error.
Related articles
- Large batches throw rating errors: use legacy mode