EASYSHIPPINGX API

一个 API,完成
比价、选价
与下单。
One API to
compare rates
and create shipments.

预览并下载3PL/API 验收空表与假设样例。Preview and download the 3PL/API acceptance blank and sample.

多家服务商,按你的需求选择。Multiple services. Your choice.

一次请求,获取账户下适用于这票包裹的报价。选择最低有效价格,或选择你需要的服务商,再从自己的系统创建订单。Get available quotes for your shipment in one request. Choose the lowest returned price or the service you prefer, then create the shipment from your own system.

  • 多服务商比价Compare available rates
  • 自动判断覆盖Coverage checked for you
  • 自主选择服务Stay in control
一个包裹通过统一接口连接多个配送服务选项
一次接入,让每票包裹多一些选择。One integration. More choice for every shipment.
按你的规则选价YOUR SHIPMENT. YOUR RULES.

最低价优先,
也可以自己选。
Pick the lowest rate.
Or pick your service.

从本次返回的可用报价中,选择最符合需求的一项。你可以在接入系统中按价格选择,也可以指定服务商。Choose from the quotes available for this shipment. Your integration can select by price, or use the service you prefer.

  • 在同币种有效报价中比较价格。Compare valid quotes in the same currency.
  • 无有效价格的选项不参与选择。Options without a valid price stay out of the selection.
  • 由你的系统选定服务,再调用创建订单接口。Your system selects the service, then calls the order API.

试着选择服务 B,或点击“选择最低报价”。Try selecting Service B, or choose the lowest quote.

同一票包裹ONE SHIPMENT

你的报价选项Your rate options

示例数据Example data
选择示例服务商Choose an example service
已选服务YOUR SELECTION

服务 AService AUSD 3.71

下一步:使用服务 A 创建订单。Next: create your order with Service A.

仅为交互示例,不获取实时报价或创建订单。实际报价取决于包裹信息与账户可用服务。Interactive example only. No live rates are requested and no orders are created. Actual quotes depend on shipment details and enabled services.

包裹和目的地经过可用性判断,形成可选服务
可用报价Available quotes无报价,不参与选择No quote, no selection
覆盖判断交给接口COVERAGE, TAKEN CARE OF

不用再逐个检查
服务商的邮编覆盖。
Skip the ZIP-code
guesswork.

提供收件地址和包裹信息,接口会判断渠道是否适用。某个区域服务商无法覆盖目的地时,就不会产生可供选择的有效价格。Send the recipient address and parcel details. The API checks service eligibility. If a regional service cannot cover the destination, it will not produce a valid price to choose.

无需在自己的系统中维护每家服务商的邮编覆盖表。直接围绕返回的有效报价,决定这票包裹怎么发。You do not need to maintain a separate ZIP coverage list for each service. Make your shipping decision from the valid quotes returned.

覆盖是可用条件之一。包裹规格、账户分配渠道及所需服务选项,也会影响能否获得报价。Coverage is one eligibility check. Parcel specifications, enabled channels and required service options also affect quote availability.

从报价到订单FROM QUOTE TO ORDER

三个步骤,接入你的发货流程。Three steps. One connected workflow.

适用于有开发资源的电商团队、3PL,以及 ERP、OMS 和 WMS 平台。For eCommerce teams, 3PLs, and ERP, OMS or WMS platforms with development resources.

  1. 01

    获取可用报价Get available quotes

    提交同一票包裹的地址、尺寸与重量,查询单个、多个或账户下全部已分配渠道。Send the address, dimensions and weight. Request one channel, several, or all channels assigned to your account.

    输入一次包裹信息One set of shipment details
  2. 02

    选择合适的服务Choose your service

    在有效报价中比较价格。由你的系统选最低报价,或按需要指定服务商。Compare valid quotes. Let your integration choose the lowest returned price, or select the service you need.

    选价规则由你决定Your selection rules
  3. 03

    创建订单Create the order

    沿用这票包裹的信息,提交选定渠道创建订单,保存返回的运单编码,衔接后续处理。Use the same shipment details with the selected channel to create the order. Save the returned shipment code for the next steps.

    从选择进入履约Move from choice to fulfillment
为开发团队准备FOR YOUR DEVELOPERS

两个接口,衔接比价与下单。Two endpoints to connect the flow.

服务端通过 Api-Token 鉴权,以 JSON 发送请求。以下是简化的字段示例,完整要求请查看 API 文档。Authenticate server-side with Api-Token and send JSON requests. These simplified examples show the field structure; consult the API documentation for full requirements.

POST/v1/order/quotation

先获取报价Start with a quote

express 为字符串时查询单个渠道,数组查询多个渠道;设为 null 时查询账户已分配渠道。Use a string for one channel, an array for several, or null for all channels assigned to your account.

{
  "order_id": "DEMO-10001",
  "express": null,
  "parcel": {
    "length": 20, "width": 15,
    "height": 10, "weight": 0.5
  },
  "ship_to": {
    "firstname": "Demo",
    "country": "US", "state": "CA",
    "city": "Los Angeles", "zip": "90001",
    "address1": "123 Example Street"
  }
}
查看简化报价响应View a simplified quote response
[
  {
    "express": "service_a",
    "price": 3.71,
    "price_currency": "USD",
    "weight": 0.5,
    "weight_unit": "kg",
    "surcharge": { "total": 0 }
  },
  {
    "express": "service_b",
    "price": 3.99,
    "price_currency": "USD",
    "weight": 0.5,
    "weight_unit": "kg",
    "surcharge": { "total": 0 }
  }
]

多渠道响应中,不可用项可能返回 price: null 和 reason。只在有效、同币种的报价中比较价格。Unavailable entries in a multi-channel response may include price: null and reason. Compare only valid quotes in the same currency.

POST/v1/order

再提交选定渠道Create with your chosen channel

将选定的渠道编码作为字符串写入 express,沿用包裹信息并补齐该渠道要求的服务选项。Pass the selected channel code as a string in express. Reuse the shipment details and include any options required by that channel.

{
  "order_id": "DEMO-10001",
  "express": "service_a",
  "parcel": {
    "length": 20, "width": 15,
    "height": 10, "weight": 0.5
  },
  "ship_to": {
    "firstname": "Demo",
    "country": "US", "state": "CA",
    "city": "Los Angeles", "zip": "90001",
    "address1": "123 Example Street"
  }
}
查看简化创建响应View a simplified order response
{
  "data": {
    "order_id": "DEMO-10001",
    "shipment_code": "DEMO-SHIPMENT-10001",
    "price": 3.71,
    "price_currency": "USD",
    "surcharge": { "total": 0 }
  }
}

保存 data.shipment_code。tracking_number 仅在创建时已提供追踪号的情况下返回;后续面单获取流程以文档为准。Save data.shipment_code. A tracking_number is returned only if provided during creation. Follow the documentation for subsequent label retrieval.

请求约定Request conventions请求头:Content-Type: application/json、Api-Token: YOUR_TOKEN。尺寸使用 cm,重量使用 kg;创建订单时使用唯一的 order_id。Headers: Content-Type: application/json and Api-Token: YOUR_TOKEN. Dimensions use cm, weight uses kg; use a unique order_id when creating an order.

示例说明About these examples渠道编码、地址、订单号、凭证和金额均为演示值。请替换为有效信息及账户实际分配的渠道;部分渠道需要额外字段。报价为预估,不代表最终账单金额。Channel codes, addresses, references, credentials and amounts are illustrative. Replace them with valid details and your assigned channels; some channels require additional fields. Quotes are estimates, not a guarantee of final billed charges.

准备开始接入?Ready to start integrating?

查看完整参数与渠道要求。需要文档访问或接入帮助时,请在费率申请表的“补充信息”中说明。Explore full field definitions and channel requirements. For documentation access or integration help, add your needs to the rate request form’s Additional Information field.

面向实际发货流程BUILT AROUND YOUR SHIPPING WORKFLOW

海外仓与 3PL 接入评估API onboarding for warehouses and 3PLs

先提交发货仓 ZIP、订单重量及尺寸分布、目的地区域、账户要求和当前 WMS/OMS 对接方式。用相同样本验证可用报价、服务选择、创建订单返回值及错误恢复,再决定自动化范围。报价成功不等于订单创建成功。Start with origin ZIPs, weight and dimension distribution, destinations, account requirements, and your WMS/OMS connection. Test available quotes, service selection, order responses, and error recovery on the same sample before defining automation scope. A successful quote is not a created shipment.

3PL 多客户发货3PL operations

3PL 可先验证同一包裹在不同客户账户下的报价与订单归属。A 3PL can first test pricing and order ownership across client accounts.

4PL 多仓协同4PL coordination

4PL 应按仓库确认执行方、凭证与恢复责任。A 4PL should identify execution, credential, and recovery owners per warehouse.

大型品牌履约Brand fulfillment

大型品牌应核对 OMS/WMS 订单、退货和账单之间的关联。Large brands should verify OMS/WMS orders, returns, and invoice relationships.

客户隔离、白标、webhook、财务字段及测试环境都是需核验的接入要求,不由本页示例推定已开放。Client isolation, white-label output, webhooks, finance fields, and test environments are onboarding requirements to confirm, not capabilities established by these examples.

EasyShippingX 本页承接美国境内运输与 API。头程、进口清关及仓储由客户或其伙伴负责;承运商可接收的产品、账户、起运地点与交接方式需另行确认。EasyShippingX supports U.S. domestic transportation and API onboarding on this page. Customers or their partners handle international transport, import clearance, and warehousing. Confirm the enabled product, account, origin, and tender arrangement separately.

本页用于评估 EasyShippingX 产品与申请接入;Shipping API 技术指南解释流程与开发边界,3PL API 评估指南帮助核对多客户需求。服务开放范围与交接安排须在账户接入时确认。Use this page to evaluate EasyShippingX and request onboarding. The Shipping API technical guide explains development boundaries, and the 3PL API evaluation guide covers multi-client requirements. Confirm enabled services and tender arrangements during account onboarding.

用验收结果确定接入范围Define onboarding scope through acceptance evidence

评估任务Evaluation task需要验证What to validate业务通过条件Business acceptance condition
可用报价Available quotes用相同起运、目的地、实重、尺寸和商品样本取得实际响应;记录账户、服务与报价时间。Use matching origin, destination, packed weight, dimensions, and contents; retain account, service, response, and quote time.有可用报价才进入服务选择;无结果、无资格和请求失败应分别处理。Select a service only from available quotes; distinguish no results, ineligibility, and request failure.
创建订单Create shipments按现有文档传递所选报价及订单数据,核对响应、业务标识、面单与客户订单的关联。Pass the selected quote and order data using current documentation; verify responses, identifiers, and the relationship between labels and client orders.报价成功不代表创建成功;按实际接口合同核对状态,不以页面示例推定功能。A successful quote is not a created shipment; verify state against the actual API contract rather than inferring capabilities from examples.
异常恢复Exception recovery测试无效参数、权限、超时、重复操作以及恢复后的状态查询;重复策略先与接入团队确认。Test invalid inputs, permissions, timeouts, repeated actions, and state checks after recovery; confirm retry rules with onboarding.能识别已发生的业务动作并保留人工处理路径,避免未经核验的重复创建。Identify actions already performed and retain a manual recovery path to avoid unverified duplicate creation.
履约与账单Fulfillment and billing将仓库交接、首扫、轨迹、异常和最终费用映射回原订单,确认实际可开放的数据与责任人。Map tender, first scan, tracking, exceptions, and final charges to the original order; confirm available data and responsible owners.按门户或 API 的已开通能力分阶段验收;多客户隔离、通知和财务字段作为接入需求逐项确认。Accept enabled Portal/API capabilities in stages; confirm multi-client separation, notifications, and finance fields as individual onboarding requirements.

建议先准备一份脱敏样本和一页接入清单:仓库 ZIP、包裹画像、月单量、当前系统、客户归属和上线范围。门户与 API 分阶段接入帮助选择起点,WMS/API 验收指南帮助组织开发测试。现有营销插图与请求示例用于说明流程,正式字段和可用服务以当前接口文档及账户确认结果为准。Prepare a redacted sample and a one-page checklist covering warehouse ZIPs, parcel profiles, monthly volume, current systems, client ownership, and launch scope. Phased Portal/API onboarding helps select a starting point; the WMS/API acceptance guide supports development tests. Existing marketing illustrations and request examples explain the workflow; use current API documentation and account confirmation for production fields and service availability.

商务评估先申请费率评估,开发团队再按 技术指南与当前接口文档核对字段,最后 申请接入讨论。Start procurement with a request a rate review, have engineering check fields against the technical guide and current API documentation, then request an onboarding discussion.

本节为 EasyShippingX 的采购与接入评估建议,复核日期:2026-10-30。公开资料、保留文件与账户开通状态需要分别核验,示例不构成真实报价或客户成果。EasyShippingX procurement and onboarding recommendations, reviewed 2026-10-30. Verify public references, retained files, and account activation separately; examples are not customer results or actual quotes.

常见问题A FEW MORE DETAILS

接入前,
你可能想了解。
Good questions.
Clear answers.

需要自行检查区域服务商的邮编覆盖吗?Do I need to check regional ZIP coverage myself?

不需要自行维护覆盖表。提交收件地址与包裹信息后,接口会判断适用性。无法覆盖的服务不会产生有效报价;包裹规格、账户渠道和服务选项也会影响报价可用性。You do not need to maintain your own coverage lists. The API checks eligibility from the address and parcel details. A service that cannot cover the destination will not produce a valid quote. Parcel specifications, enabled channels and service options also affect availability.

可以自动选择最低价格吗?Can my integration choose the lowest price?

可以在你的系统中,对本次返回的同币种有效报价进行比较,选择最低价格,再把对应渠道提交给创建订单接口。报价接口本身不会替你创建订单,也不保证全市场最低价。Your system can compare valid quotes in the same currency, select the lowest returned price, and submit that channel to the order API. The quotation endpoint does not create an order for you or guarantee the lowest price across the entire market.

可以指定服务商,而不是选择最低价吗?Can I choose a specific service instead?

可以。你可以查询指定的单个或多个渠道,再从有效报价中选择所需服务。创建订单时,传入选定的渠道编码,而不是价格数字。Yes. Request one or more specific channels and select the service you need from valid quotes. When creating an order, pass the selected channel code, not the quoted price.

报价是否就是最终账单金额?Is the quote the final billed amount?

报价基于提交信息预估费用与计费重量。实际计费可能受到包裹信息、适用费率及附加费影响,且报价中的附加费明细未必列出所有项目;请以适用价卡与最终账单为准。A quote estimates price and billable weight from the submitted details. Actual billing can depend on parcel information, applicable rates and surcharges. The surcharge breakdown may not list every item; refer to the applicable rate sheet and final invoice.

如何开始测试?How do we start testing?

请先提交费率申请,并在“补充信息”中注明 API 接入、测试或技术支持需求,以便确认可用渠道与后续安排。获得测试配置后,先验证报价、服务选择和创建订单流程。测试地址为 https://test-api.easyshippingx.com。Submit a rate request and describe your API integration, testing or support needs in Additional Information so we can confirm available channels and next steps. Once testing is set up, validate quotation, service selection and order creation. Test base URL: https://test-api.easyshippingx.com.

EASYSHIPPINGX API

让每票包裹,都有更合适的选择。Give every shipment a better choice.

申请配送费率,并在“补充信息”中告诉我们你的 API 接入、测试或技术支持需求。Request shipping rates and tell us about your API integration, testing or support needs in Additional Information.

3PL/API 接入验收表3PL/API acceptance worksheet

公开预览与下载,无需留资。空表有相同字段与五行待填写记录;已填样例均为假设数据。用上文的字段契约、错误恢复和验收流程逐项替换需求、预期结果、证据、负责人及状态。Preview and download without a form. The blank has the same columns and five fillable records; every completed sample row is hypothetical. Use the field contract, recovery, and acceptance workflow to replace requirements, expected results, evidence, owners, and status.

表格可左右滑动。Scroll horizontally to review all columns.

3PL/API 接入验收表,全部为假设记录3PL/API acceptance worksheet, hypothetical records only
记录类型Record type验收编号Test ID需求Requirement预期结果Expected result证据Evidence负责人Owner状态Status
假设样例HypotheticalAPI-01API-01租户与账户映射Tenant and account mapping客户 A 订单归属账户 A;客户 B 不可读取Tenant A orders remain in account A; tenant B cannot read themMOCK-ACCOUNT-A-BMOCK-ACCOUNT-A-B示例技术负责人Example technical owner模拟验证通过Passed in mock
假设样例HypotheticalAPI-02API-02地址与包裹单位Address and parcel units映射起运地、目的地、重量单位、尺寸单位及服务字段Map origin/destination, weight unit, dimension unit and service fieldsMOCK-FIELD-MAP-01MOCK-FIELD-MAP-01示例接入负责人Example integration owner模拟验证通过Passed in mock
假设样例HypotheticalAPI-03API-03可用服务与报价快照Eligible service and quote snapshot保留可用服务、币种、报价时间及请求引用Retain available service, currency, quote timestamp and request referenceMOCK-QUOTE-01MOCK-QUOTE-01示例运营负责人Example operations owner模拟验证通过Passed in mock
假设样例HypotheticalAPI-04API-04建单超时与重复恢复Create timeout and duplicate recovery重试前查询原引用,防止第二次购买Query the original reference before retrying; prevent a second purchaseMOCK-TIMEOUT-01MOCK-TIMEOUT-01示例技术负责人Example technical owner模拟验证通过Passed in mock
假设样例HypotheticalAPI-05API-05校验错误与恢复Validation errors and recovery显示字段错误,修正输入并记录有界重试路径Show the field error; correct inputs and record a bounded retry pathMOCK-ERROR-01MOCK-ERROR-01示例接入负责人Example integration owner模拟验证通过Passed in mock
假设样例HypotheticalAPI-06API-06面单与轨迹映射Label and tracking mapping关联订单、运单、客户单号及支持的面单格式Link order, shipment, customer tracking number and supported label formatMOCK-LABEL-01MOCK-LABEL-01示例仓库负责人Example warehouse owner模拟验证通过Passed in mock
假设样例HypotheticalAPI-07API-07事件重放或轮询恢复Event replay or polling recovery验证配置的事件/轮询路径并对重复事件去重Validate configured event/polling path and deduplicate repeated eventsMOCK-EVENT-01MOCK-EVENT-01示例技术负责人Example technical owner待账户确认Needs account confirmation
假设样例HypotheticalAPI-08API-08取消、费用与对账Void, charges and reconciliation按单票及币种匹配报价、账单费用、调整和贷项Match quote, billed charges, adjustments and credits by shipment and currencyMOCK-INVOICE-01MOCK-INVOICE-01示例财务负责人Example finance owner模拟验证通过Passed in mock
假设样例HypotheticalAPI-09API-09试运行与回退Pilot and rollback记录试单范围、未决事项、备用方案及上线负责人Record pilot scope, unresolved items, fallback and named launch ownerMOCK-PILOT-01MOCK-PILOT-01示例上线负责人Example launch owner待试运行Pending pilot

“模拟验证通过”只描述这份假设样例;事件/轮询方案仍待账户确认,试运行尚未完成。模板不是对所有账户提供 webhook、取消或其他能力的承诺;每项以当前文档与实际响应确认。“Passed in mock” describes this hypothetical sample only. Event/polling setup still needs account confirmation, and the pilot remains open. The template does not promise webhooks, voids, or other capabilities on every account; validate each against current documentation and actual responses.

EasyShippingX 团队 · 模板与页面一致性核验:2026-10-30。编制依据:3PL API 选型指南、WMS/API 集成验收及当前接口文档入口。具体字段与账户能力在联调时复核。EasyShippingX team · Template/page consistency checked October 30, 2026. Based on the 3PL API selection guide, WMS/API acceptance guide, and current API documentation entry. Recheck exact fields and account capabilities during integration.