API access

DineFlow does not publish a customer-facing API in the current release. All restaurant configuration — menu, hours, persona, knowledge base, approvals, reservations — is handled through the operator dashboard at app.dineflow.ai.

Internal APIs

The product has internal APIs (powering the dashboard, widget, and Vapi voice tool calls), but they are not stable, not documented for external use, and require dashboard JWT auth — they should not be called from a third-party integration.

What works today via integrations

• Stripe — subscriptions, billing portal, webhooks (handled inside the product, no integration work on your side)
• Vapi — voice infrastructure (we manage the assistant for you)
• Telnyx — phone numbers + SMS (we manage)
• Google Places — restaurant data import during onboarding
• Google OAuth — sign-in to the dashboard

What we don't do today

• No public REST or GraphQL API
• No SDKs (JavaScript, Python, etc.)
• No webhooks delivered to your servers (Stripe webhooks land on us, not you)
• No POS integration (Toast, Square, Lightspeed, etc.)
• No third-party reservation platform sync (OpenTable, Resy, etc.)
• No CRM integration (HubSpot, Salesforce, etc.)

Those items are on the roadmap; none have ship dates worth printing.

Enterprise contracts

If you're running multiple locations and need custom API work, scoped webhooks, or a specific integration, email general@dineflow.ai and we'll quote it.

Why we're not pretending

The previous version of this page documented a fictional API key system. We removed it. We'd rather lose the SEO traffic from a fake "DineFlow API docs" page than mislead an integrator who'd build against endpoints that don't exist.