# Snackpass API

> Snackpass store menus with products and add-on groups

- Vendor: `snackpassapi` · version 1.0 · category Food · tags snackpass api, snackpass menu api, campus food ordering api, restaurant menu api, snackpass store api, pickup ordering api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/snackpassapi
- This document: https://apiclay.com/docs/snackpassapi.md
- OpenAPI 3.1: https://apiclay.com/api/snackpassapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `snackpassapi`
- Updated: 2026-11-18

## About

## Snackpass API

Read a Snackpass store's menu: every product with its category, price, image and add-on groups.

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

The store id is the last part of a Snackpass store URL.

### Routes

#### GET `/menus` - Menus (store products with add-ons)
Returns the store's products.

| Param | In | Type | Required | Description |
|---|---|---|---|---|
| store_id | path | string | yes | Snackpass store id (last part of the store URL). |

Returns (fields read by the source code; not yet verified live):
- `products[]._id`, `.name`, `.description`, `.category`, `.price`, `.image`, `.soldOut`: product
- `products[].addonGroups[]._id`, `.name`, `.required`, `.limit`: add-on group and its limit
- `products[].addonGroups[].addons[]._id`, `.name`, `.price`, `.soldOut`: add-on

### Caveats

- Upstream calls change over time (embedded keys, field names). Verify responses before relying on them.
- The source site uses bot protection (Vercel Security Checkpoint on the web ordering site); calls may be blocked until that is handled.
- The products endpoint expects a logged-in Snackpass account token, which this listing does not send. Calls answer 403 Unauthorized until that is handled.
- These routes were translated from working client code but have not yet been called through ApiClay. Expect adjustments once they are tested.
- Not affiliated with snackpass.co.

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

### GET /menus — Menus (store products with add-ons)
- Gateway: `GET https://api.apiclay.com/v1/api/snackpassapi/menus`
- Public query params: `store_id` (string, required)
- 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 GET "https://api.apiclay.com/v1/api/snackpassapi/menus?store_id=<store_id>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

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