EasyParcel API

Quick Summary To get your EasyParcel API key, log into your EasyParcel SG account, navigate to Integrations > Add New Store, and click on API Key. Choose between an Individual API (for single-store owners) or a Marketplace API (for ...

Quick Summary The main difference lies in account ownership and billing control. The Individual API is designed for sole website owners where one main account manages all bookings and shipping fees. In contrast, the Marketplace API is ...

Quick Summary Yes, EasyParcel SG provides a Sandbox (Demo) Environment for developers to safely test API integrations without incurring charges or creating real shipments. By using the dedicated Sandbox Base URL, you can simulate the e...

Quick Summary To obtain sandbox credit for API testing, you must first access the EasyParcel SG integration dashboard and switch to the demo environment. Because sandbox transactions are simulated, you can request free test credits by ...

Quick Summary If your AWB number or tracking link returns as blank in the EasyParcel SG API response after payment, it is typically due to a temporary delay in the courier's system generating the label. To resolve this, wait a few ...

Quick Summary Yes, orders submitted via the EasyParcel SG API will automatically expire if payment is not completed promptly, typically on the same day or once the collection date passes. Expired orders cannot be retrieved or paid, as...

Quick Summary Price differences between the EasyParcel SG portal and the API often occur because the portal automatically applies your active top-up package (such as VIP or Premier rates) based on your login, whereas the API might defa...

Quick Summary Some couriers display drop-off as an available service without immediately listing locations because the service availability and the physical station data are managed through separate, dynamic databases. To view active l...

Quick Summary The EasyParcel SG API supports a maximum of 300 parcels per single bulk request for endpoints like EPSubmitOrderBulk and EPPayOrderBulk. This limit is designed to maintain optimal processing speeds and prevent server time...

Quick Summary The exclude_fields parameter in the EPRateCheckingBulk endpoint is designed to remove specific data fields (like drop-off points) from the response payload, but it cannot be used to filter or exclude specific courier comp...