Popmenu

aid: popmenu
name: Popmenu
description: 'Popmenu is a restaurant technology platform offering websites, interactive and dynamic menus, online ordering,
  marketing automation, and menu management designed to turn a restaurant''s web presence into a customer conversion engine.
  Popmenu promotes a Developer API that gives partners access to data on menus, guests, orders, and more for custom integrations,
  and it connects to applications such as Square, Toast, Google Analytics, Mailchimp, OpenTable, Resy, DoorDash, and Yelp,
  plus hundreds of others through partner integrations. That API is GraphQL rather than REST: a live single endpoint was verified
  at https://api.popmenu.com/graphql on 2026-08-13, mirrored at https://my.popmenu.com/graphql, returning HTTP 200 with vendor
  popmenu-ratelimit-* headers — but introspection and every query answer "unauthorized" without partner credentials, so the
  schema cannot be discovered publicly. No OpenAPI, Swagger, AsyncAPI, webhook catalog, MCP server, agent card, llms.txt or
  /.well-known/ document exists on any Popmenu host. Authentication, scopes, error codes and rate limits are undocumented,
  and get.popmenu.com/developer-api is a lead-capture form rather than a reference. Popmenu''s engineering stack is Ruby on
  Rails with a React front end, and its entire marketing estate returns HTTP 403 to non-browser clients.'
type: Index
accessModel:
  pricing: paid
  onboarding: approval
  trial: false
  try_now: false
  public: false
  label: Paid · Requires approval
  confidence: high
  source:
  - https://get.popmenu.com/developer-api
  - https://get.popmenu.com/pricing
  - https://api.popmenu.com/graphql
  generated: '2026-08-13'
  method: searched
  note: 'HAND-CORRECTED, do not let derive-access-model.py overwrite this without a fix upstream. On 2026-08-13 that script
    derived `onboarding: open / public: true / "Open access"` for Popmenu, which is the opposite of the truth. The cause is
    its `auth_present and not types -> open` branch: this repo''s authentication/popmenu-authentication.yml exists but declares
    `schemes: []` BECAUSE Popmenu documents no authentication at all, and the script read that honest empty set as evidence
    of anonymous access. The real posture: the Developer API is reachable only after a sales conversation (get.popmenu.com/developer-api
    is a lead-capture form landing on /success-api), every unauthenticated call to https://api.popmenu.com/graphql returns
    `unauthorized`, and the published $159/$269/$449-per-month tiers price the software platform, not API access.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/popmenu.png
tags:
- Restaurant
- Menus
- Online Ordering
- Websites
- Marketing
- Integration
- Hospitality
- GraphQL
- Point-of-Sale
- Reservations
- Loyalty
- AI Marketing
tags_raw:
- Restaurant
- Menus
- Online Ordering
- Websites
- Marketing
- Integrations
- Hospitality
- GraphQL
- Point Of Sale
- Reservations
- Loyalty
- AI Marketing
url: https://raw.githubusercontent.com/api-evangelist/popmenu/refs/heads/main/apis.yml
created: '2026-06-02'
modified: '2026-08-13'
specificationVersion: '0.23'
apis:
- aid: popmenu:rest-api
  name: Popmenu Developer API
  description: 'The Popmenu Developer API gives partners access to restaurant data including menus, guests, and orders for
    building custom integrations with the Popmenu platform. Popmenu also connects with POS and marketing tools such as Square,
    Toast, Mailchimp, OpenTable, and Yelp. The interface is GraphQL, not REST: a single endpoint at https://api.popmenu.com/graphql
    was verified live on 2026-08-13 (HTTP 200, application/json) and is mirrored at https://my.popmenu.com/graphql. Introspection
    and every query return an `unauthorized` error envelope without partner credentials, so the schema cannot be discovered
    publicly. There is no OpenAPI, Swagger, AsyncAPI or published reference, no documented authentication scheme, and no self-service
    signup — get.popmenu.com/developer-api is a lead-capture form that lands on a "we''ll be reaching out to you soon" page.'
  humanURL: https://get.popmenu.com/developer-api
  baseURL: https://api.popmenu.com/graphql
  tags:
  - Menus
  - Guests
  - Order
  - GraphQL
  tags_raw:
  - Menus
  - Guests
  - Orders
  - GraphQL
  properties:
  - type: DeveloperProgram
    url: https://get.popmenu.com/developer-api
    note: Deliberately NOT typed `Documentation` or `DeveloperPortal`. The page was read verbatim (via the Internet Archive,
      since get.popmenu.com returns 403 to every non-browser client) and contains no reference material of any kind — it is
      an access-request form. It was typed `Documentation` in a prior round; that was a false credit and is corrected here.
  - url: graphql/popmenu-graphql.md
    type: GraphQL
  - type: AuthenticationProbe
    url: authentication/popmenu-authentication.yml
    note: Deliberately NOT typed `Authentication`. The scored check reads "authentication is documented as its own topic"
      and Popmenu documents none — this artifact records only what an unauthenticated probe of the live endpoint observed.
  - type: ErrorCatalog
    url: errors/popmenu-problem-types.yml
  - type: Conventions
    url: conventions/popmenu-conventions.yml
  - type: RateLimits
    url: rate-limits/popmenu-rate-limits.yml
- aid: popmenu:integrations
  name: Popmenu Integrations
  description: Popmenu integrates with popular restaurant, ordering, delivery, reservation, and marketing applications including
    Square, Toast, Google Analytics, Google Business Profile, Mailchimp, Yelp, OpenTable, Resy, DoorDash, PayPal, and social
    platforms (Facebook, Instagram, X), enabling custom workflows around websites, menus, ordering, reputation, and marketing.
  humanURL: https://get.popmenu.com/integrations
  tags:
  - Integration
  - Point-of-Sale
  - Marketing
  tags_raw:
  - Integrations
  - Point Of Sale
  - Marketing
  properties:
  - type: Documentation
    url: https://get.popmenu.com/integrations
common:
- type: DomainSecurity
  url: security/popmenu-domain-security.yml
- type: Website
  url: https://get.popmenu.com/
- type: DeveloperProgram
  url: https://get.popmenu.com/developer-api
  note: Was typed `Documentation` before 2026-08-13. The page carries no reference material — it is an access-request form
    — so the Documentation pointer was a false credit and has been retyped rather than removed, to preserve the link.
- type: Support
  url: https://support.popmenu.com/s/
- type: Blog
  url: https://get.popmenu.com/blog
- type: Partners
  url: https://get.popmenu.com/partnerships
- type: GitHubOrganization
  url: https://github.com/Popmenu
- type: Pricing
  url: https://get.popmenu.com/pricing
- type: Login
  url: https://my.popmenu.com/
- type: TermsOfService
  url: https://my.popmenu.com/terms
- type: PrivacyPolicy
  url: https://my.popmenu.com/privacy
- type: StatusPage
  url: https://status.popmenu.com/
- type: Plans
  url: plans/popmenu-plans-pricing.yml
- type: RateLimits
  url: rate-limits/popmenu-rate-limits.yml
- type: Lifecycle
  url: lifecycle/popmenu-lifecycle.yml
- type: Conformance
  url: conformance/popmenu-conformance.yml
- type: Conventions
  url: conventions/popmenu-conventions.yml
- type: ErrorCatalog
  url: errors/popmenu-problem-types.yml
- type: Packages
  url: packages/popmenu-packages.yml
- type: LLMsTxt
  url: llms/popmenu-llms.txt
- type: WellKnownProbe
  url: well-known/popmenu-well-known.yml
  note: Deliberately NOT typed `WellKnown`. Every /.well-known/ path 404s on the reachable hosts and 403s behind the bot challenge
    on the rest; the file documents an absence, and a `WellKnown` pointer would assert Popmenu serves a discovery surface
    it does not.
- type: MCPProbe
  url: mcp/popmenu-mcp.yml
  note: Deliberately NOT typed `MCPServer`. Popmenu ships no MCP server, hosted or stdio.
- type: Features
  data:
  - name: Restaurant Websites
    description: Mobile-responsive restaurant websites with built-in SEO designed to convert visitors into guests.
  - name: Interactive Dynamic Menus
    description: Photo-rich, followable menu items with guest engagement, reviews, and AI-driven menu recommendations.
  - name: Online Ordering
    description: First-party online ordering for pickup, delivery, and dine-in that keeps margins with the restaurant rather
      than third-party marketplaces.
  - name: Marketing Automation
    description: Automated email and SMS marketing, social posting, and reputation management driven by guest profile data.
  - name: Menu Management
    description: Centralized menu management and publishing that syncs across the website, ordering, and partner channels
      such as OpenTable.
- type: UseCases
  data:
  - name: Sync Menus to Partner Channels
    description: Use partner integrations to publish and keep menus consistent across ordering, delivery, and reservation
      platforms.
  - name: Unify Guest Data
    description: Centralize guest profile, order, and engagement data to power targeted marketing campaigns.
  - name: Streamline Online Ordering
    description: Connect ordering and POS systems to streamline fulfillment for pickup, delivery, and dine-in.
- type: Integrations
  data:
  - name: Toast
    description: POS integration for menu and order synchronization.
  - name: Square
    description: POS and payments integration.
  - name: OpenTable
    description: Preferred menu management and publishing partner for reservations.
  - name: Resy
    description: Reservation platform embed and integration.
  - name: DoorDash
    description: Third-party delivery integration.
  - name: Google Analytics
    description: Web analytics integration for restaurant websites.
  - name: Google Business Profile
    description: Business listing and reputation integration.
  - name: Mailchimp
    description: Email marketing integration.
  - name: Yelp
    description: Reviews, reputation, and reservation integration.
  - name: PayPal
    description: Online payments integration for ordering.
  - name: Facebook
    description: Social posting and marketing integration.
  - name: Instagram
    description: Social posting and marketing integration.
- type: Partners
  data:
  - name: Technology Partners
    description: Companies offering complementary technology solutions that integrate with the Popmenu platform.
  - name: Service Partners
    description: Consultants, agencies, and professional services firms focused on independent restaurants.
  - name: Product Partners
    description: Providers of food, beverage, equipment, and small wares to restaurants.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 11
  pass: local-v1