Back to API
The API stack vs. the incumbents.
An honest, side-by-side comparison of what each platform’s API can do today. We count documented public endpoints, not private partner ones. We don’t count features that are technically possible if you email sales.
API surface
| Capability | Rellavo | PushPress | Mindbody | Glofox |
|---|---|---|---|---|
| Public REST API on every plan Mindbody bills API usage per call; Glofox access is activated by emailing ABC Fitness. | ||||
| OpenAPI 3.1 spec, machine-readable Glofox publishes an OpenAPI 3.1 spec; Mindbody’s is legacy Swagger 2.0. | ||||
| Interactive docs site PushPress’s developer docs site is offline as of this snapshot. | ||||
| Number of documented endpoints Operations in each vendor’s published spec or SDK. | 196 | 49 | ~150 | 63 |
| Resource coverage parity with dashboard Only Rellavo exposes every resource its own UI uses. |
AI / agents
| Capability | Rellavo | PushPress | Mindbody | Glofox |
|---|---|---|---|---|
| First-party MCP server PushPress ships an alpha MCP server inside its SDK package. | ||||
| AI-tailored system prompt per tenant | ||||
| Tenant-feature-gated tool registration | ||||
| One-command installer (Claude / Cursor) PushPress documents manual config steps; Rellavo’s installer writes the config for you. |
Webhooks
| Capability | Rellavo | PushPress | Mindbody | Glofox |
|---|---|---|---|---|
| Signed webhooks (HMAC-SHA256) Glofox documents HMAC signing, but webhook setup itself is email-gated. | ||||
| Public event taxonomy | ||||
| Retry with exponential backoff Mindbody retries every 15 minutes for 3 hours; Glofox retries 3 times — neither backs off. | ||||
| Self-serve test delivery | ||||
| Replay failed deliveries Documented per-delivery retry endpoint; dashboard button is next. | ||||
| Number of event types Mindbody’s catalog includes 16 staff-management events. | 42 | 23 | ~46 | 4 |
Security & isolation
| Capability | Rellavo | PushPress | Mindbody | Glofox |
|---|---|---|---|---|
| Scoped tokens | ||||
| Documented rate limits Rellavo’s are per token; Mindbody and Glofox publish account-level limits. | ||||
| Tenant-bound at the database layer (RLS) JWT-bound RLS — DB physically refuses cross-tenant queries. No competitor documents an equivalent. | ||||
| Audit log of every API call | ||||
| Token prefix that secret scanners detect |
Developer ergonomics
| Capability | Rellavo | PushPress | Mindbody | Glofox |
|---|---|---|---|---|
| Streaming CSV exports (members, invoices, attendance, comms) | ||||
| Bulk operations (tag / message / assign) | ||||
| Live API console with demo token Mindbody’s console needs a developer signup; Rellavo pre-fills a read-only demo token. | ||||
| Public unauthenticated booking endpoint Every Mindbody call requires an API key; Glofox offers embeddable widgets, not an API. | ||||
| Idempotency-Key on writes |
Snapshot as of 2026-07, re-verified against each vendor’s live public docs, published OpenAPI/Swagger specs, SDK packages, and their own integration marketing pages. We re-check this table on every major Rellavo release. Spot something wrong? Email api@rellavo.com.
Next step
See the price, then see it work.
$499 a month with everything included, in writing on the pricing page. Or book a walkthrough and watch it catch a drifting member while you're on the call.
Reply within one business day