Zepto API Capability

Health check

Run a Zepto diagnostic across location, category, search and advertising surfaces.

Capability ID zepto.health

Cost From $1.25 per 1,000 requests · 1 credit

Maximum runtime 180 seconds

# Health check

Run a Zepto diagnostic across location, category, search and advertising surfaces.

- Platform: [Zepto](https://docs.upscrape.com/docs/platforms/zepto)
- Capability ID: `zepto.health`
- 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.health"
}'
```

## Input

Optionally provide a six-digit pincode or both latitude and longitude for the diagnostic context. Do not combine pincode with coordinates.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `latitude` | `number` | No | Latitude for location-based health check. From -90 to 90. |
| `longitude` | `number` | No | Longitude for location-based health check. 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`.

status and per-surface flags/counts describe this diagnostic execution. They are not an uptime SLA, a whole-catalogue availability guarantee or a replacement for checking the capability needed by your workflow.

first_error can identify the first diagnostic failure when one occurs.

### Illustrative sample output

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

```json
{
  "capabilities": {
    "ads": "ok",
    "categories": "ok",
    "location": "ok",
    "search": "ok"
  },
  "checked_at": "2026-09-24T09:55:32.428095465Z",
  "status": "ok"
}
```
### Illustrative output fields

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

| Path | Observed type | Example |
| --- | --- | --- |
| `capabilities` | `object` | 4 fields |
| `capabilities.ads` | `string` | ok |
| `capabilities.categories` | `string` | ok |
| `capabilities.location` | `string` | ok |
| `capabilities.search` | `string` | ok |
| `checked_at` | `string` | 2026-09-24T09:55:32.428095465Z |
| `status` | `string` | ok |

## 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)

POST /execute Shared execution endpoint

Input parameters

Optionally provide a six-digit pincode or both latitude and longitude for the diagnostic context. Do not combine pincode with coordinates.

latitude number optional

Latitude for location-based health check. From -90 to 90.

Example 12.96902

longitude number optional

Longitude for location-based health check. From -180 to 180.

Example 77.75395

pincode string optional

Six-digit Indian pincode. When provided, Upscrape resolves coordinates and the Zepto delivery store automatically.

Response

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

status and per-surface flags/counts describe this diagnostic execution. They are not an uptime SLA, a whole-catalogue availability guarantee or a replacement for checking the capability needed by your workflow.

first_error can identify the first diagnostic failure when one occurs.

Illustrative sample The example response is shown in the response panel.

Illustrative output fields

Values illustrate one response. Read the guidance above for missing values and limits; fields can vary with the requested operation and the data available.

Path	Observed type	Example
`capabilities`	`object`	4 fields
`capabilities.ads`	`string`	ok
`capabilities.categories`	`string`	ok
`capabilities.location`	`string`	ok
`capabilities.search`	`string`	ok
`checked_at`	`string`	2026-09-24T09:55:32.428095465Z
`status`	`string`	ok

Execution behavior

A 200 response completed inline. A 202 response was queued; poll GET /jobs/:id until the job reaches completed or failed.

Overview, pricing and sample data for every endpoint: Zepto API

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.health" }'

import json import os import requests payload = json.loads(r'''{ "input": { "latitude": 12.96902, "longitude": 77.75395 }, "capability": "zepto.health" }''') response = requests.post( "https://data.upscrape.com/execute", headers={ "Authorization": f"Bearer {os.environ['UPSCRAPE_API_KEY']}", "Content-Type": "application/json", "Prefer": "wait=30", }, json=payload, ) response.raise_for_status() print(json.dumps(response.json(), indent=2))