Faster time to market
Ship Bluecore integrations without custom point-to-point engineering
Bluecore Connector
Embed Bluecore in your SaaS to push customer profiles and behavioral events, trigger transactional or direct-send messages, and export audiences for campaigns — all orchestrated and published from Cyclr without building point-to-point integrations.
Multi-tenant orchestration
Reuse workflows across customer namespaces with tenant-specific credentials
Governed MCP tools
Expose only approved Bluecore methods to end users
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Teams can send customer profiles and behavioral events to Bluecore, read and update customer records, trigger transactional or direct-send messages, and export audiences for campaigns. Bluecore uses a REST-style API and organized endpoints (namespace-scoped) for Customer Profile, Events and Communicate surfaces; Cyclr workflows can orchestrate event ingestion, profile updates and transactional sends. (developers.bluecore.com)
PRODUCT USE CASES
Use cases
Quickly build customer-facing automations that sync profiles, post events, trigger transactional messages and export audiences. Publish integrations in your white-label embedded marketplace and govern which Bluecore actions are available to each tenant.
Sync customer profiles from your app
Create or update Bluecore Customer Profile records from your app to enable personalization and audience membership. (developers.bluecore.com)
Post behavioral events for real-time personalization
Send events (page views, purchases, cart actions) to Bluecore’s Events API to fuel audience rules and campaign triggers. (help.bluecore.com)
Trigger transactional emails and direct sends
Use Bluecore’s Transactional or Direct Send APIs to send order confirmations or other transactional messages programmatically. (developers.bluecore.com)
ORCHESTRATION
How Bluecore works with Cyclr
Cyclr sits between your SaaS product and Bluecore 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
Bluecore
Bluecore 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 Bluecore methods you can orchestrate through Cyclr.
Emails1
Add Contact
ActionPush contact to campaign.
TECHNICAL DETAILS
Bluecore integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Bluecore integrations in Cyclr.
API and authentication
- API host
https://api.bluecore.app- Authentication
- API key
- Credentials
API key; Namespace (namespace ID); API base Bluecore documentation
- Method categories
Customer profile read/write; Event ingestion; Transactional sends; Audience exports; Direct-send messages
Pagination and rate limits
Pagination
Most list endpoints use offset-style skip/limit pagination; a few use cursor-style pageInfo responses. (blue.app)
Rate limits
Bluecore enforces per-key, per-user and per-organization per-minute limits; exceeding limits returns HTTP 429. Confirm limits for your account or plan. (blue.app)
IMPLEMENTATION
Authentication at a glance
Bluecore authenticates via API keys created in the Bluecore Developer Portal; confirm which auth option Cyclr enables in Console. (help.bluecore.com)
- Authentication method
- API key
- Credential required
API key; Namespace (namespace ID); API base Bluecore documentation
Before you begin:
View setup guideRequires a Bluecore Namespace and API key with appropriate read/write permissions.
COMMON QUESTIONS
Frequently asked questions
It can push customer profiles and behavioral events, read and update customer records, trigger transactional or direct-send messages, and export audiences for campaigns. These actions let you automate personalization and campaign activation from your app. (developers.bluecore.com)
Use an API key created in the Bluecore Developer Portal; keys can be scoped read-only, read & write or custom permissions and display only once when created. Confirm Cyclr’s enabled auth option in Console. (help.bluecore.com)
Yes. Map each tenant to its Bluecore Namespace and API key so Cyclr workflows run per-customer, enabling multi-tenant embedding and tenant-specific orchestration and credentials management.
Yes. Cyclr can expose selected Bluecore actions as governed MCP tools, letting product teams control which methods tenants may run and centrally manage permissions, retries and error handling.
KEEP EXPLORING
Related resources and connectors
Documentation
Email Marketing Integrations to make your daily tasks easier
Read more →ProductTeaming up your POS and eCommerce Integrations
Read more →ProductMCP PaaS
Read more →Related connectorLeadfox
Related Marketing connector for customer-facing integration workflows.
Related connectorAmazon Selling Partner
Related Marketing connector for customer-facing integration workflows.
Related connectorFreshsuccess
Related Marketing connector for customer-facing integration workflows.