来自 Shopee 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存，可追溯
- 官方原文可核对
资料正文
§1 Significant OpenAPI Updates of Order and Logistics
Dear Developers
Please find below the OpenAPI updates released this time. These changes aim to enhance functionality, improve flexibility, and provide better integration support.
§2 1. Support Auto Call Driver for Instant Delivery Channels in ID, MY, VN, TH Markets
To enhance Shopee's instant delivery timeliness, optimize seller fulfillment efficiency, and enhance buyer experience, Shopee will gradually roll out the "Auto Call Driver" feature for instant delivery channels in the ID, MY, VN, TH markets.
This feature allows the system to automatically arrange shipment and trigger driver dispatch while the seller is preparing the package. Once the package is ready, the system will immediately trigger driver dispatch without any manual operation.
To help sellers obtain related dispatch information via Open API and optimize order processing flows, the v2.order.get_package_detail API will be upgraded with the following changes:
- Add new “preparation_end_time” response parameter under package_list:
| Name | Type | Description |
|---|---|---|
| package_list | object[] | / |
| >>preparation_end_time | timestamp | The system-calculated deadline for package preparation. When the package fulfillment_status/logistics_status changes to "LOGISTICS_READY", the system calculates this time based on the "Preparation Time" configured for the logistics channel of this package. Notes: 1) Only effective for logistics channels that have Auto Call Driver enabled and Preparation Time configured. 2) Seller needs to complete packing and waybill printing before this time to ensure the package is ready when the driver arrives. 3) When this time is reached, the system will automatically arrange shipment and trigger driver dispatch: - If driver calling is successful, the package fulfillment_status/logistics_status will change from “LOGISTICS_READY” to “LOGISTICS_REQUEST_CREATED”. - If driver calling fails, the package fulfillment_status/logistics_status will remain unchanged, and the seller must arrange shipment manually. |
- Add new “driver_info” response parameter under package_list:
| Name | Type | Descriptiom |
|---|---|---|
| package_list | object[] | / |
| >>driver_info | object | After the driver is successfully called, the driver's information will be returned. Note: Data availability depends on the specific 3PL provider; certain fields may be omitted due to provider policies, PII restrictions, or data unavailability. |
| >>driver_name | string | Driver name |
| >>driver_phone | string | Driver phone number |
| >>vehicle_type | string | Delivery vehicle type |
| >>license_plate | string | License plate number |
| >>courier_photo | string | URL of the driver’s photo |
| >>eta_start_time | timestamp | Earliest estimated arrival time at pickup address |
| >>eta_end_time | timestamp | Latest estimated arrival time at pickup address |
| >>driver_status | string | Driver status. Applicable values: - Allocating Driver - Driver assigned - Driver is on the way - Driver is arrived |
Notes:
-
Currently, Auto Call Driver and Preparation Time cannot be configured via Open API. Sellers must configure them in Seller Center → Shipping Channel Setting page.
-
After switching the Auto Call Driver toggle, there may be up to 10 minutes cache delay:
- When turning ON: Only packages that become “LOGISTICS_READY” after the switch takes effect will be auto-dispatched. Packages already in “LOGISTICS_READY” before that still require manual shipment.
- When turning OFF: Packages that become “LOGISTICS_READY” after the switch takes effect will require manual shipment. Packages that became “LOGISTICS_READY” before that may still trigger auto-dispatch.
Please complete the integration with the updated v2.order.get_package_detail API as soon as possible to avoid any impact on the sellers’ fulfillment process.
Related APIs:
v2.order.get_package_detail
Effective Date on Live:
2026.02.27
§3 2. Update on Warehouse and Pickup Address Return Limit
- Update Details
To better support multi-warehouse sellers in retrieving complete warehouse and pickup address information, and to prevent shipment disruptions caused by incomplete address data, the platform has increased the maximum number of warehouses and pickup addresses returned by the following APIs from 30 to up to 600:
- v2.shop.get_warehouse_detail
- v2.logistics.get_shipping_parameter
- v2.logistics.get_mass_shipping_parameter
- Developer Recommendations
Please note that the platform may further adjust this limit based on future business requirements.
To ensure service stability and compatibility, developers are advised to review and properly configure the following:
- Response size validation thresholds
- API request timeout settings
This helps prevent requests from being truncated or timing out due to large response payloads.
尊敬的开发者
请查收本次的 OpenAPI 功能更新。这些改动旨在提升功能灵活性、优化使用体验，并为集成提供更好的支持。
§4 1. ID, MY, VN, TH 市场的即时配送渠道支持“Auto Call Driver”
为提升 Shopee 即时配送时效，优化卖家履约效率与买家体验，平台即将针对 ID, MY, VN, TH 市场的即时配送渠道逐步推出 “Auto Call Driver” (自动呼叫司机) 功能。
该功能可在卖家准备订单期间自动发货并调度配送司机，实现订单准备就绪后立即触发派单，无需手动操作。为支持卖家通过 Open API 获取相关调度信息，优化订单处理流程，本次对 v2.order.get_package_detail 接口进行适配升级，具体更新内容如下：
- package_list 下新增 preparation_end_time 响应参数：
| Name | Type | Description |
|---|---|---|
| package_list | object[] | / |
| >>preparation_end_time | timestamp | 系统计算的包裹准备完成截止时间。 当包裹的履约状态 (fulfillment_status / logistics_status) 变为 “LOGISTICS_READY” 后， 系统基于卖家为该包裹所属物流渠道配置的 “Preparation Time” 叠加计算得出。 注意： 1) 仅针对已开启 “Auto Call Driver” 开关并且设置 “Preparation Time” 的物流渠道生效。 2) 卖家需在该时间点前完成包裹打包与贴面单等操作，确保司机到达时包裹已准备就绪。 3) 达到该时间点，系统将自动发货并调度配送司机： - 如果呼叫司机成功，包裹的履约状态将从 “LOGISTICS_READY” 变为 “LOGISTICS_REQUEST_CREATED”； - 如果呼叫司机失败，包裹的履约状态将保持不变，卖家仍需手动安排发货。 |
- package_list 下新增 driver_info 响应参数：
| Name | Type | Descriptiom |
|---|---|---|
| package_list | object[] | / |
| >>driver_info | object | 呼叫司机成功后，将返回司机信息。 注意：数据可用性取决于具体的第三方物流服务商 (3PL)； 由于服务商政策、个人身份信息 (PII) 限制或数据暂不可用等原因，部分字段可能会被省略。 |
| >>driver_name | string | 司机姓名 |
| >>driver_phone | string | 司机联系电话 |
| >>vehicle_type | string | 配送车辆类型 |
| >>license_plate | string | 车牌号码 |
| >>courier_photo | string | 司机照片URL |
| >>eta_start_time | timestamp | 司机预计到达取货地址的最早时间2 |
| >>eta_end_time | timestamp | 司机预计到达取货地址的最晚时间 |
| >>driver_status | string | 司机状态，枚举值如下： - Allocating Driver - Driver assigned - Driver is on the way - Driver is arrived |
注意：
-
目前暂不支持通过 Open API 配置物流渠道的 “Auto Call Driver” 开关及其 “Preparation Time”，卖家需通过卖家中心的 Shipping Channel Setting 页面进行配置。
-
Auto Call Driver 开关切换后，存在最多 10 分钟的缓存延迟：
- 开关开启：开关正式开启后变为 “LOGISTICS_READY” 状态的包裹将自动发货，在此之前已处于 “LOGISTICS_READY” 状态的包裹，卖家仍需手动安排发货；
- 开关关闭：开关正式关闭后变为 “LOGISTICS_READY” 状态的包裹需手动安排发货，在此之前变为 “LOGISTICS_READY” 状态的包裹仍可能触发自动发货。
请尽快完成对 v2.order.get_package_detail 接口的更新对接，以避免对卖家履约流程造成影响。
影响接口：
v2.order.get_package_detail
上线时间：
2026.02.27
§5 2. 仓库及取货地址返回数量限制更新
- v2.shop.get_warehouse_detail
- v2.logistics.get_shipping_parameter
- v2.logistics.get_mass_shipping_parameter
- 开发者建议
注意：平台后续可能会根据业务需求对该上限进行进一步调整。
为保障您的服务稳定性与兼容性，建议您检查并合理配置以下内容：
- Response Size 的校验阈值
- 接口调用的超时时间设置
以避免因响应体过大导致请求被截断或超时。