The EPISHIP API Endpoints provide comprehensive control over hardware integration and data reporting. You can develop applications that manage local print servers, automate label generation, and retrieve detailed business reports programmatically, bridging the gap between cloud-based shipping logic and physical hardware.
View Doc →
The following figure shows the relationship between your EPISHIP app, the EPISHIP API, and Hardware services.
Figure 1. EPISHIP API relationship diagram. Print server communication and report generation flow.
EPISHIP’s application layer serves as the control center for configuring physical devices. It allows administrators to define available printers, assign them to specific companies or users, and visualize data through generated reports.
The REST API that facilitates the CRUD (Create, Read, Update, Delete) operations for print servers and reports. It handles the logic for determining default printers based on user or company hierarchy.
Secured via Bearer tokens in the Authorization header, ensuring that hardware configurations and sensitive business reports are accessible only to authenticated entities.
A specialized set of endpoints designed to manage the software bridge between the API and local printers. This includes capabilities to download platform-specific software (Linux, Mac, Windows) and generate sample labels for testing.
Users can use the EPISHIP Endpoints API to perform common workflows, such as:
Properties available to view and filter through the EPISHIP Endpoints API:
