Vagaro

Last reviewed: July 2026

Overview

Integuru's Vagaro integration provides production-ready HTTP API access to Vagaro, the salon and spa management platform used by independent stylists, franchise salons, fitness studios, and wellness businesses, covering 22 actions across customer management, appointment scheduling, transactions, memberships, packages, and service discovery. Integuru connects to Vagaro via direct HTTP requests rather than browser automation, so calls complete in under 3 seconds with a 99.9%+ success rate.

No public developer API. Vagaro does not expose an official developer API. Engineering teams that need to move customer, appointment, or transaction data programmatically have historically relied on manual exports or fragile browser scripts that break whenever Vagaro updates its UI.

The integration covers every major Vagaro object. Customer lookup spans both list_customers (paginated, up to 200 per page) and get_customers (supports large-batch retrieval with page sizes up to 100,000). The get_customer_all_data action returns the full customer record in a single call. Appointment read/write covers get_appointments, get_customer_appointments, fetch_customer_appointment, create_appointment, update_appointment, and delete_appointment. Financial data is accessible via get_transactions and get_customer_invoices. Membership, package, and intake form data are reachable through get_customer_memberships, get_customer_packages, and get_customer_forms.

Wellness-tech engineers typically use this integration to sync customer rosters into CRM or marketing platforms, automate appointment booking from external scheduling flows, pull transaction history into revenue reporting pipelines, and manage membership and package data across multi-location salon franchises. See the Zenoti integration for another major salon and spa platform, or browse the full integrations catalogue.

---

Use Cases

Integuru's Vagaro integration covers the full customer and appointment lifecycle. Because Vagaro uses encrypted IDs throughout, most workflows begin with a lookup action that returns the correct ID before calling the target action.

• Customer roster sync: Call get_customers with a large page_size to retrieve your full customer list in one request, or use list_customers with search_text to filter by name, email, or phone. Both actions return the encrypted customer_id required by all per-customer actions.
• Full customer record pull: Use get_customer_all_data with an encrypted customer_id to retrieve the complete customer record in a single call, avoiding multiple round trips across individual actions.
• Appointment scheduling: Call list_employees for encrypted calendarIds, list_services for the encrypted service_id, and get_customers for the customer_id, then pass all three into create_appointment along with start_time, duration, and amount.
• Multi-employee appointment retrieval: Pass a calendarIds array to get_appointments to pull appointments across multiple providers in a single date-range query. Use fetch_customer_appointment for a single customer's upcoming appointments.
• Transaction and invoice reporting: Pull paginated transaction history with get_transactions (filter by date range, transaction_type, and show_refunded), or retrieve per-customer invoices with get_customer_invoices.
• Membership and package management: Use get_customer_memberships and get_customer_packages to read active membership and package state for a customer. Call list_memberships to enumerate all available membership plans in the account.
• Service catalog and staff lookup: Use list_services to enumerate available services (pass include_staff: true to include which staff members perform each service), then call get_service_staff with a service_id to verify staff availability for a specific service type.
• Customer notes: Add notes programmatically with add_customer_note, or remove them with delete_customer_note using the encrypted note_id and customer_id.

---

Setup Notes

Integuru's Vagaro integration authenticates against https://www.vagaro.com. Integuru handles the full session flow automatically, including any 2FA your Vagaro account requires. You configure credentials once during setup; Integuru manages re-authentication from that point forward.

Encrypted IDs are central to this integration. Vagaro uses encrypted strings for customer IDs, note IDs, service IDs, calendar IDs, and appointment IDs. These are not human-readable integers. Always retrieve them from the relevant lookup action before calling an action that requires them:

• customer_id: from list_customers or get_customers
• service_id and calendar_id: from list_services and list_employees respectively
• service_provider_id: from get_employees or list_employees
• appointment_ids: from get_appointments or get_customer_appointments
• note_id: from customer note data returned by customer lookup actions

For get_appointments, calendarIds accepts either a single encrypted string or an array of strings, allowing you to query multiple providers in one call.

The create_appointment and update_appointment actions require amount (service price) and duration (minutes) alongside the encrypted IDs. The update_appointment action also accepts old_service_id and old_start_time to record what was changed; both default to the new values if omitted.

For delete_appointment, pass appointment_ids as an array of encrypted strings. Set ignore_refund: true to skip refund processing on cancellation, and recurring: true to delete all instances of a recurring appointment.