# Which Shuffll API should I use?

Start with **Shuffll Engage** for video campaign workflows connected to your applications and AI assistants through API and MCP. Choose the **Shuffll Video Production API** to create, enhance, and export individual video projects from prompts, scripts, articles, or supplied media.

## Compare the APIs

|  | Shuffll Engage API and MCP | Shuffll Video Production API |
|  --- | --- | --- |
| Main purpose | Connect video campaign workflows to your business systems and AI assistants | Build video creation and post-production into an application |
| Product focus | Personalized video at scale, across customer journeys and audience segments | Video projects: content in, a produced video out |
| Documented resources | Published templates, campaigns, recipients, generation jobs, and video results | Organizations, workspaces, templates, assets, projects, enhancement, and exports |
| REST base URL | `https://engage.shuffll.com/api` | `https://api.shuffll.com/api/v1` |
| REST path example | `/v1/capabilities` | `/auth/project/create` |
| REST authentication | `Authorization: Bearer <ENGAGE_API_KEY>` | `x-api-key: <VIDEO_PRODUCTION_API_KEY>` |
| MCP endpoint | `https://engage.shuffll.com/mcp` | This API reference documents REST; use Engage for the documented MCP connection |
| First step | [Read your workspace capabilities](/engage/quickstart) | [Create your first video project](/guides/quickstart) |
| Reference | [Engage REST operations](/engage/openapi) | [Video Production REST operations](/apis) |
| OpenAPI download | [Engage JSON](/openapi/engage.json) | [Video Production YAML](/openapi/video-production.yaml) |


API credentials and resource identifiers belong to their own API. An Engage key, template ID, or campaign ID cannot be substituted for a Video Production credential or project ID.

## When should I choose Shuffll Engage?

Choose Engage when the integration centers on campaigns, audience records, reusable templates, and video results. Connect your application through REST or a compatible AI assistant through MCP. E-commerce and product videos are supporting use cases within Engage's broader focus on customer interests, behaviors, and audience segments.

Start by reading live capabilities for your authorized workspace. Then choose the operations and template inputs that support your intended campaign. The [V1 campaign workflow](/engage/workflows) uses the legacy `flat-video-v1` format to render frozen clips; recipient fields alone do not configure personalized media. See [API scope and availability](/engage/release-status) before selecting a rendering workflow.

## When should I choose the Video Production API?

Choose Video Production when your application needs to turn content into a video project, control its branding and media, follow enhancement, and retrieve an exported video. Start with the [Video Production quickstart](/guides/quickstart), then use its [workflow guides](/guides) for project creation, enhancement, and export.

Some operations have explicit development-server overrides. Use the server documented for the operation; a development contract does not establish production availability.

## Are API and MCP two different Engage products?

No. REST API and MCP are two ways to connect to Shuffll Engage. REST suits application code and automation services. MCP lets a compatible AI assistant discover and call authorized tools. Both follow workspace permissions; the tools a client sees depend on its access.

Their catalogs need not be identical. Use the [REST reference](/engage/openapi) for its documented operations and the live MCP schemas for assistant tools, including available [journey workflows](/engage/agentic-workflows).

## Where should I go next?

- [Shuffll Engage quickstart](/engage/quickstart)
- [Connect an AI assistant with MCP](/engage/mcp)
- [Shuffll API FAQ](/faq)
- [Video Production quickstart](/guides/quickstart)


If you need help choosing, [contact Shuffll](/contact) with your intended workflow and the API you are considering.