Features of connecting the ShipStation API
ShipStation is a convenient service aggregator for sending data about packages being prepared for shipment. So, if you use, for example, FedEx, DHL, APC or other shipping services and want all of them to be collected in one place, then ShipStation is what you need.
In your personal account, you must already have accounts of the necessary delivery services and link them to your ShipStation account.
You need to understand that support is provided for general shipping methods, which are already huge, but if you have any special individual conditions with a delivery service, these conditions will not be taken into account in ShipStation.
As in the the Payoneer API, the ShipStation API is a JSON API using the popular request signing method with passing the header "Authorization" with the value 'Basic'. base64_encode ("$id:$key"), where $id and $key are provided to the developer by ShipStation.
If you are interested in the idea of using ShipStation as an aggregator for your service, but you do not know what its features are, then everything is also very simple.
The service works with two types of dimensions - centimeters and inches, and three types of weight - grams, ounces, and pounds. For the passed parameters of the package, you can get the shipping costs of different delivery methods from different services and choose the appropriate one. Thus, it is an excellent tool for saving money on sending packages. In addition, different packaging methods are taken into account, which introduces additional variability in the choice of service and delivery method.
An important plus is the receipt of pdf-labels online for printing and gluing on the package. This release you from unnecessary waiting when visiting points of the delivery services and significantly saves time.
All API entities, such as users, orders, and packages, are separated, and thanks to this, making requests becomes convenient, which every API cannot boast of.
Each of the delivery services in reality has its own nuances, which in a sense is displayed on the ShipStation API. This can be observed, for example, when working with packaging types when choosing FedEx, but this is revealed only at the stage of connecting the API itself. Therefore, to process the data of some delivery services, you need to add some additional conditions. However, as for the rest, ShipStation API is a qualitatively universalized service, the connection of which often eliminates the need to connect the API of different delivery services, which saves development time.
A convenient error return system based on HTTP status codes only helps the client code developer to properly handle unforeseen errors.
ShipStation API has a limit of 40 requests per minute for one API account. More use requires an individual agreement with ShipStation, and only this moment, to some extent, can be an obstacle between you and your future highly loaded service using the ShipStation API.