# Resolve location

Resolve Zepto serviceability, store context and ETA fields from a six-digit Indian pincode or coordinates.

- Platform: [Zepto](https://docs.upscrape.com/docs/platforms/zepto)
- Capability ID: `zepto.location`
- Cost: 1 credit per request
- Maximum runtime: 180 seconds
- Execute endpoint: `POST https://data.upscrape.com/execute`

## Request

Use the exact public capability ID in the shared execute envelope.

```bash
curl --request POST \
  --url https://data.upscrape.com/execute \
  --header "Authorization: Bearer $UPSCRAPE_API_KEY" \
  --header "Content-Type: application/json" \
  --header "Prefer: wait=30" \
  --data '{
  "input": {
    "latitude": 12.96902,
    "longitude": 77.75395
  },
  "capability": "zepto.location"
}'
```

## Input

Provide either pincode or both latitude and longitude. Do not combine the two explicit location modes. Pincode must be a six-digit Indian postal code and is resolved to a matching delivery point before Zepto serviceability is checked.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `latitude` | `number` | No | Latitude of the delivery location. From -90 to 90. |
| `longitude` | `number` | No | Longitude of the delivery location. From -180 to 180. |
| `pincode` | `string` | No | Six-digit Indian pincode. When provided, Upscrape resolves coordinates and the Zepto delivery store automatically. |

### Example input

```json
{
  "latitude": 12.96902,
  "longitude": 77.75395
}
```

## Response

Successful output is returned in `results[0].data`.

Use location.serviceable and the returned store identifiers as delivery-context fields. ETA fields are observations for that resolved context; a missing estimate remains unknown and should not be substituted from another store.

Keep captured_at with the resolved location when using it to interpret catalogue, price or availability data.

### Illustrative sample output

This example shows one response. Values and optional fields vary with the data available.

```json
{
  "captured_at": "2026-09-24T09:54:33.228867228Z",
  "location": {
    "eta_minutes": 6,
    "eta_serviceable": true,
    "latitude": 12.96902,
    "longitude": 77.75395,
    "secondary_store_ids": [
      "0059ff6a-7eb0-477a-a7f5-69256f2c444b"
    ],
    "serviceable": true,
    "store_id": "b4dc8d65-ed2e-4142-81b6-373982b13500",
    "store_ids": [
      "b4dc8d65-ed2e-4142-81b6-373982b13500",
      "0059ff6a-7eb0-477a-a7f5-69256f2c444b"
    ]
  }
}
```
### Illustrative output fields

Derived from the sample above for orientation only. These fields are not a fixed response schema.

| Path | Observed type | Example |
| --- | --- | --- |
| `captured_at` | `string` | 2026-09-24T09:54:33.228867228Z |
| `location` | `object` | 8 fields |
| `location.eta_minutes` | `integer` | 6 |
| `location.eta_serviceable` | `boolean` | true |
| `location.latitude` | `number` | 12.96902 |
| `location.longitude` | `number` | 77.75395 |
| `location.secondary_store_ids` | `array` | 1 items |
| `location.serviceable` | `boolean` | true |
| `location.store_id` | `string` | b4dc8d65-ed2e-4142-81b6-373982b13500 |
| `location.store_ids` | `array` | 2 items |

## Execution behavior

A `200` response completed inline. A `202` response was queued; poll `GET /jobs/{id}` until the job reaches `completed` or `failed`. Use an `Idempotency-Key` when retrying must not create a duplicate logical job.

## Related documentation

- [Authentication](https://docs.upscrape.com/docs/api/authentication)
- [Jobs and results](https://docs.upscrape.com/docs/api/jobs)
- [Errors and retries](https://docs.upscrape.com/docs/api/errors)
- [Idempotency](https://docs.upscrape.com/docs/api/idempotency)