Guest and contact sync
Keep product and Cendyn guest profiles aligned in real time.
Cendyn Connector
Embed Cendyn CRM to sync guest profiles, manage audience lists, and trigger email, SMS and push deliveries per customer account—publish these integrations inside your app for end-user self-service.
Campaign and delivery automation
Trigger email, SMS and push sends from product events or workflows.
Bulk ingest and audiences
Create audience lists and run bulk contact imports for segmentation.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
What teams can integrate or automate with Cendyn
Teams can integrate guest and contact records, audience lists, campaigns, deliveries (email/SMS/push), purchases and hotel metadata using Cendyn’s REST API. Use Cyclr to orchestrate multi-tenant syncs, trigger campaign sends from product events and surface those workflows as in-app integrations for customers.
PRODUCT USE CASES
Top Use Cases for Cendyn Integrations
Create two-way guest sync to keep product records aligned with Cendyn profiles, trigger targeted campaigns and deliveries from product events, automate bulk contact imports, and surface campaign and delivery actions inside your embedded integration marketplace.
Two-way guest profile sync
Sync product user records with Cendyn guest profiles (create, update, read contact and custom fields) so customer accounts see consistent guest data.
Trigger campaigns and deliveries
Trigger email, SMS or push deliveries and preview campaign messages from product events using Cendyn deliveries and campaign endpoints.
Bulk contact ingestion and audience creation
Import contact batches via Sync Data and create audience lists for segmentation and targeted sends inside Cendyn.
ORCHESTRATION
How Cendyn works with Cyclr
Cyclr sits between your SaaS product and Cendyn to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Cendyn
Cendyn processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Cendyn methods you can orchestrate through Cyclr.
Forms1
Upload Form Data
ActionUpload data to a form with the specified Form ID.
TECHNICAL DETAILS
Cendyn integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Cendyn integrations in Cyclr.
API and authentication
- API host
https://api.eu.cendyncrm.com- Authentication
- Token (Authorization header)
- Credentials
Account secret or master secret, account_id/crm_property_code, optional app secret, region base URL.
- Method categories
Contacts/profiles CRUD, deliveries (email/SMS/push), campaigns, audience lists, purchases, coupon lists, bulk sync, webhooks.
Pagination and rate limits
Pagination
Method-specific behavior should be confirmed before implementation.
Rate limits
No published rate-limit headers or throttling policy; API exposes a consumption balance endpoint for delivery credit tracking.
IMPLEMENTATION
Authentication at a glance
Header token auth: pass account_secret or account_master_secret in Authorization as ‘Token token=…’. App secrets exist for Web SDK; no OAuth flows documented.
- Authentication method
- Token (Authorization header)
- Credential required
Account secret or master secret, account_id/crm_property_code, optional app secret, region base URL.
Before you begin:
View setup guideSome operations may need account-master secret; credential rotation not documented.
COMMON QUESTIONS
Frequently asked questions
It syncs guest and contact records, manages audience lists, sends campaigns and deliveries (email, SMS, push), ingests bulk contacts and reads purchases and hotel metadata to automate hospitality workflows.
Cendyn uses header token authentication: include the account_secret or account_master_secret in the Authorization header as ‘Token token=’. App-level secrets exist for the Web SDK.
Yes. Cyclr stores per-tenant Cendyn credentials and property codes so one orchestration can run per customer account and surface separate, governed connections inside your app.
Yes. Cyclr can expose verified Cendyn methods as governed MCP tools with role-based controls, per-tenant credentials and reusable orchestration templates.
KEEP EXPLORING
Related resources and connectors
Documentation
CRM Integrations you should be using
Read more →ProductWhat is iPaaS?
Read more →ProductMCP PaaS
Read more →Related connectorActiveCampaign
Related Crms connector for customer-facing integration workflows.
Related connectorBitrix24
Related Crms connector for customer-facing integration workflows.
Related connectorCapsule
Related Crms connector for customer-facing integration workflows.