Skip to main content
Returns and support endpoints accept either customer authentication method described in Authentication. With a Customer access token, ticket and return actions also require x-partner-id; upload URL requests do not.
Examples on this page use a Customer access token. With the Partner API key and External user ID method, replace the Authorization and x-partner-id headers with x-api-key and x-external-user-id.

Evidence upload flow

Upload support and return images with signed URLs:
  1. Request signed URLs from Keystone.
  2. Upload each file with PUT to the returned uploadUrl.
  3. Send the returned publicUrl in imageUrls when creating the ticket or return.
Limits: Send each file’s sizeBytes when you request upload URLs. Keystone refuses a declared size over the limit, so check the file size before requesting a URL.

Create support upload URLs

Request:
Response:
Upload the file:

Create support ticket

Request:
Response:

List support tickets

Query parameters: Request:
Response:

Retrieve support ticket

Request:
Response shape is the same as a single item from the list response.

Create return upload URLs

Request:
Response:

Create return request

Returns require a delivered order. A prepaid order must also be paid; a COD order qualifies once it is delivered. Each requested quantity must not exceed the item’s remaining returnable quantity. COD orders cannot use ORIGINAL_PAYMENT_REFUND. Because it is the default, always send requestedResolution for COD returns, for example WALLET_CREDIT. Resolutions a customer can request: For mixed-tender orders, approved returns restore the applicable Reward Points and Wallet Cash. Any remaining original-payment amount is refunded through the payment provider when ORIGINAL_PAYMENT_REFUND is selected. Request:
Response:

List returns

Query parameters: Return statuses:
Request:
Response:

Retrieve return

Request:
Response shape is the same as the create return response.