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

- slug: developers
- locale: en-US
- localeResolved: en-US
- canonical: https://www.merchandaise.com/en-us/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
- **API docs:** Review human-readable docs and machine-readable OpenAPI contracts for planning, testing, and versioned release management. (Open API docs: /api/docs)
- **Community embed API:** Implement locale-safe storefront embeds, community workflows, and authenticated handoffs with a versioned public contract. (Open community contract: /api/v1/community/public/openapi/v1)
- **Supplier API:** Connect onboarding, catalog, and supplier-side operations through versioned endpoints built for fulfillment workflows. (Open supplier contract: /api/v1/supplier/openapi/v1)
- **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. (Open enterprise identity contract: /api/v1/enterprise/identity/openapi/v1)
- **MCP tools:** Expose approved MerchandAise capabilities to AI agents through discoverable MCP-compatible tool definitions and execution endpoints with assistant authorization. (Open MCP tools endpoint: /api/v1/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.

## 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-us/contact
- **Explore enterprise platform:** /en-us/enterprise