> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.returnhelper.com/llms.txt
> Use this file to discover all available pages before exploring further.
# 按目的地获取 Resend Shipping Fees
此页面由 AI 自动翻译。API 技术规格以英文呈现为标准。如有任何疑问，请参阅[英文版本](/api-reference/resend/get-resend-shipping-fees-by-destination)。
针对一个或多个要寄往指定目的地（国家 + 邮编）的退货库存项目，返回可用的 **Resend**（出库）服务类型，并**附带费用估算**。可用于在调用 [创建 Resend Order](/zh-Hans/api-reference/resend/create-resend-order) 之前预览 Resend 费用。
本端点仅估算 **Resend**（出库）运送费用。若要预览 **Return**（入库）费用，请改用 [按起始位置获取 Shipping Fees](/zh-Hans/api-reference/shipment/get-shipping-fees-from-origin-location)。
必要参数
* **`returnInventoryIdList`** — 必填。以逗号分隔的退货库存 ID 列表（例如 `10023,10024`），代表要一并重寄的项目。**所有 ID 必须属于同一个 Warehouse**，且每个都必须存在，否则请求会验证失败。
* **`toCountryCode`** — 必填，**小写 ISO3**（例如 `usa`、`gbr`）。有效值请参阅 [获取所有国家](/zh-Hans/api-reference/country/get-all-countries)。
* **`toPostalCode`** — 必填，且不可为空。
* **`limit`** — 选填。限制返回的服务类型选项数量；省略时会返回该目的地所有可用选项。
响应说明
每一条项目描述一种可用的 Resend 服务类型与其费用：
* `serviceTypeCode` / `serviceTypeName` — 服务标识符与其显示名称。
* `isEnableAutoCreateLabel` — 以此服务创建 Resend Order 时是否自动生成面单。
* `postalCodePair` — 用于推算费率的 `from` / `to` 邮编区间配对。
* `currencyCode` 与 `fee` — 估算的费用。
* `chargeableWeight` — 承运商实际计费的重量，可能因体积重量进位而高于包裹的实际重量。
列表为空表示该库存组合与目的地没有可用的 Resend 服务。费用为估算值；最终费用于创建 Resend Order 时套用。
* [创建 Resend Order](/zh-Hans/api-reference/resend/create-resend-order) — 使用所选的 `serviceTypeCode`。
* [获取 重寄订单 详情](/zh-Hans/api-reference/resend/get-resend-order-details) — 创建后查看 Resend Order。
* [按起始位置获取 Shipping Fees](/zh-Hans/api-reference/shipment/get-shipping-fees-from-origin-location) — Return（入库）费用预览的对应端点。
## OpenAPI
````yaml get /api/Resend/getShippingFeeListByToShippingOption
openapi: 3.1.0
info:
title: Return Helper API
description: API documentation for Return Helper — covering User and Public endpoints.
version: 1.0.0
servers:
- url: https://api.returnshelper.com/uat/user
description: Sandbox — User API
- url: https://api.returnshelper.com/uat/public
description: Sandbox — Public API
- url: https://api.returnhelpercentre.com/v1/user
description: Production — User API
- url: https://api.returnhelpercentre.com/v1/public
description: Production — Public API
- url: https://api.returnhelperchina.com/user
description: Production — User API (China)
security:
- ApiKey: []
ApiToken: []
paths:
/api/Resend/getShippingFeeListByToShippingOption:
get:
tags:
- Resend
summary: Get resend shipping fees by destination
operationId: ReturnUserApi_GetShippingFeeListByToShippingOption
parameters:
- name: returnInventoryIdList
in: query
required: true
schema:
type: string
description: >-
Comma-separated list of return inventory IDs to price the resend
for. All IDs must belong to the same warehouse.
- name: toCountryCode
in: query
required: true
schema:
type: string
description: ISO3 destination country code
- name: toPostalCode
in: query
required: true
schema:
type: string
description: Destination postal code
- name: limit
in: query
required: false
schema:
type: integer
format: int32
minimum: 0
description: Maximum number of service-type fee options to return
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: >-
#/components/schemas/GeneralList_ShipmentShippingFeeDetailReply
'401':
description: >-
Authentication failed. Returned when the `x-rr-apikey` or
`x-rr-apitoken` header is missing or invalid. The body uses the
standard `ApiResponse` envelope with `meta.error.message` describing
the auth failure.
content:
application/json:
schema:
$ref: '#/components/schemas/ApiResponse'
security:
- ApiKey: []
ApiToken: []
servers:
- url: https://api.returnshelper.com/uat/user
description: Sandbox — User API
components:
schemas:
GeneralList_ShipmentShippingFeeDetailReply:
type: object
properties:
data:
type: array
items:
$ref: '#/components/schemas/ShipmentShippingFeeDetailReply'
description: List of available resend service types with their shipping fee
ApiResponse:
type: object
description: >-
Universal response envelope. Successful responses include the business
payload as additional top-level fields alongside `correlationId` and
`meta`. Failed responses (auth errors, validation errors) only populate
`correlationId` and `meta`, with `meta.errorCode` and `meta.error`
describing the failure.
properties:
correlationId:
type:
- string
- 'null'
description: >-
Unique correlation ID for tracing the request through Return Helper
systems.
meta:
$ref: '#/components/schemas/ApiResponseMeta'
ShipmentShippingFeeDetailReply:
type: object
properties:
serviceTypeCode:
type:
- string
- 'null'
serviceTypeName:
type:
- string
- 'null'
isEnableAutoCreateLabel:
type: boolean
postalCodePair:
type: object
description: Postal-code zone pair used to derive the rate
properties:
from:
type:
- string
- 'null'
description: Origin postal-code zone
to:
type:
- string
- 'null'
description: Destination postal-code zone
currencyCode:
type:
- string
- 'null'
fee:
type: number
format: decimal
chargeableWeight:
type: number
format: decimal
ApiResponseMeta:
type: object
description: >-
Application-level metadata for every API response. Inspect `status` and
`errorCode` to detect soft-error responses (validation failures arrive
as HTTP 200 with `meta.status: 400`).
properties:
status:
type: integer
description: >-
Application-level status code. For successful operations this
mirrors the HTTP status (e.g. 200). For validation failures it
reports the logical status (e.g. 400) even though the wire HTTP
status is 200.
data:
type: object
additionalProperties:
type: string
description: Reserved free-form metadata key/value pairs. Usually empty.
errorCode:
type:
- string
- 'null'
description: >-
Machine-readable error code (e.g. `VALIDATION_FAILED`). Non-null
only when the operation failed.
error:
type: object
additionalProperties: true
description: >-
Field-level or message-level error detail keyed by request property
name. Empty object on success.
securitySchemes:
ApiKey:
type: apiKey
in: header
name: x-rr-apikey
description: Your API key
ApiToken:
type: apiKey
in: header
name: x-rr-apitoken
description: Your API token — keep this private
````