# Get Serviceability for Pickup and Drop Pincode

This API validates shipping feasibility between a **pickup pincode** and a **delivery pincode**.\
It determines:

* Available shipping services
* Supported payment modes (Prepaid / COD)
* Reverse pickup availability
* Estimated delivery timelines
* Shipping zone

### Endpoint

**Method:** `POST`\
**URL:**

```
https://{accountSlug}.myeshopbox.com/api/v1/checkpincodeserviceability
```

### Request Body

| Attribute         | Type   | Description                                          | Mandatory |
| ----------------- | ------ | ---------------------------------------------------- | --------- |
| `deliveryPincode` | string | 6-digit postal code of the customer delivery address | Yes       |
| `pickupPincode`   | number | Postal code of the warehouse or fulfillment center   | Yes       |

### Sample Request

```bash
curl --location 'https://{accountSlug}.myeshopbox.com/api/v1/checkpincodeserviceability' \
--header 'Content-Type: application/json' \
--data '{
    "deliveryPincode": "122003",
    "pickupPincode": "121001"
}'
```

***

### Response Attributes

#### Serviceability Object (`data[]`)

<table><thead><tr><th width="164.67449951171875">Attribute</th><th width="146.2265625">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>type</code></td><td>string</td><td>Shipping service type (e.g. Eshopbox standard, Eshopbox express, Eshopbox prime)</td></tr><tr><td><code>isPickup</code></td><td>string</td><td><code>"1"</code> if reverse pickup is available, otherwise <code>"0"</code></td></tr><tr><td><code>isCOD</code></td><td>string</td><td><code>"1"</code> if Cash on Delivery is supported, otherwise <code>"0"</code></td></tr><tr><td><code>isPrepaid</code></td><td>string</td><td><code>"1"</code> if Prepaid payment is supported, otherwise <code>"0"</code></td></tr><tr><td><code>etd</code></td><td>string</td><td>Estimated delivery date or time window</td></tr><tr><td><code>index</code></td><td>integer</td><td>Priority ranking of the service (lower value = higher priority)</td></tr></tbody></table>

#### Root-Level Attributes

| Attribute | Type   | Description                                                               |
| --------- | ------ | ------------------------------------------------------------------------- |
| `zone`    | string | Shipping zone classification (e.g. Local, Zonal, National, Remote, Metro) |

***

### Success Response (200 OK)

```json
{
    "data": [
        {
            "type": "Eshopbox standard",
            "isPickup": "1",
            "isCOD": "1",
            "isPrepaid": "1",
            "index": 1,
            "etd": "19 Jan, 2026"
        },
        {
            "type": "Eshopbox express",
            "isPickup": "1",
            "isCOD": "1",
            "isPrepaid": "1",
            "index": 2,
            "etd": "17 Jan, 2026"
        },
        {
            "type": "Eshopbox prime",
            "isPickup": "0",
            "isCOD": "0",
            "isPrepaid": "0",
            "index": 3,
            "etd": ""
        }
    ],
    "zone": "National"
}
```

***

### Error Responses

| Status Code | Description                                |
| ----------- | ------------------------------------------ |
| `200`       | Serviceability data retrieved successfully |
| `400`       | Invalid or missing pincode in request body |

***

### Notes

* Multiple service types may be returned for the same pickup–delivery pincode pair.
* Clients should use the `index` field to identify the recommended service.
* An empty `etd` indicates the service is currently unavailable for that route.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://eshop.gitbook.io/eshopbox-developers/advanced/pincode-serviceability-api/get-serviceability-for-pickup-and-drop-pincode.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.