Get Courier Recommendation
Outbound | POST | /shipping-label/get-courier-recommendation
Summary
This API is used to make the get courier recommendation call to Logistic Aggregator and return the recommended couriers.
Description
This API is used to make the get courier recommendation call to Logistic Aggregator and return the recommended couriers that can be used to assign awb for the shipment. When this call is made to the logistic aggregator, based on the rule engine at logistic aggregator’s end, the recommended couriers are returned with priorities, and the same is forwarded by RMS.
Sample Request Payload
{
"pickupPincode": "560102",
"dropPincode": "110019",
"deliveryType": "FORWARD",
"invoiceValue": 1200,
"isCod": true,
"weight": 10
}
Parameter Name | Data Type | Description | Mandatory |
| String | Pincode from where shipment is to be picked | yes |
| String | Pincode of area where shipment is to be delivered | yes |
| String | Can be FORWARD or RETURN, based on the order type | yes |
| Double | The total amount in invoice | no |
| Boolean | Whether the order has Cash-on-delivery or not | yes |
| Double | Total weight of the shipment. Although, weight is not a mandatory field, Clickpost’s recommendation engine decides courier priority on the weight of the shipment too. For Clickpost, it will be in grams and for Shiprocket, it will be in kgs. | no |
Sample Response Payload
{
"courierData": [
{
"courierId": 1001,
"courierName": "Delhivery",
"priority": 1
},
{
"courierId": 1002,
"courierName": "Fedex",
"priority": 2
}
]
}
Parameter Name | Data Type | Description | Mandatory |
| Object | Data of the couriers that are available | yes |
| String | Id of the courier configured in Clickpost/Shiprocket | yes |
| String | Name of the courier | yes |
| Integer | Priority of the courier as per Clickpost/ Shiprockets recommendation engine. | yes |