Return Created
This REST API is used to notify the Partner when the return has been created in Uniware.
Tip
- The access token received in response is required in Header (Authorization) in all subsequent API requests.
- It is recommended to check out Notes for the reader. You might find this helpful as it contains Guidelines for using API references and Terminologies used here.
Basic Information
| NAME | DETAILS |
|---|---|
| BaseUrl: | https://{PartnerBaseUrl} |
| Endpoint: | /createReturn |
| Request Type: | POST |
| Scheme: | HTTPS |
| Header (Content-Type): | application/json |
| Header (Authorization): | token value(got from Authentication |
Request Payload
{
"SaleOrderCode": "5973531722035",
"ShippingPackageCode": "WEAR-46917",
"returnId": "RP-5600",
"status": "CREATED",
"returnReason": "size too big",
"type": "CUSTOMER_RETURN",
"createdOn": "Jul 18, 2024 6:47:10 PM",
"facilityCode": "wearcomet",
"orderItems": [
{
"orderItemId": "15126801449267",
"bundleIdentifier": null,
"skuCode": "CLSA03080",
"customFieldValues": [
]
}
],
"customFieldValues": [
]
}Request Payload Details
| LEVEL | PARAMETER | TYPE | DESCRIPTION | MANDATORY | NOTES |
|---|---|---|---|---|---|
| 1 | saleOrderCode | string | Sale order code | Yes | - |
| 2 | returnId | string | Return id | Yes | - |
| 3 | status | string | Return status | Yes | “CREATED” for CIR , “Return_AWAITED” for RTO |
| 4 | returnReason | string | Return reason | Yes | - |
| 5 | facilityCode | string | Uniwre warehouse code | Yes | - |
| 6 | type | string | Return type | Yes | “CUSTOMER_RETURN” for CIR or “RTO - Return To Origin” for RTO |
| 7 | createdOn | Date | date-time Eg: Feb 13, 2023 4:01:45 PM | Yes | - |
| 8 | customFields | object | Custom fields details | Opt | - |
| 9 | orderItems | object | Order Items details | Yes | - |
| 10 | orderItemId | string | OrderItems Ids | Yes | - |
| 11 | bundleIdentifier | string | Bundle Identifier | Yes | - |
| 12 | skuCode | string | SKU code | Yes | - |
| 13 | customFieldValues | object | Custom fields details | Opt | - |
| 14 | ShippingPackageCode | string | shippingPackage code | Condi | Only for type = “RTO - Return To Origin” for RTO |
Response Payload
{
"status": "Success",
"message": "Detail is updated successfully"
}Response Payload Details
| LEVEL | PARAMETER | TYPE | DESCRIPTION | MANDATORY | NOTES |
|---|---|---|---|---|---|
| 1 | status | string | Success after notification is acknowledged | Yes | Success/Failed |
| 2 | message | string | Readable response message | Yes | - |
Error Codes
Refer Response Codes section to know about specific errors codes.
FAQs/Notes
Q1. What would be that frequency of Notification push to partner?
Ans. Real-time or nearly real-time.