aid: vagaro url: https://raw.githubusercontent.com/api-evangelist/vagaro/refs/heads/main/apis.yml name: Vagaro kind: company description: Vagaro is a cloud platform for salon, spa, and fitness/wellness business management - scheduling, point of sale and payments, marketing, and a consumer booking marketplace (Vagaro.com and the Vagaro app). Vagaro publishes a real developer surface at docs.vagaro.com, a readme.io-hosted "PUBLIC - Enterprise Business API V2" site with a documented OAuth-style Access Token endpoint, five REST capability areas (Employee Management, Locations, Appointments, Customers, Employees), and an outbound Webhooks system covering Appointments, Customers, Employees, Transactions, Form Responses, and Business Locations plus booking- widget interaction events, with fully specified event payloads. Access is gated behind Settings, Developers, APIs & Webhooks inside a Vagaro business account. It requires a paid, non-trial subscription with Credit Card Processing enabled on the computer, tablet, Pay Desk, or PayPro version, a submitted request form, and roughly five to seven business days for approval before credentials and full endpoint reference detail become visible. image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg tags: - Salon - Spa - Fitness - Wellness - Scheduling - Booking - Vertical SaaS created: '2026-07-03' modified: '2026-07-03' specificationVersion: '0.19' apis: - aid: vagaro:vagaro-access-token-api name: Vagaro Access Token API tags: - Authentication - OAuth - Access Token image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg humanURL: https://docs.vagaro.com/public/reference/generate-access-token baseURL: https://api.vagaro.com properties: - url: https://docs.vagaro.com/public/reference/api-introduction type: Documentation - url: https://docs.vagaro.com/public/reference/generate-access-token type: APIReference - url: openapi/vagaro-openapi.yml type: OpenAPI description: Exchanges a partner clientId and clientSecretKey, plus a comma- separated list of requested scopes, for a bearer access token scoped to a business region - POST https://api.vagaro.com/{region}/api/v2/merchants/generate-access-token. Documented response codes are 200 (issued), 400 (bad request), 401 (unauthorized), and 429 (too many requests); each other Vagaro Business API reference page lists the specific scope it requires from this token. - aid: vagaro:vagaro-appointments-api name: Vagaro Appointments API tags: - Appointments - Bookings - Scheduling image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg humanURL: https://docs.vagaro.com/public/reference/api-introduction baseURL: https://api.vagaro.com properties: - url: https://docs.vagaro.com/public/reference/api-introduction type: Documentation - url: https://docs.vagaro.com/public/docs/appointment-events type: Documentation - url: openapi/vagaro-openapi.yml type: OpenAPI description: Retrieve appointment records - booking status (Confirmed, Awaiting Confirmation, No Show, Service Completed, and similar values), start/end time, service and service provider, customer, and booking source. Vagaro's own reference describes this area only at the capability level ("retrieve details about appointments including status, start time, and service provider") without exposing the full path/parameter list outside an approved partner account; the endpoints here are honestly modeled from that description and from the confirmed Appointment webhook payload schema, not fabricated or verified against a live response. endpointsModeled: true - aid: vagaro:vagaro-customers-api name: Vagaro Customers API tags: - Customers - CRM - Contacts image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg humanURL: https://docs.vagaro.com/public/reference/api-introduction baseURL: https://api.vagaro.com properties: - url: https://docs.vagaro.com/public/reference/api-introduction type: Documentation - url: https://docs.vagaro.com/public/docs/customer-events type: Documentation - url: openapi/vagaro-openapi.yml type: OpenAPI description: Retrieve customer contact information and profile tags. Documented by Vagaro only at the capability level; endpoints here are honestly modeled from that description and the confirmed Customer webhook payload shape, not verified against the gated live reference. endpointsModeled: true - aid: vagaro:vagaro-employees-api name: Vagaro Employees API tags: - Employees - Staff - Service Providers image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg humanURL: https://docs.vagaro.com/public/reference/api-introduction baseURL: https://api.vagaro.com properties: - url: https://docs.vagaro.com/public/reference/api-introduction type: Documentation - url: https://docs.vagaro.com/public/docs/employee-events type: Documentation - url: openapi/vagaro-openapi.yml type: OpenAPI description: Retrieve service provider details - contact information and reporting relationships. Documented by Vagaro only at the capability level; endpoints here are honestly modeled from that description and the confirmed Employee webhook payload shape, not verified against the gated live reference. endpointsModeled: true - aid: vagaro:vagaro-employee-management-api name: Vagaro Employee Management API tags: - Employee Management - Access Control - Calendars image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg humanURL: https://docs.vagaro.com/public/reference/api-introduction baseURL: https://api.vagaro.com properties: - url: https://docs.vagaro.com/public/reference/api-introduction type: Documentation - url: openapi/vagaro-openapi.yml type: OpenAPI description: Assign and unassign employees across multiple business locations with a specified access level, and provision or deprovision a bookable calendar for an employee. Vagaro documents this only as a capability summary ("easily manage employees across multiple locations by assigning and unassigning them while specifying what access level they should have"); endpoints here are honestly modeled from that description, not verified against the gated live reference. endpointsModeled: true - aid: vagaro:vagaro-locations-api name: Vagaro Locations API tags: - Locations - Multi-Location - Businesses image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg humanURL: https://docs.vagaro.com/public/reference/api-introduction baseURL: https://api.vagaro.com properties: - url: https://docs.vagaro.com/public/reference/api-introduction type: Documentation - url: https://docs.vagaro.com/public/docs/business-location-events type: Documentation - url: openapi/vagaro-openapi.yml type: OpenAPI description: Retrieve single- or multi-location business details for a Vagaro account. Documented by Vagaro only at the capability level; endpoints here are honestly modeled from that description and the confirmed Business Location webhook payload shape, not verified against the gated live reference. endpointsModeled: true - aid: vagaro:vagaro-webhooks name: Vagaro Webhooks tags: - Webhooks - Events - Real-Time image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg humanURL: https://docs.vagaro.com/public/docs/introduction properties: - url: https://docs.vagaro.com/public/docs/introduction type: Documentation - url: https://docs.vagaro.com/public/docs/webhook-events type: Documentation - url: https://docs.vagaro.com/public/docs/appointment-events type: Documentation - url: https://docs.vagaro.com/public/docs/securing-webhook-endpoint type: Documentation - url: https://docs.vagaro.com/public/docs/retry-policy type: Documentation - url: https://support.vagaro.com/hc/en-us/articles/29521637950875-Set-Up-Webhooks-From-Vagaro type: Documentation description: Outbound event notifications - HTTP POST requests to a merchant- registered HTTPS endpoint, not a WebSocket - fired whenever Appointments, Customers, Employees, Transactions, Form Responses, or Business Locations change, plus booking-widget interaction events (tab clicked, book now clicked, service searched, time slot clicked, form viewed/submitted, credit card capture viewed, booking completed, gift card/promo code applied, customer login, product added/removed from cart, widget loaded). Each event carries an id, createdDate, type, action (created/updated/deleted), and a typed payload; delivery follows a documented retry policy and endpoints can be signature-verified. A business may register up to 10 webhooks. Enabling APIs & Webhooks requires a request submitted from Settings > Developers > APIs & Webhooks and is limited to paid, non-trial accounts running Credit Card Processing on the computer, tablet, Pay Desk, or PayPro version; approval takes roughly five to seven business days. common: - type: DomainSecurity url: security/vagaro-domain-security.yml - type: Authentication url: authentication/vagaro-authentication.yml - type: LinkedIn url: https://www.linkedin.com/company/vagaro - type: Website url: https://www.vagaro.com/pro - type: Documentation url: https://docs.vagaro.com/ - type: Plans url: plans/vagaro-plans-pricing.yml - type: RateLimits url: rate-limits/vagaro-rate-limits.yml - type: FinOps url: finops/vagaro-finops.yml maintainers: - FN: Kin Lane email: kin@apievangelist.com