# Developer API, embeds, MCP tools & enterprise integrations | MerchandAise

- slug: developers
- locale: en-GB
- localeResolved: en-GB
- canonical: https://www.merchandaise.com/en-gb/developers

Explore MerchandAise developer APIs for custom merchandise: OpenAPI docs, community embeds, supplier workflows, enterprise identity, and MCP tools for AI agents.

## Developer platform
Use MerchandAise APIs, OpenAPI contracts, community embeds, supplier workflows, enterprise identity, and MCP tools to connect custom merchandise into websites, portals, and AI agents.

## Who builds with MerchandAise
- **Community operators:** Launch embedded storefronts, configurator handoffs, and community flows inside club, league, and company sites with versioned public contracts.
- **Enterprise teams and platform partners:** Connect procurement portals, identity systems, and internal operations to merchandise workflows without rebuilding approval and supplier logic.
- **AI agent and automation builders:** Give assistants structured tool access for discovery, quoting, and approved operations through MCP-compatible endpoints.

## Integration surfaces and contracts
- **Assistant tooling API docs:** Read the assistant/tooling OpenAPI docs that support design sessions, tool use, and integration reviews. Community, supplier, and enterprise contracts are listed separately. Human guide: Open assistant tooling docs (/en-gb/developers/api-integrations). Machine-readable contract: Assistant tooling OpenAPI JSON (/api/docs/openapi.json). Access: public. Public machine-readable OpenAPI for assistant/tooling APIs; use the domain-specific contracts below for community, supplier, and enterprise implementation. Canonical section: /developers#api-docs.
- **Community embed API:** Implement locale-safe storefront embeds, community workflows, and authenticated handoffs with a versioned public contract. Human guide: Review community integration guide (/en-gb/developers/api-integrations#community-integrations). Machine-readable contract: Community OpenAPI JSON (/api/v1/community/public/openapi/v1). Access: public. Public contract for storefront embeds, community discovery, and locale-aware handoffs. Canonical section: /developers#community-integrations.
- **Supplier API:** Connect onboarding, catalog, and supplier-side operations through versioned endpoints built for fulfillment workflows. Human guide: Review supplier integration guide (/en-gb/developers/api-integrations#supplier-integrations). Machine-readable contract: Supplier OpenAPI JSON (/api/v1/supplier/openapi/v1). Access: public. Public versioned contract for supplier onboarding, catalog, and fulfillment workflows. Canonical section: /developers#supplier-integrations.
- **Enterprise identity API:** Integrate SSO, SCIM provisioning, and audit-ready identity flows for enterprise rollouts and governance through a protected contract for approved enterprise access. Human guide: Review enterprise integration guide (/en-gb/developers/api-integrations#enterprise-integrations). Machine-readable contract: Enterprise identity OpenAPI JSON (/api/v1/enterprise/identity/openapi/v1). Access: protected. Protected contract for approved enterprise workspaces; request access before using this endpoint. Canonical section: /developers#enterprise-integrations.
- **MCP server card and authorized tools:** Plan AI-agent integrations on the browser-safe MCP guide page, use the AI custom product designer pillar for intent-to-product context, then use the public server-card JSON for machine discovery and assistant-authorized endpoints for tool listing and execution. Human guide: Read MCP implementation guide (/en-gb/developers/ai-agents-mcp). Machine-readable contract: Public MCP server-card JSON (/en-gb/.well-known/mcp/server-card). Access: public. Public discovery document for machine clients. The tools list and tool execution endpoints still require assistant authorization at /api/v1/mcp/tools. Canonical section: /developers#mcp-tools.

## Integration quickstart
- **Step 1: Choose the contract that matches your workflow:** Start with the surface that matches your user and auth model: community embed, enterprise identity, supplier operations, or MCP tools for assistants.
- **Step 2: Validate auth, versioning, and environment boundaries:** Confirm required headers, scopes, callback expectations, and contract versions in staging before you route production traffic.
- **Step 3: Test end-to-end workflows before launch:** Verify requests, webhooks, provisioning, observability, and rollback paths so the integration is reliable from first live usage.

## Production launch gates for developers
A production integration needs more than a public endpoint. Use these gates to decide whether your workflow is ready for customer, supplier, enterprise, or AI-agent traffic.
- **Sandbox and access review:** Confirm which contracts are public, which enterprise surfaces require approval, and which credentials or workspace roles are needed before launch.
- **Versioned implementation evidence:** Keep generated clients, callback URLs, auth scopes, contract versions, and rollback ownership documented before production traffic is enabled.
- **Operational observability:** Plan logs, retries, support ownership, failure states, and health checks for every workflow that can affect an order, supplier, or enterprise user.

## Need an integration review?
Share your architecture, rollout timeline, and destination channels. We will recommend the right contract surface, auth pattern, and launch sequence.
- **Talk to integrations team:** /en-gb/contact?intent=developer-integration-review
- **Explore enterprise platform:** /en-gb/enterprise