> ## 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-Hant/api-reference/resend/create-resend-order) 之前預覽 Resend 費用。
本端點僅估算 **Resend**（出庫）運送費用。若要預覽 **Return**（入庫）費用，請改用 [依起始位置取得 Shipping Fees](/zh-Hant/api-reference/shipment/get-shipping-fees-from-origin-location)。
必要參數
* **`returnInventoryIdList`** — 必填。以逗號分隔的退貨庫存 ID 清單（例如 `10023,10024`），代表要一併重寄的項目。**所有 ID 必須屬於同一個 Warehouse**，且每個都必須存在，否則請求會驗證失敗。
* **`toCountryCode`** — 必填，**小寫 ISO3**（例如 `usa`、`gbr`）。有效值請參閱 [取得所有國家](/zh-Hant/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-Hant/api-reference/resend/create-resend-order) — 使用所選的 `serviceTypeCode`。
* [取得 重寄訂單 詳情](/zh-Hant/api-reference/resend/get-resend-order-details) — 建立後檢視 Resend Order。
* [依起始位置取得 Shipping Fees](/zh-Hant/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
````