Cendyn

Sync guest profiles and contacts to Cendyn CRM for hospitality marketing, loyalty management, and personalized guest engagement. Zeotap keeps your Cendyn contact database in sync with your warehouse data, enabling targeted campaigns with up-to-date guest attributes.

Prerequisites

• A Cendyn CRM account with API access enabled
• Your Cendyn Account ID
• A Cendyn API token (account secret)
• Knowledge of your Cendyn API region (EU or US)

Authentication

Cendyn uses Token authentication with an account secret.

1. Log in to your Cendyn CRM dashboard
2. Navigate to Settings > API Keys
3. Locate your Account ID and Account Secret (API token)
4. Copy the account secret token
5. In Zeotap, paste the token into the API Token field when creating the destination

Configuration

Target Settings

To find your List ID, navigate to Contacts > Lists in Cendyn CRM. The ID is displayed alongside each list.

Supported Operations

Sync Modes

Audience Sync Modes

Cendyn’s API supports adding contacts to lists via the bulk create endpoint with list subscriptions. Removing contacts from lists is not natively supported through the bulk API, so Remove and Mirror audience modes are not available.

Features

• Field Mapping: Yes
• Schema Introspection: No

Required Mapping Fields

Default Destination Fields

email, name_first, name_last, phone_number, phone_countrycode, city, country, language, born_date, gender, user_id, tags

Cendyn uses snake_case field names. Zeotap maps your warehouse columns directly to Cendyn contact fields.

How It Works

Contact Sync (Upsert / Insert Mode)

1. Zeotap batches contacts in groups of up to 5,000 (Cendyn’s maximum per request)
2. Each batch is sent to the Cendyn Bulk Contact Create endpoint (POST /v2/account/{account_id}/contact/bulk)
3. The match_contact_user_id flag is set to true, so existing contacts matched by user_id are updated
4. If a List ID is configured, contacts are automatically subscribed to the specified list
5. Cendyn processes the batch asynchronously and returns a job ID

Contact Update Mode

1. For each contact, Zeotap looks up the contact by email to retrieve the Cendyn contact ID
2. The contact is updated via PUT /v2/account/{account_id}/contact/{contact_id}
3. If a contact cannot be found by email, that row is reported as failed

Audience Sync (Add / Upsert Mode)

1. Contacts are created or updated via the bulk endpoint
2. List subscriptions are included in the contact payload, subscribing each contact to the configured list
3. New contacts are created and subscribed; existing contacts are updated and their subscription is maintained

Rate Limits

Cendyn does not publish specific rate limits in their public documentation. Zeotap uses reasonable batch sizes (up to 5,000 contacts per request) and automatically retries on 429 Too Many Requests responses with exponential backoff.

For high-volume syncs, consider:

• Scheduling syncs during off-peak hours
• Using upsert mode instead of update mode (which requires per-contact lookups)
• Contacting your Cendyn account representative for rate limit details

Best Practices

• Use upsert mode for most syncs to handle both new and existing contacts in a single operation
• Set the user_id field to enable Cendyn’s contact matching when using upsert mode
• Choose the correct region matching where your Cendyn account is hosted to avoid authentication errors
• Configure a List ID for audience syncs to automatically manage list subscriptions
• Use born_date in ISO 8601 format (e.g., 1990-01-15) for proper date handling
• Set gender to MALE or FEMALE to match Cendyn’s expected values
• Use ISO-2 codes for language (e.g., en, fr, de)
• Include phone_countrycode when syncing phone numbers (e.g., +1, +44)

Troubleshooting

Authentication failed: invalid API token or account ID

Verify your API token and account ID in Cendyn CRM under Settings > API Keys. Ensure the token has not been revoked and the account ID matches your Cendyn instance.

Contact not found (update mode)

The update sync mode requires contacts to already exist in Cendyn. It looks up contacts by email address. If you are syncing new contacts, use upsert mode instead.

Wrong region selected

If you receive connection errors, verify you selected the correct API region. European accounts use api.eu.cendyncrm.com and US accounts use api.us.cendyncrm.com. Selecting the wrong region results in authentication failures.

Bulk import returns queued status

Cendyn processes bulk imports asynchronously. A 201 response with status queue means the import was accepted and is being processed. Check your Cendyn dashboard for import results and any per-contact errors.

Phone number not syncing

Cendyn expects the phone_countrycode and phone_number fields to be provided separately. Map your warehouse phone country code column to phone_countrycode and the number to phone_number.

Tags not appearing on contacts

Ensure the tags field is mapped as a comma-separated string or array. Cendyn treats tags as an array of strings — verify the format matches what your Cendyn account expects.

List subscription not applied

Ensure the List ID is set in the target settings and the list exists in your Cendyn account. List subscriptions are only applied during bulk create operations (upsert/insert modes), not during individual updates.

Rate limit exceeded (429 errors)

Zeotap retries automatically with exponential backoff. If errors persist, reduce your sync frequency or contact your Cendyn account representative to discuss rate limit increases.