# Shipt API

> Shipt store categories and category products (unverified)

- Vendor: `shiptapi` · version 1.0 · category E-commerce · tags shipt api, shipt grocery api, shipt products api, shipt search api, grocery delivery api, target shipt api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/shiptapi
- This document: https://apiclay.com/docs/shiptapi.md
- OpenAPI 3.1: https://apiclay.com/api/shiptapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `shiptapi`
- Updated: 2026-11-18

## About

## Shipt API

Shipt's store category facets, subcategories and category product listings (48 per page) for a retailer location.

Data comes from **shipt.com** (https://www.shipt.com). Every route below calls the site's own endpoint directly and returns the upstream response unchanged.

Typical flow: `/menus` -&gt; `/categories` -&gt; `/products`

A Shipt store is identified by three numbers: store (retailer) id, metro id and store location id, e.g. `27`, `56`, `6794`.

### Routes

#### POST `/menus` - Menus (store categories)
Top-level categories of a store location.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| zip | body (JSON) | string | yes | Delivery zip code, e.g. `94107`. |
| store_id | body (JSON) | number | yes | Shipt store (retailer) id, e.g. `27`. |
| metro_id | body (JSON) | number | yes | Metro id, e.g. `56`. |
| store_location_id | body (JSON) | number | yes | Store location id, e.g. `6794`. |
| page | body (JSON) | number | yes | Page number, starting at `1`. |

Returns (fields the source code reads; not yet verified live):
- `facets[]`: the facet named `Categories` has `items[]` with `id` and `name`

#### POST `/categories` - Categories (subcategories)
Category facets inside one category.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| zip | body (JSON) | string | yes | Delivery zip code, e.g. `94107`. |
| store_id | body (JSON) | number | yes | Shipt store (retailer) id, e.g. `27`. |
| metro_id | body (JSON) | number | yes | Metro id, e.g. `56`. |
| store_location_id | body (JSON) | number | yes | Store location id, e.g. `6794`. |
| page | body (JSON) | number | yes | Page number, starting at `1`. |
| category_id | body (JSON) | number | yes | Category id from `/menus`. |

Returns (fields the source code reads; not yet verified live):
- `facets[]`: category facets (`categories`, `h1categories`, `h2categories`) with `id` and `name`

#### POST `/products` - Products (category products)
One page (48) of a category's products.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| zip | body (JSON) | string | yes | Delivery zip code, e.g. `94107`. |
| store_id | body (JSON) | number | yes | Shipt store (retailer) id, e.g. `27`. |
| metro_id | body (JSON) | number | yes | Metro id, e.g. `56`. |
| store_location_id | body (JSON) | number | yes | Store location id, e.g. `6794`. |
| page | body (JSON) | number | yes | Page number, starting at `1`. |
| category_id | body (JSON) | number | yes | Category id from `/menus` or `/categories`. |

Returns (fields the source code reads; not yet verified live):
- product hits with `product_id`, name, price, sale price, image, and `parent.variation_products[]` for products with variants

### Caveats

- These routes were written from MealMe's source code and have not been tested live yet (the site blocks plain requests from the test machine).
- The source site uses bot protection (Fastly WAF); calls may be blocked until that is handled.
- Upstream calls change over time (embedded keys, field names). Verify responses before relying on them.
- Not affiliated with shipt.com.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### POST /menus — Menus (store categories)
- Gateway: `POST https://api.apiclay.com/v1/api/shiptapi/menus`
- Body sample (JSON):

```json
{"zip": "94107", "metro_id": 56, "store_id": 27, "store_location_id": 6794, "page": 1}
```

- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### POST /categories — Categories (subcategories)
- Gateway: `POST https://api.apiclay.com/v1/api/shiptapi/categories`
- Body sample (JSON):

```json
{"zip": "94107", "metro_id": 56, "store_id": 27, "store_location_id": 6794, "page": 1, "category_id": 4}
```

- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### POST /products — Products (category products)
- Gateway: `POST https://api.apiclay.com/v1/api/shiptapi/products`
- Body sample (JSON):

```json
{"zip": "94107", "metro_id": 56, "store_id": 27, "store_location_id": 6794, "page": 1, "category_id": 4}
```

- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X POST "https://api.apiclay.com/v1/api/shiptapi/menus" \
  -H "token: <YOUR_APICLAY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"zip": "94107", "metro_id": 56, "store_id": 27, "store_location_id": 6794, "page": 1}'
```

Index of every published API: https://apiclay.com/llms.txt
