Skip to content
Last updated

Shuffll Engage — Personalized video at scale

Create personalized video campaigns based on customer interests, behaviors, and audience segments. Tailor content across customer journeys, including e-commerce and product videos, and integrate it into your existing workflows through a robust API and MCP.

Start with the Engage quickstart, connect your AI assistant through MCP, or compare Engage with Video Production. For common integration questions, read the Shuffll API FAQ.

See the platform in action

Explore the capability guide for a connected view of the platform, or jump straight to an outcome:

What can I connect through Engage?

Orchestrate video workflows from your application or a compatible AI assistant. Discover content and published templates, coordinate campaigns and recipients, start generation, and follow jobs through to video results. Choose the operations available to your workspace and compose them around your brief, audience and creative decisions.

REST API and MCP connect to the same Engage product. REST fits application code; MCP lets an AI assistant discover and call the operations available to its authorized workspace.

About this API reference

This reference documents the V1 campaign operations, including the legacy flat-video-v1 rendering format. That format renders frozen clips; recipient fields do not alter the media. See API scope and availability for this contract's boundaries, and check your workspace's live capabilities to select a personalization workflow.

Shared REST and MCP operations use the same operation registry. Journey and tool-specific workflows can expose additional contracts; read live capabilities and the discovered schema before choosing the workflow and template inputs for your integration.

For creating, enhancing, and exporting individual video projects, see the separate Shuffll Video Production API. Use the endpoint and credentials issued for the API you are integrating.

Servers and endpoints

The documentation site hosts these guides; API requests go to the Engage service below. Use these addresses for REST and MCP integrations.

REST API base URL

https://engage.shuffll.com/api

Append the operation path from the reference, including its /v1 prefix. For example, the capabilities request goes to /api/v1/capabilities. The reference's server setting already contains the REST base URL.

MCP server URL · Streamable HTTP

https://engage.shuffll.com/mcp

Enter this exact URL in your compatible MCP client; do not append REST operation paths. REST examples use a scoped Engage API key in the Authorization: Bearer <YOUR_API_KEY> header. MCP clients can use a supported OAuth flow or private API-key settings. Existing Video Production API keys are not interchangeable with Engage credentials. See authentication for access requirements.

Need help? Contact Shuffll with the operation and request ID, excluding credentials and recipient data.