Our website uses cookies. By continuing to use our site, you agree to our use of cookies in accordance with our Privacy Policy.

Now powering .gov websites

CMS Max developer platform

CMS Max Developer Platform

Connect content, commerce, automation, and AI through tenant-scoped platform interfaces.

Use documented APIs, webhooks, supported plugins, Zapier, and the CMS Max MCP server to integrate business systems and operate website content with clear authentication and ownership.

Open API reference Explore the MCP server
  • REST API
  • MCP server
  • Webhooks
  • Tenant scope
  • Revocable tokens
CMS Max API reference showing product, order, page, form, and webhook endpoints
The public CMS Max API reference documents commerce, content, form, user, and webhook-related resources available through the current API.
Authenticate Read Write Automate Monitor

Integration architecture

Start with the business workflow and data owner, then choose the interface.

CMS Max supports several integration paths because a storefront sync, a form notification, an AI content workflow, and a back-office automation do not need the same contract.

REST for application data

Use documented API resources for supported product, order, content, user, form, coupon, file, and related application workflows.

MCP for AI-assisted site operations

Give an MCP-capable client tenant-scoped tools for supported pages, sections, layouts, menus, shortcodes, and theme configuration.

Events for downstream work

Use supported webhooks, Zapier triggers, and plugin-specific event paths when another system needs to react to a CMS Max change.

Platform interfaces

Choose the supported path that matches the integration's responsibility.

Actual resources, permissions, data direction, plan availability, limits, and implementation requirements depend on the website and the enabled CMS Max products.

01

Commerce and content API

Work with the current documented resources for products, variations, categories, brands, images, files, orders, blogs, users, pages, coupons, and form submissions.

Read the API reference
02

Tenant MCP server

Connect an MCP-capable AI client to the tenant domain and expose the current tool definitions through authenticated Streamable HTTP.

Read the MCP guide
03

Webhooks and event delivery

Trigger supported downstream work from form submissions, orders, fulfillment, partner services, and other installed event-producing capabilities.

Explore Zapier automation
04

Plugin integrations

Configure supported payment, shipping, tax, analytics, CRM, marketing, security, accessibility, communications, and retail connections.

Browse integrations
05

Tenant-scoped authentication

Create API-client tokens inside the website administration experience so access is tied to one tenant, revocable, logged, and rate-limited.

Review API access
06

Partner implementation

Define field mapping, credentials, environments, test data, failure handling, reconciliation, monitoring, launch, and long-term ownership.

Discuss a partnership

Model Context Protocol

Let an AI client understand the tenant before it changes the tenant.

The CMS Max MCP server exposes descriptions and JSON input schemas for its current tools. Read operations support discovery; write operations support deliberate changes inside the authenticated website.

Explore MCP connection and tool groups
01Tenant domainThe site domain resolves the tenant context.
02Bearer tokenAn API-client token authenticates the request.
03Tool schemaThe client reads current names, descriptions, and inputs.
04Scoped actionThe selected tool runs in that tenant's data.
05Structured resultThe client receives a machine-readable response.

Developer resources

Use the tenant endpoint and the current public documentation.

Replace the example host with the CMS Max website domain. Store tokens as secrets and never place them in public source, client-side code, screenshots, or shared content.

REST API
https://your-site.example/ecommerce-api/v1
MCP server
https://your-site.example/mcp
User documentation
cmsmax.com/docs/user

Production delivery

Move from a successful request to an integration the business can operate.

  1. 01

    Discover

    Define the actors, system owners, customer journey, source of truth, required data, and expected outcomes.

  2. 02

    Authenticate

    Create the appropriate account and token, restrict access, store secrets correctly, and document revocation.

  3. 03

    Validate

    Test representative records, limits, errors, retries, duplicate delivery, edge cases, and reconciliation.

  4. 04

    Operate

    Monitor jobs and logs, rotate credentials, review API changes, assign support, and maintain the data contract.

Security and governance

Give every connection a purpose, a boundary, and an owner.

Technical access is only one part of a responsible integration. Production work also needs data minimization, secret handling, human review, monitoring, partner policy compliance, and a tested offboarding path.

Tenant boundary
Use the website domain and token created for the intended CMS Max tenant.
Least necessary access
Use the interface and workflow needed for the job; avoid collecting or moving unrelated data.
Secret lifecycle
Protect tokens in a secret store, rotate them when required, and revoke them when a client or project ends.
Operational evidence
Retain useful request, delivery, reconciliation, and change records without exposing sensitive values.

Start with the right resource

Move from platform discovery to a scoped implementation.

Public referenceCMS Max APIReview current resources, request shapes, and documented endpoints. AuthenticationAPI access guideCreate and manage an API client from the CMS Max website administration. AI operationsMCP server guideConnect an MCP-capable client and understand the tenant-scoped tool groups. ImplementationPartner with CMS MaxPlan a supported integration, customer implementation, or technology partnership.

Developer platform FAQ

Questions about CMS Max APIs, MCP, and integrations.

Confirm current access, resources, limits, and implementation scope for the specific CMS Max website.

How is a CMS Max API client authenticated?

A website administrator creates an API client and token in CMS Max. Requests send the token as a bearer credential to the intended website domain. Tokens should be stored as secrets and can be revoked from the administration interface.

What does the public CMS Max API cover?

The current public reference includes documented resources for products, variations, categories, variants, brands, images, files, orders, blogs, users, pages, coupons, form submissions, and several webhook or operational endpoints.

What is the CMS Max MCP server for?

The MCP server lets an authenticated MCP-capable client discover and use tenant-scoped tools for supported website content, sections, layouts, navigation, shortcodes, and theme configuration.

Does an API or MCP token work across every CMS Max website?

No. CMS Max resolves the tenant from the website domain and validates the token against that tenant. Create and use credentials for the intended website.

Can CMS Max send data to other applications?

Supported plugins, webhooks, Zapier triggers, API workflows, and partner integrations can deliver or synchronize data according to the installed capability and implementation.

Can CMS Max help design a custom integration?

CMS Max can evaluate a connection based on the business workflow, customer demand, available API or file interface, security, data ownership, implementation complexity, testing, partner cooperation, and ongoing support.

Build on CMS Max

Connect the platform to the systems that make the website operational.

Bring the use case, data contract, source systems, owners, security requirements, launch plan, and support model into one technical discovery.

Start technical discoveryBrowse integrations

Building Relationships with Web Developers and Marketing Agencies that want better results

The world's fastest and most SEO friendly website code.

VIEW PACKAGES