Drop Pincode Serviceability
By entering the drop_pincode, the enterprises can determine whether the Pincode is serviceable by any of their active carriers or not.
Overview
By entering the drop_pincode
, the enterprises can determine whether the Pincode is serviceable by any of their active carriers or not
The enterprise will be able to know which types of services are available for the particular drop-up Pincode or combination of pickup or drop pincode
They can know if COD
(Cash on Delivery), PREPAID
(payment done in advance) or EXCHANGE
(Deliver one good and take one good back to the warehouse) are serviceable or not by the carrier partner
-
Enterprises can use the serviceability API to trigger order creation/ order manifestation based on the API response
-
Lightweight API just to check whether the drop Pincode is serviceable or not. (If there are multiple warehouses, then pass the combination of pickup and drop pincode)
Usecase
This is a standard API which applies to all MPS (Multi-Piece Shipment) and SPS (Single Piece Shipment) orders
Geography
This is a standard API which supports all shipments created and transported within
- India
Note
Enterprise can put a check on the
serviceable
field which they get in the response from Clickpost
Note
If the enterprise does not pass the
service_type
field, then Clickpost will be assume it toFORWARD
shipment
Request Payload
Mandatory Field
Field Name | Data Type | Field | Description | Max Length | Example |
---|---|---|---|---|---|
drop_pincode | num | Mandatory | The drop pincode for which the serviceability needs to be ascertained | 6 char | 380001 |
optional
[optional parameters]
Field Name | Data Type | Field | Description | Max Length | Example |
---|---|---|---|---|---|
order_type | enum | Optional | The Order typeCOD or PREPAID | 10 | "COD" |
pickup_pincode | string | Optional | The pickup Pincode for which the serviceability needs to be ascertained | 6 char | "380015" |
service_type | enum | Optional | The order type for which serviceability needs to be determined. Enter FORWARD if the shipments need to be delivered to the customer from the enterprise's warehouse.Enter RVP if the shipment needs to picked up from the customer’s location and delivered to the enterprise’s warehouse.Enter EXCHANGE in case of exchange order | 10 | FORWARD |
Response
meta
[meta parameters]
Field Name | Data Type | Description | Example |
---|---|---|---|
success | Boolean | Indicates the success of the API request | true |
message | String | The message from Clickpost. In case of success, it will be "SUCCESS". In case there are no carrier partners that are servicing the pincodes it will be” Pincode not serviceable" | "SUCCESS" |
status | HTTP Code | The HTTP response status code of the API request | 200 |
result
[result parameters]
Field Name | Data Type | Description | Example |
---|---|---|---|
serviceable | Boolean | Whether the particular drop pincode is serviceable. Note: If the enterprise has multiple warehouse, then you need to pass the pickup_pincode | "380015" |
COD | Boolean | Field indicates whether Cash on Delivery is supported by the particular carrier to the particular pincode | true |
PREPAID | Boolean | Field indicates whether Prepaid is supported by the particular carrier to the particular pincode | true |
EXCHANGE | Boolean | Field indicates whether Exchange is supported by the particular carrier to the particular pincode | true |
{
"meta": {
"success": true,
"message": "SUCCESS",
"status": 200
},
"result": {
"serviceable": true,
"COD": false,
"PREPAID": true,
"EXCHANGE": false
}
}
Updated over 1 year ago