integrate with the showclix (leap event technology) api
domain: developer.showclix.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Note that ShowClix now operates under Leap Event Technology's 'Leap Events' branding, with newer docs at technically.leapevents.com alongside the legacy class reference at developer.showclix.com.
Authenticate with the token-based scheme shared across ShowClix's API family (Authentication, Core, Reporting, Sales, Coupon Assignment, Coupons), passing an X-API-Token header on requests.
Use the Core API (new V2 standard) for Events, Venues, and other core entities, or the legacy REST endpoints under api.showclix.com/<Class> (e.g. Event, Sale, Ticket, Venue, Seller, Member).
Use standard HTTP verbs — GET, PUT, POST, DELETE — against class resources as documented in the legacy class reference.
Use the Reporting API for customer/order/ticket/product/scan-log/financial reports, and the narrower Sales API for lightweight consumer sales/marketing insights.
Known gotchas
The platform is mid-rebrand (ShowClix → Leap Event Technology/Leap Events); documentation and endpoints reference both names — verify which domain is authoritative for your account.
There are multiple, separately-versioned APIs (legacy class-based REST, newer Core API V2, Reporting, Sales, Coupon Assignment/Coupons) — confirm which one a given guide describes before reusing sample code.
Full class-level write access (create/edit venues, sellers, events) is intended for approved partners/sellers, not arbitrary third parties — expect a permissions/approval step.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?