Does EasyPost have a limit on the amount of requests we send to the API?
We employ multiple algorithms to protect the operational integrity of our API, ranging from simple rate limits to dynamic systems which take into account the CPU time consumed across all of our backend services by each request and the total capacity available to serve them. If you are rate-limited in any way you will receive a 429 status code, at which point your client application should respond with exponential backoff or a similar throttling measure. In general these limits are high enough that non-abusive request patterns will not trigger them.
We provide "batch" APIs for many operations, including shipment and tracker creation. If you are regularly encountering our rate limiters, we recommend that you move to an asynchronous/batch workflow.
Why would I need child users?
Child Users are an organizational tool that can be leveraged to associate specific carrier accounts and EasyPost objects with a User while still maintaining control from master account. These child Users function similarly to a regular Users account except all the billing flows through the parent User and the child User can not login to our website. Child Users can be beneficial if you have a customer that wants to use their negotiated rates with a carrier. Since the billing rolls up to the parent User you will gain greater control over the billing process of your application. We have an in-depth explanation into child accounts here that you can check out.
Child accounts can be useful if you want a separate account for your customers, but you still want them to access your negotiated rates. The vice-versa is also true, if a customer wants to use your application, but would rather use their own negotiated rates. The flexibility of a child User allows you to provide limited and precise access to customers or 3rd parties that need to access your shipping application.
How do child users work on EasyPost?
A child User is an associated account that's linked to its parent account. Child accounts can help businesses support multiple end-users with their own set of carrier credentials. In essence, a child User is a clone of the master User, with some major exceptions. The child User will only get its own rates, which is the parent User's USPS account by default, and any carrier accounts that need to be associate with the specific child User. Please keep in mind, if you wish to associate any carrier account beyond the parent User's USPS account to the child User, you'll have to build that logic on your end.
You can only create a child User in production mode with your production API key. Read our API Documentation to learn more about child users.
How do I close my EasyPost account?
We’re sorry to see you go! To initiate the process of closing your account, submit a support ticket and we’ll get you started.