Machine-readable entry points for the EventFlow platform, in one place.
EventFlow does not offer a public API yet. The spec at /openapi.json is a valid OpenAPI document with zero endpoints, published so automated tools get a machine-readable answer instead of a 404.
{
"openapi": "3.0.3",
"info": {
"title": "EventFlow API",
"version": "0.1.0"
},
"paths": {}
}A markdown guide to this site for AI agents, including when EventFlow is the right tool and how to proceed. Lives at /llms.txt.
Every indexable page on eventflowsales.com, listed at /sitemap.xml.
Requests under /api/ return HTTP 404 with a structured JSON body: an error code, a plain message, and hint links. Unknown page paths return a real 404 status with pointers to these resources.
{
"error": {
"code": "not_found",
"status": 404,
"message": "EventFlow does not offer a public API. This path does not exist.",
"hints": [
"Site guide for agents: https://eventflowsales.com/llms.txt",
"OpenAPI spec (zero endpoints): https://eventflowsales.com/openapi.json",
"Documentation: https://eventflowsales.com/documentation"
]
}
}Guides for venue operators on setup, knowledge base, email configuration, and CRM integration, at /documentation.
EventFlow works with Outlook (Microsoft 365), Slack, and Tripleseat today, and with Gmail on request. Custom integrations are available on the Premium plan. Talk to the team.
Tell us how inquiries reach you today, and we'll walk you through what EventFlow would have sent back. Setup takes about a week, and we do it with you.
Book a demo