AllergyTable Data

The allergen API for independent restaurants.

One request returns a cited, dish-by-dish allergen record for any restaurant, including the independents that no other database covers.

9 allergensPer-dish resolutionA source on every claim
request
POST https://api.allergytable.com/v1/check
Authorization: Bearer sk_live_…

{
  "restaurant": "Lilia",
  "location": "Brooklyn, NY"
}
9major allergens, per dish
Citeda source URL on every claim
Cachedresearched once, then instant
JSON / CSVAPI or scheduled bulk export
Three ways to consume it

Query it live, license it in bulk, or direct where it grows.

REST · JSON

Real-time API

Query a restaurant by name and location, get a structured allergen record back in one call. Results are cached, so repeat lookups are instant and free.

Request access →
JSON · CSV export

Bulk licensing

Take a scheduled export of the growing independent-restaurant allergen dataset and load it into your own stack. Refreshed as coverage expands.

Request access →
Partner priority

Coverage on demand

Need a specific city or a named list of restaurants populated first? We direct the research engine to fill coverage where partners need it.

Request access →

A record is structured, graded, and sourced.

Every dish is checked against the nine major allergens. Each hit carries how it was established and the page it came from. When a menu can’t be read, the record says so instead of guessing.

200 OK · sample response
{
  "restaurant": { "name": "Lilia", "location": "Brooklyn, NY" },
  "dishes": [
    {
      "name": "Housemade Mozzarella, Garlic Bread, Bottarga",
      "allergens": [
        { "name": "milk", "presence": "confirmed", "source_url": "lilianewyork.com/menu" },
        { "name": "wheat_gluten", "presence": "confirmed" },
        { "name": "fish", "presence": "confirmed" }
      ]
    }
  ],
  "data_quality": { "coverage": "partial", "cited": true }
}

Real output from the research engine. Field shape is stable; the endpoint opens to partners in the private beta.

Chains publish their allergens. Independents don’t.

Every nutrition dataset already ingests the national chains, because the chains hand that data out. For independent restaurants there is no structured allergen source to license anywhere. That gap is the product. We read the actual menu, grade each allergen, and cite it.

Chains

Already covered

Public matrices, ingested everywhere. No edge in reselling what a brand gives away.

Independent restaurants

Covered by no one else

Unstructured menus, seasonal changes, undocumented cross-contact. Generic food APIs guess from a lookalike dish. We read the real one and source it.

Who builds on it

An allergen layer for anywhere people choose a restaurant.

Delivery + ordering

A real allergen read next to every indie listing, not just the chains.

Reservation + discovery

Let diners filter and book by what they can actually eat.

Allergy communities

Back recommendations with cited, per-dish data instead of anecdotes.

Health + clinical

Give patients a sourced answer for real restaurants near them.

Private beta

Request data access.

The API and bulk licensing are opening to a first set of partners. Tell us what you’re building and the coverage you need, and we’ll be in touch as access opens.

  • Sample records and the full field spec
  • Coverage priorities for your market
  • Pricing for API and bulk licensing

No spam. We use this only to talk about data access.