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

CapabilityRellavoPushPressMindbodyGlofox
Public REST API on every plan
Mindbody requires its Public API tier; Glofox is enterprise-gated.
OpenAPI 3.1 spec, machine-readable
Interactive docs site
Number of exposed endpoints170+~40~120~50
Resource coverage parity with dashboard
Only Rellavo exposes every resource its own UI uses.

AI / agents

CapabilityRellavoPushPressMindbodyGlofox
First-party MCP server
AI-tailored system prompt per tenant
Tenant-feature-gated tool registration
One-command installer (Claude / Cursor)

Webhooks

CapabilityRellavoPushPressMindbodyGlofox
Signed webhooks (HMAC-SHA256)
Public event taxonomy
Retry with exponential backoff
Self-serve test delivery
Replay deliveries from the dashboard
Worker supports manual retry; UI is the next step.
Number of event types42~12~30~10

Security & isolation

CapabilityRellavoPushPressMindbodyGlofox
Scoped tokens
Per-token rate limits
Tenant-bound at the database layer (RLS)
JWT-bound RLS — DB physically refuses cross-tenant queries.
Audit log of every API call
Token prefix that secret scanners detect

Developer ergonomics

CapabilityRellavoPushPressMindbodyGlofox
Streaming CSV exports of every dataset
Bulk operations (tag / message / assign)
Live API console with demo token
Public unauthenticated booking endpoint
Idempotency-Key on writes

Snapshot as of 2026-05. Sources: each vendor’s public docs, dev portal, 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 what Rellavo would build around you.

A short conversation is all we need to come back with a concrete plan and a real price.

Request pricing→
Reply within one business day