Fides Documentation – Ethyca
Zenoti
This Integration requires Fides Cloud or Fides Enterprise. For more information, talk to our solutions team.
Zenoti is a comprehensive cloud-based software solution for spas, salons, and wellness centers that provides business management tools including appointment scheduling, customer management, and payment processing.
Prerequisites
In order to integrate with Zenoti, you'll need to collect the following information:
| Name | Description |
|---|---|
| Domain* | Your Zenoti API domain (default: api.zenoti.com). |
| API Key* | The API key for your Zenoti organization that you wish to use with Fides. Contact your Zenoti administrator for steps to retrieve this key. |
In order for the integration to work the Zenoti org level setting Search Guest Across Centers needs to be turned on.
Your Zenoti API key will need the following API groups enabled: HyperConnect, Classes (Integrations), Forms, Memberships, GiftCards, Classes (Consumer), Opportunities, Invoice Read, Invoice Payments (Other), Invoice Payments (Credit Card), Guests Read, Guests Write/Update/Delete, and Center Master Read.
Integrating with Zenoti
To integrate an existing system with Zenoti:
- Navigate to Data map → View Systems and choose the system that you want to connect.
- Click on the Integrations tab.
- Pick the vendor or system type that you want to integrate with from the Connection type drop-down menu.
- Complete the required fields for the integration and click Save.
You may confirm your connection is working using the Test connection button, if desired.
To learn more, please see our guide for Managing Integrations.
Technical detail
Fides utilizes API endpoints to access the API service for a SaaS application. An API service is the programmatic interface through which Fides can query and update data within an application to access, rectify, or delete personal information. Each SaaS tool will have a unique set of endpoints to enable privacy functions.
Zenoti Endpoints
In the table below, you can find which endpoints are used for each type of privacy function. Clicking on the endpoint will take you to the documentation for that endpoint.
| Privacy function | Endpoint | Description |
|---|---|---|
| Access Requests | Guest | Used to search and fetch guest information by email. |
| Access Requests | Appointments | Used to retrieve appointment history for a specific guest. |
| Access Requests | Gift Cards | Used to retrieve gift card information for a specific guest. |
| Access Requests | Products | Used to retrieve product purchase history for a specific guest. |
| Access Requests | Payment Accounts | Used to retrieve payment account information for a specific guest. |
| Access Requests | Memberships | Used to retrieve membership information for a specific guest. |
| Access Requests | Relationships | Used to retrieve relationship information for a specific guest. |
| Access Requests | Prepaid Cards | Used to retrieve prepaid card information for a specific guest. |
| Access Requests | Coupons | Used to retrieve coupon information for a specific guest. |
| Access Requests | Series Packages | Used to retrieve series package information for a specific guest. |
| Access Requests | Forms | Used to retrieve form information for a specific guest. |
| Update Requests | Guest | Used to update guest information for data masking requests. |
| Erasure Requests | Payment Account | Used to delete payment account information for a specific guest. |