Returns via API
As part of Global-e's comprehensive solution, Global-e delivers a Returns Portal branded with the merchant logo and theme as well as a unique URL to access your Returns Portal.
Merchants who have their own returns portal and third-party return portals can use Global-e Return APIs to integrate functionality for Global-e return shipping options, as well as to obtain required return documents and manage tracking information.
For further information, please consult the pre-integrated third party returns providers list.
For a new third-party integration please contact your representative at Global-e.
Functional documentation
Global-e Return API’s are designed to provide a comprehensive solution for the return flow.
Global-e Return APIs
GetReturnShippingOptions API - Used to receive a list of return shipping methods available for a specific order and its associated costs.
GetReturnDocuments API - Used to receive return documents and related information, including the label, the tracking number, the tracking URL, the shipper’s name, the commercial invoice (if relevant), the RMA number, and the return note.
GetTrackingEvents API - Used to receive status events on the delivery status of an order/return.
High-level flow
Following is the recommended high-level workflow for the product(s) return process.
Shopper initiates a return, usually using an Order ID and an Email.
Shopper selects the return product(s) and the reason(s) for his return.
Returns Portal calls GetReturnShippingOptions API to receive a list of available return shipping methods and their associated prices configured on Global-e.
Returns Portal displays the available return shipping methods.
The return shipping price received from Global-e via the API can be overridden by the Returns Portal.
Additional refund\credit methods, such as store credit, can be offered to the shopper.
Once the shopper selects the desired return shipping method, the Returns Portal calls GetReturnDocuments API to generate a Global-e RMA and receive all the required return documents.
Global-e returns all the required documents as a single PDF file including tracking information, if relevant.
Returns Portal shows a confirmation page indicating the return was issued with the documents available for download.
Global-e sends an RMA email - a return request confirmation email - to the shopper with the relevant documents attached.
The RMA email can be disabled on the Global-e side and managed by the Returns Portal. To disable it please refer to your Global-e representative.
Shopper ships the return package using the return documents.
Optional: the Returns Portal calls the Tracking Events API to get all the tracking events for a given tracking number. (Not all returns are trackable)
Based on the merchant policy, the shopper should be refunded for the returned items (after shipping cost deduction). The merchant portal can use standard Global-e functionality with web portal, pre-integrated webhooks, or Refund APIs.
Integrated Returns Portal
Following is a list of pre-integrated third party returns providers.
Returns Provider | Integrated APIs | Supported Functionalities | Further Information |
---|---|---|---|
BabackVision | Returns with:
| ||
ChapsVision | Returns with:
| ||
EasyCom | Returns with:
| ||
Loop |
| ||
ParcelLab | Returns with:
|
GetReturnShippingOptions (Merchant to Global-e)
The Return Shipping Options API provides essential return information, including a list of return shipping methods and costs.
Important
Global-e must enable and configure this API on the Global-e side.
Method/URL
POST https://{globale_api_domain}/Return/GetReturnShippingOptions
Parameters
Request
Parameter Name | Type | Description | Mandatory |
---|---|---|---|
| String | 10-character code. Default is EN Maximum: 10 characters. | No |
| String | The currency of the return prepaid shipping cost. This is a 3-char ISO currency code. The default should be the same as the origin order currency. If the submitted order currency is not the same as the (outbound) order, apply the currency exchange. | No |
| String | Email that identifies the source of the request. | No |
| String | Unique Global-e Order ID or Merchant Order ID. Maximum: 100 characters. | Yes |
| String | Provider name that identifies the source of the request. | Yes |
| Array of | The following fields should be populated:
| Yes |
| Long | Provides the ID of the return shipping method. | No |
Response
Parameter Name | Type | Description | Mandatory |
---|---|---|---|
| Double | The cost of the shipment | Yes |
| String | 3-letter currency ISO code | Yes |
| String | Whether this is a label-free return (QR code only). | No |
| String | Identifies whether this is a trackable return. | Yes |
| String | The unique merchant Order ID. Maximum: 100 characters | Yes |
| String | The unique Global-e Order ID. Maximum: 100 characters | Yes |
| Object | The Contains the following values:
| Yes |
| Array of |
| Yes |
| String | Description of the shipping method. | Yes |
| Integer | The shipping method identifier. Can be used when calling GetReturnDocuments to receive the return document for the selected shipping method. | Yes |
| String | Identifies the shipping method type. | Yes |
| Integer | Possible values:
Can be used when calling GetReturnDocuments to receive the return document for the selected shipping method. | Yes |
| String | The name of the shipping service of the return provider | Yes |
Errors
General Error Response
{ "Code": "error code", "Error": "error message", "Description: "error description" }
Error Codes
Code | Message |
---|---|
E01 | Could not find an available shipping method (No shipping method was found for the submitted products and quantities) |
E02 | Return is not allowed due to order status % (Relates to Allowed Return Statuses) |
E03 | Order ID not found (Returned if the provided OrderId cannot be found for the merchant) |
E04 | Currency is not valid |
E05 | There are multiple orders with this |
E06 | The |
ME01 | Input value for |
ME02 | Input value for |
ME03 | Input value for |
ME06 | Input value for |
ME07 | Input value for |
ME09 | Input value for |
ME10 | Input value for |
ME12 | Input value for |
ME13 | Input value for |
SME15 | Input value for |
Product Errors
Examples
Examples
Request
{ "ProviderCode": "ExampleProvider", "OrderId": "EUQA6215359", "Email": [email protected], "ReturnedProducts": [ { "ProductCode": "433117270672", "ReturnQuantity": 1 } ] }
Response
{ "IsSuccess": true, "Data": { "OrderId": "GE10470948238NL", "MerchantOrderId": "EUQA6215359", "ReturnShippingMethods": [ { "ShippingMethodId": 40044878, "ShippingMethodDescription": "DHL-GlobalE", "ShippingMethodType": "Express Courier (Air)", "ShippingMethodTypeID": 2, "ShipperName": "DHL", "IsQrLabel": false, "IsTrackable": true, "Cost": 0.0, "Currency": "EUR" } ], "ReturnShippingDestinationDetails": { "Country": "Netherlands", "City": "Amsterdam", "Address": "Ood 5", "Zip": "4751XK", "StateOrProvince": "", "Email": [email protected], "Phone": "310610887191" } }
GetReturnDocuments (Merchant to Global-e)
Use the GetReturnDocuments API to integrate the return documents capability into your Returns Portal or through a third party returns provider.
Important
Global-e enables and configures this API on the Global-e side.
The API provides return documents and related information, including:
The label
The tracking number
The tracking URL
The shipper's name
The commercial invoice (if relevant)
The return merchandise authorization (RMA) number
The return note
In addition, as part of the process, Global-e produces a Global-e RMA.
If so requested by a merchant, Global-e can configure whether to send RMA letters to customers and whether to disable sending RMA information to the merchant. Electronic invoices are not returned.
Method/URL
POST https://{globale_api_domain}/Return/GetReturnDocuments
Parameters
Request
Field | Type | Description | Mandatory |
---|---|---|---|
| String | The currency of the returned prepaid shipping cost. 3-character ISO code. | Mandatory if ShippingCost has a greater value than 0. |
| String | The language for the Return Note document. 3-character ISO code. Currently, English is the only supported language. | No |
| String | The customer's email address. Maximum 100 characters. | No |
| Boolean | Indicates if return is created for service | No |
| String | The Merchant's internal return merchandise authorization (RMA) Number. Maximum 200 characters. | No |
| String | Then unique Order ID. Maximum 100 characters. | Yes |
| String | The provider's name identifies the source of the request. | Yes |
| Object | The merchant hub delivery address with return details. | No |
| Array | An array containing the returned products' details. Contains array of ReturnedProduct objects:
| Yes |
| Integer | Based on the end customer's selected shipping method, as returned in the Get Return Shipping Options response. If empty, Global-e uses the cheapest method based on the return shipping type ID (or self-postage if configured) | No |
| Integer | Possible values:
| No |
| Decimal | The prepaid shipping cost associated with the return. If not provided, then the ShippingCost will be the configured prepaid/flat return rate. | No |
Response
When the API call is successful, the call returns the documents required for the return process.
Name | Type | Description |
---|---|---|
| Boolean | True: If the API call is successful. False: If the API call fails. |
| Object | Data regarding the return, including:
|
Errors
Error Codes
Code | Message |
---|---|
E01 | Could not create the shipping label. (Note: Not applicable to the self-postage option.) |
E02 | The return is not allowed due to the order status ({0}) (Global-e can enable the E02 error code and validate the order status through configuration.) |
E03 | The Order ID was not found |
E04 | There is already an RMA request for this order ({0}) |
E07 | The return is not allowed due to the parcel status ({0}). |
E08 | Unable to find the shipping method for the provided return shipping method Id ({0}) |
E09 | The provided |
E10 | There are multiple orders with this Order ID ({0}) |
E11 | No shipping options were found for the order return ({0}) |
E12 | The return shipping address was not found for order ({0}) |
E13 | Invalid currency code for the provided shipping cost for order ({0}) |
E14 | The return shipping cost cannot be a negative number |
E15 | The return shipping cost is greater than the return product price |
E16 | Return address country code is not valid |
E17 | Return address state code is not valid or does not belong to the country |
E18 | Return address country is not allowed for given order |
E19 |
|
E20 |
|
Product Errors
Model Validation Errors
Code | Message |
---|---|
ME01 | The input value for |
ME02 | The input value for |
ME03 | The input value for |
ME04 | The input value for |
ME05 | The input value for |
ME06 | The input value for |
ME07 | The input value for |
ME08 | The input value for |
ME09 | The input value for |
ME10 | The input value for |
ME11 | The input value for |
ME12 | The input value for |
ME13 | The input value for |
ME14 | The input value for |
ME15 | The input value for |
ME16 | "Input value for |
ME17 | Input value for |
ME19 | Input value for |
ME20 | Input value for |
ME21 | Input value for |
ME22 | Input value for |
ME23 | Input value for |
ME24 | Input value for |
ME25 | Input value for |
ME26 | Input value for |
ME27 | Input value for |
ME28 | Input value for |
ME29 | Input value for |
ME30 | Input value for |
ME31 | Input value for |
ME32 | Input value for |
ME33 | Input value for |
Examples
Request
curl --location 'https://[globale domain]/Return/GetReturnDocuments' \ --header 'MerchantGUID: D2ED2A7F-F6ED-4CCB-B611-B44AC8D02250' \ --header 'Content-Type: application/json' \ --data-raw '{ "ProviderCode": "Loop", "OrderId": "GE314856569TS", "Email": "[email protected]", "MerchantRMANumber": "RM132", "ShippingCost": 10.0, "CurrencyCode": "USD", "ReturnShippingTypeId": 2, "ReturnShippingMethodId": null, "ReturnedProducts": [ { "ProductCode": "DKB500680.M8", "CartItemId": null, "ReturnQuantity": 1, "MerchantReturnReasonCode": "", "MerchantReturnReasonDescription": "Return Reason from GRD request for product 1" }, { "ProductCode": "B7ECS.C8", "CartItemId": 1, "ReturnQuantity": 1, "MerchantReturnReasonCode": "TTT", "MerchantReturnReasonDescription": "Return Reason from GRD request for product 2" } ] }'
Responses
Success
{ "IsSuccess": true, "Data": { "OrderId": "GE314856569TS", "MerchantOrderId": "314856569", "GlobaleRmaNumber": "371104", "ReturnTrackingDetails": { "TrackingNumber": "1ZXXXXXXXXXXXXXXXX", "TrackingURL": "https://wwwapps.ups.com/tracking/tracking.cgi?tracknum=1ZX&requester=ST/", "IsQrLabel": "false", "IsTrackable": true }, "ReturnDocuments": [ { "DocumentTypeCode": "ShippingLabel", "DocumentTypeName": "Shipping Label", "DocumentData": "AQCkosNhECNeAACYzH/NIA5NgtHU2QAAAABJRU5ErkJggg==", "URL": "https://[MerchantDomain]/url" } ] }, }
Failure
{ "Code": "error code", "Error": "error message", "Description: "error description" }
Example 1
"IsSuccess": false, "Errors": [ { "Code": "E500", "Error": "We encountered an unexpected error and are working to resolve the issue”, "Description": null, "Success": false } ] }
Example 2
{ "IsSuccess": false, "Errors": [ { "Code": "PE27", "Error": "Return products collection has duplication", "Description": null, "Success": false }, { "Code": "PE07", "Error": "Return product (DKB500680.M8) was not found for order", "Description": null, "Success": false }, { "Code": "PE07", "Error": "Return product (B7ECS.C8) was not found for order", "Description": null, "Success": false } ] }
Tracking Events API
Prerequisites
The request can include a list of global-e order IDs, a list of tracking events, or both, but all the same type: Inbound or Outbound. Each request can report on either inbound orders or outbound, but not both. For requesting inbound and outbound tracking events, two different requests should be issued.
GetTrackingEvents (Merchant to Global-e)
The Get Tracking Events API lets you receive status events on the delivery status of an order. Reporting of tracking events allows both our customers and 3rd parties to stay informed about the exact location and status of returned items throughout the entire external return journey.
With that, having tracking events for return shipments allows to trigger refunds automatically upon confirmation of returned item receipt (or any other tracking event).
The API accepts one or more order ID numbers, up to 100, on a single call, a list of either orders moved to forward shipments, after checkout completion (outbound), or returns (inbound) and returns their status.
Method/URL:
POST https://{globale_api_domain}/Shipment/GetTrackingEvents
Parameters
Request
Parameter Name | Type | Description | Mandatory |
---|---|---|---|
| DateTime | Date and time for the earliest time of the order shipment status, UTC, in RFC 2822 format (for example, Fri, 8 Aug 2014 17:13:07 +0000). | No |
| List of Strings | List of Global‑e Order IDs. Up to 100 in each request. Note: each Max length:100 chars. | One of either |
| List of Strings | List of Global‑e tracking numbers. Up to 100 in each request, with prefix | Conditional |
| String | The shipment direction. One of the following:
| Yes |
Response
Parameter Name | Type | Description | Mandatory |
---|---|---|---|
| List of | List of objects containing detailed error information. The object includes:
| |
| Object | The events for each
|
Global-e Tracking Events
The following table lists all the tracking events reported by Global-e:
GlobaleEventCode | GlobaleEventDescription |
---|---|
1 | The parcel has been created but is waiting to be manifested (i.e. despatched) |
2 | The parcel has been manifested (i.e.. despatched) |
3 | The carrier has yet to receive the parcel into their network |
4 | The carrier has acknowledged receipt of the parcel into their network |
5 | The carrier has acknowledged receipt of the parcel into their network but did not receive the required electronic manifest (pre advice file) |
6 | A collection request has been acknowledged by the carrier |
7 | The carrier has successfully collected a parcel from a customer |
8 | The carrier has failed to collect a parcel from a customer |
9 | The parcel has been misrouted by the carrier due to incorrect routing on the label |
10 | The parcel has been misrouted by the carrier due to incorrect routing on the label |
11 | The parcel has been advised as lost within the carriers network |
12 | The parcel has been delayed due to factors beyond the carriers control (i.e. inclement weather) |
13 | The parcel is with Customs (NR: This does not necessarily mean that the parcel has been refused entry into the destination country) |
14 | The parcel has been damaged |
15 | The parcel is in transit (NB: This could either be en route to a country hubs delivery depot) |
16 | The parcel has been Left at the local post office for collection |
17 | The parcel is with a 3rd party sub-contractor and a tracking event has occurred (refer to "Confirmation' field for further information if provided |
18 | The parcel has left the delivery depot for the recipients address |
19 | The parcel has been received by a sub-contractor 3rd party |
20 | The carrier has a query concerning the recipients address (i.e. Unable to locate,. incorrect post code etc.) |
21 | The carrier has left a calling card for the customer as they were unable to deliver the parcel |
22 | The carrier has delivered part of the consignment advised (e.g. Parcel 1 parcel of a 2 parcel consignment has been delivered) |
23 | The parcel is available to collect from the carriers premises |
24 | The parcel is being held at the delivery depot |
25 | The recipient no longer resides at the delivery address |
26 | The recipient refused to take delivery of the parcel |
27 | The parcel is to be returned to the sender |
28 | The carrier was unable to deliver the parcel (No reason specified) |
29 | The parcel has been successfully delivered |
30 | The carrier has provided some information concerning the parcel |
31 | An event has occurred after the parcel has been delivered / lost or RTS (i.e._ acknowledgement of a claim) |
32 | Special delivery instructions to app.? |
33 | The delivery / collection has requested to be cancelled |
34 | The carrier has received an electronic pre advice (manifest) for this parcel |
35 | The parcel has been at a bstatus that does not set an actual or default end date and as such has been 'closed" after a certain period of time dependent on the environment it belongs to |
36 | The parcel was miss sorted by the carrier and sent to the incorrect -deliver? dept. |
37 | The recipient has arranged a delivery with the carrier |
38 | The carrier attempted to deliver the parcel but was unable to access the recipients address to deliver or leave a inning card (i.e. Closed office building, gate-d development etc) |
39 | The payment for cash on delivery could not be collected |
40 | The recipient's identification failed |
41 | The payment could not be processed due to an invalid method of payment by recipient. |
42 | The payment for cash on delivery of parcel has been collected by the carrier |
43 | The parcel has been cleared for delivery |
44 | The parcel has been re boxed / re packed |
45 | The parcel has been requested to be disposed |
46 | The declared weight of the parcel does not match the actual weight of the parcel. |
47 | The parcel has been held by destination Customs |
48 | The parcel has been held by origin Customs |
49 | The parcel has been delivered to a neighbour's address |
50 | The parcel has been delivered to a safe place suggested by the recipient |
51 | The customer has collected the parcel from the store |
52 | The parcel is received at store and is ready for collection by recipient_ |
53 | The parcel is ready for collection at the store and it has not been collected after a period of time |
54 | The parcel has been delivered to a locker or collection point and is ready to be collected by the recipient. |
55 | The parcel has been delivered to the recipient's preferred point instead of collecting from depot or re-delivery or return |
56 | The package has been held by the carrier whilst collecting recipient details for clearance |
57 | The parcel has been re-labelled |
58 | The parcel attributes lie outside of service capability, i.e. weight/size/remote area issues |
59 | An SMS has been transmitted to the recipient to inform that the parcel is out for deliver). today |
60 | An email has been transmitted to the recipient to inform that the parcel is out for delivery today |
61 | The carrier attempted delivering the parcel but could not deliver |
62 | The package/s arrived to the destination country |
63 | A choice that the customer has made for delivery to a safe place (the delivery not happened yet) |
Error Codes
Code | Message |
---|---|
E01 | The shipment ({0}) is not trackable with this shipper |
E02 | The order ({0}) is not trackable with this shipper |
E03 | The provided tracking number ({0}) was not found |
E04 | The provided order ID ({0}) was not found |
E05 | The order ({0}) is not associated to the merchant |
E06 | The tracking number ({0}) is not associated to the merchant |
E07 | The order ({0}) doesn't have a tracking number |
E08 | The tracking event type parameter is invalid |
E10 | The number of input values (Tracking Number and Order IDs) exceeded the ({0}) limit |
E11 | At least one Order ID or Tracking Number should be specified |
Examples
Request
Request for only Global-e orders:
curl --location 'https://[globale domain]/Shipment/GetTrackingEvents' \ --header 'MerchantGUID: D2ED2A7F-F6ED-4CCB-B611-B44AC8D02250' \ { "EventSinceInUTC": "2025-04-01T20:08:05Z", "Type": "outbound", "OrderIds": [ "GE381652418TS" ], "TrackingNumbers":[ ]}
Response
{ "Data": { "SuccessfulTrackingNumbers": [ { "GlobaleOrderID": "GE381652418US", "MerchantOrderID": "#22165241", "GlobaleParcelCode": "null", "GlobaleRMANumber": "2832849023948", "MerchantRMANumber": "832849932893", "IsTrackingNumberActive": true, "TrackingNumber": "GE381652418TS2864637A0", "Type": "outbound", "TrackingUrl": "https://mailingtechnology.com/tracking/?tn=GE381652418TS2864637A0", "ShipperName": "Spring XBS Packet Registered-GlobalE", "TrackingEvents": [ { "ShipperEventDescription": "The parcel has been created but is waiting to be manifested (i.e. despatched)", "TrackingEventDateTimeInUTC": "2024-03-24T09:19:08", "GlobaleEventCode": "1", "GlobaleEventDescription": "The parcel has been created but is waiting to be manifested (i.e. despatched)", "ShipperEventCode": "0", "TrackingEventStatus": [], "Location": { "FullAddress": "BALTIMORE AIRPORT,MD-USA" } } ] }, { "GlobaleOrderID": "GE8770052418US", "MerchantOrderID": "#23816524", "GlobaleParcelCode": "null", "GlobaleRMANumber": "0239283284948", "MerchantRMANumber": "8884994993293", "IsTrackingNumberActive": true, "TrackingNumber": "GE381652418TS2864637A0", "Type": "outbound", "TrackingUrl": "https://mailingtechnology.com/tracking/?tn=GE381652418TS2864637A0", "ShipperName": "Spring XBS Packet Registered-GlobalE", "TrackingEvents": [ { "ShipperEventDescription": "The parcel has been created but is waiting to be manifested (i.e. despatched)", "TrackingEventDateTimeInUTC": "2024-03-24T09:19:16", "GlobaleEventCode": "1", "GlobaleEventDescription": "The parcel has been created but is waiting to be manifested (i.e. despatched)", "ShipperEventCode": "0", "TrackingEventStatus": [], "Location": { "FullAddress": "BALTIMORE AIRPORT,MD-USA" } } ] } ], "FailedTrackingNumbers": [ { "OrderId": "ABC123", "TrackingNumber": "123", "ErrorInfo": { "Code": "E06", "Error": "The tracking number (123) is not associated with the merchant", "Description": null }, "Success": false } ] }, "Errors": null }