Public API endpoints for the Events module
upcoming
J
Juan Víctor Sáenz Ferreyra
Problem: Events has no public API. Unlike Contacts, Opportunities, Calendars or Conversations, there are no CRUD endpoints to create/read/update events, tickets, or registrations programmatically. This blocks any external integration — marketplaces, custom storefronts, catalog sync, or custom checkout flows built on top of Events.
Request: Expose Events as a first-class API resource (v2/v3): list/create/update events, ticket types, registrations, and check-in status, plus read access to event metadata (dates, venue, pricing, capacity).
Impact: Lets developers and agencies build event marketplaces and custom experiences on top of HighLevel instead of hitting a closed wall. Complements the existing workflow triggers (Event Registration / Checked-in) with the read/write access those triggers currently lack.
Log In
S
Sales & Marketing
updated the status to
upcoming