> ## 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.

# Get all return service types

Lists every **return service type** available to your account.

Return Helper has two distinct service-type catalogues:

* **Return service types** — carrier × service combinations used for **inbound** return shipments (customer → Return Helper warehouse) via [Create return shipment](/api-reference/returnshipment/create-return-shipment). All `/api/ServiceType/*` endpoints expose this catalogue.
* **Shipment service types** — used for **outbound** resend shipments (Return Helper warehouse → buyer) via [Create resend order](/api-reference/resend/create-resend-order). Exposed under `/api/ShipmentServiceType/*`.

This endpoint returns the full **return** catalogue, unfiltered. For resend services use [Get available shipment service types for warehouse](/api-reference/shipmentservicetype/get-available-shipment-service-types-for-warehouse) instead — they are not interchangeable.

## When to call

* During integration setup, to enumerate every return service your account is wired up for.
* When you do not yet know the origin country, destination country, or destination warehouse. For filtered lookups, prefer [Get service types by origin and destination countries](/api-reference/servicetype/get-service-types-by-origin-and-destination-countries) or [Get service types by origin country and warehouse](/api-reference/servicetype/get-service-types-by-origin-country-and-warehouse).

## Related

* [Get service types by origin and destination countries](/api-reference/servicetype/get-service-types-by-origin-and-destination-countries) — narrow by country pair (domestic or cross-border).
* [Get service types by origin country and warehouse](/api-reference/servicetype/get-service-types-by-origin-country-and-warehouse) — narrow by destination warehouse.
* [Get shipping fees from origin location](/api-reference/shipment/get-shipping-fees-from-origin-location) — same return catalogue, with fee estimates.
* [Create return shipment](/api-reference/returnshipment/create-return-shipment) — consumes the chosen `serviceTypeCode`.


## OpenAPI

````yaml get /api/ServiceType/getAllReturnServiceType
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/ServiceType/getAllReturnServiceType:
    get:
      tags:
        - ServiceType
      summary: Get all return service types
      operationId: ReturnUserApi_GetAllReturnServiceType
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: >-
                  #/components/schemas/GeneralUserAvailableReturnServiceTypeReply
        '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:
    GeneralUserAvailableReturnServiceTypeReply:
      type: object
      properties:
        data.availableReturnServiceTypeList:
          type: array
          items:
            $ref: '#/components/schemas/AvailableReturnServiceTypeReply'
          description: List of available return service types
    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'
    AvailableReturnServiceTypeReply:
      type: object
      properties:
        serviceTypeCode:
          type:
            - string
            - 'null'
          description: Service type code
        serviceType:
          type:
            - string
            - 'null'
          description: Service type display name
        fromCountryCode:
          type:
            - string
            - 'null'
          description: Origin country (lowercase ISO3)
        toCountryCode:
          type:
            - string
            - 'null'
          description: Destination country (lowercase ISO3)
    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

````