EPISHIP’s shipping interface utilizes this API to translate user selections into physical logistics documents. The UI leverages the API’s configuration data to populate accurate dropdowns for package types, thermal printer formats (like ZPL or EPL), and customs declarations. Once a label is generated, the app displays the tracking number, renders the PDF/image for printing, and can even display a map of nearby carrier drop-off locations.
The REST API acts as the orchestration layer between your system, the carrier networks, and secure cloud storage. When a label request is submitted, the API validates the data, communicates with carriers (via ShipmentLabelsService) to purchase the postage, and stores the resulting label securely in an Amazon S3 bucket, returning signed URLs for immediate download. It also supports Stripe integration to automatically capture payments for point-of-sale terminal transactions.
A unique, powerful feature of the label creation process is the application of RLD rules. Even if a user selects a specific premium service, the RLD engine evaluates the actual transit times. If a cheaper service is guaranteed to arrive within the same delivery window, the API automatically transforms the request, purchases the cheaper label, and returns both the rld_original_service and rld_transformed_service for auditing.
Users can use the EPISHIP Create Shipping Label API to perform common workflows, such as:
Label properties and parameters available through the EPISHIP Create Shipping Label API:
