Vagaro · Rate Limits

Vagaro Rate Limits

Vagaro's public reference documents a 429 (Too Many Requests) response code on the Access Token endpoint, confirming that rate limiting exists, but does not publish numeric request-per-minute or request-per-day thresholds for the Access Token endpoint or for the Appointments, Customers, Employees, Employee Management, or Locations capability areas. Webhooks are similarly bounded by a fixed count - up to 10 registered webhooks per business - and by a documented retry policy for delivery failures, rather than by a numeric inbound rate limit (Vagaro is the sender, not the receiver, of webhook traffic).

Vagaro Rate Limits is the machine-readable rate-limit profile for Vagaro on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, webhooks, and attempts.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Salon, Spa, Fitness, Wellness, and Rate Limiting.

4 Limits Throttle: 429
SalonSpaFitnessWellnessRate LimitingQuotas

Limits

Access Token Requests client
requests
not published
Documented 429 response confirms a limit exists on /merchants/generate-access-token; no numeric threshold is published.
Business API Requests account
requests
not published
No numeric per-minute/per-day limit is published for Appointments, Customers, Employees, Employee Management, or Locations endpoints.
Registered Webhooks business
webhooks
10
A Vagaro business account may register up to 10 webhooks in total, across all event types.
Webhook Delivery Retries webhook
attempts
per documented retry policy
Failed webhook deliveries are retried per Vagaro's published Retry Policy guide; exact attempt count/backoff schedule is documented there.

Policies

Backoff on 429
Clients calling the Access Token endpoint should implement backoff and retry after a 429 response rather than retrying immediately.
Webhook Endpoint Verification
Vagaro documents signing/verification of outbound webhook requests so receivers can confirm a payload originated from Vagaro before trusting it.

Sources