Emarsys connector icon

Emarsys Connector

Embed Emarsys inside your product to push and update contacts, trigger email campaigns, manage segments and send SMS so customers can run marketing actions without leaving your app.

01

Faster time to market

Ship Emarsys integrations in weeks not months.

02

Per-customer credentials

Store and rotate each customer's API user securely.

03

Governed feature surface

Expose only approved Emarsys actions to end users.

04

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

What you can integrate and automate with Emarsys

Integrate your SaaS with Emarsys to create and update contacts, start email campaigns, manage segments and export campaign or contact data. Use Cyclr’s low-code builder to map your app’s contact objects to Emarsys fields and publish in-app automations. See the Emarsys API documentation for endpoint details and permissions. (Emarsys API documentation)

PRODUCT USE CASES

Top Use Cases for Emarsys Integrations

Quickly build and publish in-app automations that sync contacts, trigger campaigns, export lists and send transactional SMS — all managed per-customer from your product.

Create and update contacts in Emarsys

Map your app’s contact records to Emarsys contacts and push create/update calls so each customer keeps marketing lists in sync.

Trigger email campaigns from product events

Start or schedule Emarsys email campaigns or program entrypoints when users perform in-app events or reach campaign thresholds.

Manage segments and subscriptions

Add or remove users from Emarsys segments and lists to control audience membership for each tenant.

ORCHESTRATION

How Emarsys works with Cyclr

Cyclr sits between your SaaS product and Emarsys to handle authentication, govern access and orchestrate every API call per customer, at scale.

  1. 1

    Your SaaS product

    Your app requests an action for a specific customer.

  2. 2

    Cyclr orchestration

    Cyclr authenticates, applies policies and routes the request.

  3. 3

    Emarsys

    Emarsys 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 Emarsys methods you can orchestrate through Cyclr.

External Events2

List External Events

Action

List all External Events.

Trigger External Event

Action

Triggers a named external event for a specified contact.

Contacts8

List Contact Data

Action

Return a list of all contact data by the specified return fields.

Add Contact

Action

Adds a single contact

Get Contacts By Email Address

Action

Get all contacts matching the given email address.

Add Contacts

Action

Add many contacts at once

Add Or Update Contact

Action

Adds a contact or updates if already exists

Get Contact Data

Action

Get contact data specified by the given ID.

Delete Contact

Action

Deletes a contact

Add Or Update Contacts

Action

Adds or updates many contacts at once

Contact Lists6

Fetch Contacts In a Contact List

Action

List contacts from the contact list.

Add Contacts To Contact List

Action

Adds one or more contact to a contact list

List Contact Data In a Contact List

Action

List all the contact data in a contact list.

Remove Contacts From Contact List

Action

Removes contacts from a contact list

List Contacts In A Contact List

Action

List all contacts in a contact list.

List Contact Lists

Action

List all contact lists.

Email Templates2

List Email Templates

Action

Returns a list of all email templates, including their names and IDs.

Get Email Template by ID

Action

Get an email template.

Sections5

Create Section

Action

Create a section in a template based email campaign.

List Sections

Action

Returns a list of sections used in the specified template-based email campaign.

Update Section

Action

Update a section in a template based email campaign.

Delete Section

Action

Deletes a section from a template-based email campaign.

Get Section by ID

Action

Returns the details of a section of a template-based email campaign.

Segments4

List Segments

Action

List all Segments.

Get Contacts Count in a Segment

Action

Retrieve the count of contacts in a segment.

Get Segment Contact Criteria

Action

Get segment contact criteria by the given segment ID.

Delete Segment

Action

Delete the segment specified in the request.

Utilities1

List Contact Fields

Action

List all Contact fields.

Conditional Text Rules1

List Conditional Text Rules

Action

Returns a list of all conditional text rules.

External Content1

Request External Content For Personalization

Action

Request external content for personalization.

TECHNICAL DETAILS

Emarsys integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing Emarsys integrations in Cyclr.

API and authentication

API host
https://api.emarsys.net
Authentication
Username & Secret Key; OAuth 2.0
Credentials

Emarsys account Username and application Secret Key (API user credentials).

Method categories

Contacts; Campaigns; SMS; Segments; Exports; Events

View vendor API documentation →

Pagination and rate limits

Pagination

Offset-based pagination using limit and offset; some endpoints return full lists with no total, stop on empty pages.

Rate limits

Rate limits vary by API; Engagement Events documents 5,000 calls per minute. Respect 429 responses and retry with backoff.

IMPLEMENTATION

Authentication at a glance

Cyclr’s Emarsys connector uses Emarsys API user credentials (account Username and Secret Key). Emarsys also supports OpenID Connect / OAuth 2.0 for Suite API v3.

Authentication method
Username & Secret Key; OAuth 2.0
Credential required

Emarsys account Username and application Secret Key (API user credentials).

Before you begin:

You must create an Emarsys API user and copy the secret key; enable needed API permissions.

View setup guide

COMMON QUESTIONS

Frequently asked questions

It can sync contact records, update custom contact fields, trigger email campaigns, manage segments and call Emarsys export or SMS endpoints to send messages or download data.

You supply an Emarsys API user Username and Secret Key for the connector; Emarsys also supports OpenID Connect (OAuth 2.0) for Suite API v3 depending on API usage.

Yes. Cyclr stores per-customer Emarsys credentials and maps each tenant to their own Emarsys account so customers operate independently inside your app.

Yes. You can surface selected Emarsys actions as governed, reusable tools in Cyclr’s managed command palette so product teams control which methods are available.