Skip to main content

Return Helper API

Return Helper provides a suite of APIs for managing e-commerce product returns end-to-end — from return request creation through shipment tracking, label generation, and warehouse processing.
The API is designed for server-to-server integration only. Do not call these endpoints directly from client-side code.

Available APIs

User API — Authenticated endpoints for merchants and partners to manage return requests, shipments, labels, inventory, and account settings. Public API — Reference data endpoints exposing lookup values such as service types, warehouse lists, status codes, and supported countries.

Authentication

All API requests require an API key and token passed as request headers:
x-rr-apikey: YOUR_API_KEY
x-rr-apitoken: YOUR_API_TOKEN
Content-Type: application/json
Getting your credentials:
  1. Log in to the Return Helper User Portal.
  2. Go to Settings → Signing Key and API Token.
  3. Your existing key-token pairs are listed here. You can also generate a new pair.
Your API token is private. Never share it or expose it in client-side code.

Base URLs

Sandbox

EndpointBase URL
User APIhttps://api.returnshelper.com/uat/user/api
Public APIhttps://api.returnshelper.com/uat/public/api

Production

EndpointBase URL
User APIhttps://api.returnhelpercentre.com/v1/user/api
User API (China)https://api.returnhelperchina.com/user/
Public APIhttps://api.returnhelpercentre.com/v1/public/api

Idempotency

For state-changing requests (creating return shipments, inventories, etc.), include an idempotency key to prevent duplicate operations in the event of network retries.
x-returnhelper-idempotency-key: YOUR_UNIQUE_KEY
Generate a fresh UUID (or similarly unique string) for each distinct transactional request. The server recognises repeated submissions of the same key and executes the operation only once, preserving data integrity.

User-Agent Header

Include a User-Agent header so Return Helper support can identify your integration when investigating issues:
User-Agent: {app name}/{app version} (Platform={os version}; Runtime={runtime version}; Language={language})
Example:
User-Agent: CompanyABCApi/2024.16.0 (Platform=Unix/13.4.0; Runtime=8.0.2; Language=CSharp12)
A full request header looks like:
x-rr-apikey: YOUR_API_KEY
x-rr-apitoken: YOUR_API_TOKEN
Content-Type: application/json
x-returnhelper-idempotency-key: YOUR_UNIQUE_KEY
User-Agent: YourApp/1.0.0 (Platform=Linux/5.15; Runtime=8.0.2; Language=CSharp12)

OpenAPI Specification

The full API specification is available as an OpenAPI 3.1 document. You can download it and import it directly into API clients such as Postman or Insomnia, or use it to generate client SDKs with tools like OpenAPI Generator.

Download OpenAPI Specification

openapi.json — OpenAPI 3.1

General Remarks

  • All dateTime parameters must be in ISO 8601 format, otherwise the API cannot parse them.
  • Date string parameters (e.g. createToStr, createFromStr) must also be ISO 8601; the time portion is ignored.
  • All timestamps returned by the API are in UTC.

Webhooks

Label results and warehouse events (shipment arrival, inventory creation, image uploads, etc.) are delivered asynchronously via webhook notifications. You must register a notification endpoint to receive these events. See the Webhooks section for the full list of notification event types and their payloads.