# API and integrations for custom merchandise | MerchandAise

- slug: developers-api-integrations
- locale: en-US
- localeResolved: en-US
- canonical: https://www.merchandaise.com/en-us/developers/api-integrations

Use MerchandAise API and integration pages for OpenAPI docs, community embeds, supplier workflows, enterprise identity, and production launch planning.

## What this page covers
This is the crawlable entry point for teams evaluating MerchandAise API and integration work. It separates human planning links from public machine contracts so developers, search engines, and AI assistants can cite the right surface.
Use it when you need storefront embeds, supplier operations, enterprise identity, or a versioned OpenAPI contract before moving into implementation.

## API and integration surfaces
- **API docs:** Review human-readable docs and machine-readable OpenAPI contracts for planning, testing, and versioned release management. Human guide: Read API docs (/api/docs). Machine-readable contract: OpenAPI JSON (/api/docs/openapi.json). Access: public. Public machine-readable OpenAPI JSON for client generation and contract review. Canonical page: /developers/api-integrations. Canonical section: /developers/api-integrations#api-docs.
- **Community embed API:** Implement locale-safe storefront embeds, community workflows, and authenticated handoffs with a versioned public contract. Human guide: Explore community workflows (/en-us/community). Machine-readable contract: Open community contract (/api/v1/community/public/openapi/v1). Access: public. Public contract for storefront embeds, community discovery, and locale-aware handoffs. Canonical page: /developers/api-integrations. Canonical section: /developers/api-integrations#community-integrations.
- **Supplier API:** Connect onboarding, catalog, and supplier-side operations through versioned endpoints built for fulfillment workflows. Human guide: Explore partner workflow (/en-us/partners). Machine-readable contract: Open supplier contract (/api/v1/supplier/openapi/v1). Access: public. Public versioned contract for supplier onboarding, catalog, and fulfillment workflows. Canonical page: /developers/api-integrations. Canonical section: /developers/api-integrations#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: Explore enterprise platform (/en-us/enterprise). Machine-readable contract: Open enterprise identity contract (/api/v1/enterprise/identity/openapi/v1). Access: protected. Protected contract for approved enterprise workspaces; request access before using this endpoint. Canonical page: /developers/api-integrations. Canonical section: /developers/api-integrations#enterprise-integrations.

## Production implementation checklist
- **Step 1: Choose the right contract surface:** Match the integration to the user journey first: community embeds for public storefronts, supplier APIs for fulfillment workflows, and enterprise identity for SSO, SCIM, and governed rollouts.
- **Step 2: Generate and test against versioned contracts:** Use the published OpenAPI JSON for client generation, contract review, staging validation, and regression testing before production traffic is enabled.
- **Step 3: Confirm access, callbacks, and rollback paths:** Document authentication scopes, callback URLs, environment boundaries, observability, and rollback ownership before launch.

## Production safeguards
- **Clear contract ownership:** Each integration surface links to the human workflow and the machine-readable contract separately, reducing ambiguity during implementation and reviews.
- **Locale-safe discovery:** The page is localized, included in locale sitemaps, and linked from global navigation so teams and search engines can discover it directly.
- **Access boundaries:** Public contracts are linked directly. Protected enterprise contracts are described without implying anonymous production access.

## FAQ
- **Which MerchandAise API should I start with?:** Start with the surface that matches the user journey: community embeds for storefront experiences, supplier APIs for fulfillment workflows, and enterprise identity APIs for SSO or SCIM rollouts.
- **Are the API contracts public?:** Core OpenAPI, community, and supplier contracts are public. Enterprise identity contracts are protected and require approved enterprise access before use.
- **Can AI assistants use this page?:** Yes. The page exposes a dedicated LLM feed, canonical metadata, structured data, and stable links to human guides and machine-readable contracts.

## Need an integration review?
Share the workflow, target environment, authentication needs, and launch timeline. The integrations team will recommend the correct contract surface and rollout path.
- **Talk to integrations team:** /en-us/contact
- **View AI Agents and MCP:** /en-us/developers/ai-agents-mcp