# Developer Home Limio gives developers full control over subscription commerce. * **Order orchestration** — Route orders across billing, provisioning, and fulfilment. No middleware to build or maintain. * **APIs and webhooks** — Every commerce touchpoint is programmable. Read the catalog, submit orders, query subscriptions, listen for events. * **Limio SDK** — React hooks for offers, basket, user context, and checkout. The foundation for building custom components in the Page Builder. * **Custom React components** — Build front-end experiences that plug straight into the Page Builder. Business teams configure and deploy them without engineering. * **AI-assisted development** — Claude Code Skills and the Limio MCP Server let your engineers build and ship commerce experiences faster than ever. {% hint style="info" %} **New to Limio?** Start with the [Limio SDK](https://docs.limio.com/developers/limio-sdk/getting-started) to build custom components, the [Orders API](https://docs.limio.com/api) to send your first order, or [Custom Components](https://docs.limio.com/developers/custom-components/custom-components) for the full getting-started guide. {% endhint %} ## Why developers choose Limio {% tabs %} {% tab title="Fits your architecture" %} **Order orchestration routes orders across billing, provisioning, and fulfilment. No middleware.** Limio acts as the commerce orchestration layer. Submit an order once, and Limio routes it to the right systems: Zuora or Stripe for billing, Salesforce for CRM, your fulfilment platform for provisioning, and any internal service via webhooks. You do not need to build or maintain integration glue between these systems. Limio handles sequencing, retries, and error reporting across every step. **How it works:** * Your channel (web, app, call centre, POS) submits an order via the Orders API * Limio breaks the order into processing steps and routes each to the correct system * Webhooks notify your services at every stage: order received, billing confirmed, entitlement granted, fulfilment triggered * Errors are surfaced per step, not as opaque failures {% endtab %} {% tab title="Full control" %} **APIs, SDK, and webhooks over every commerce touchpoint. Nothing is a black box.** Every operation in Limio is accessible programmatically. Read the catalog, submit orders, query subscriptions, and listen for events. No functionality is locked behind a UI. **What you get:** * [**Catalog API**](https://docs.limio.com/api) — Retrieve offers, pricing, and product configuration. * [**Orders API**](https://docs.limio.com/api) — Preview and submit orders from any channel. Supports new subscriptions, offer changes, cancellations, payment updates, gift redemptions, and more. * [**Object API**](https://docs.limio.com/api) — Query active subscriptions, statuses, and history. * [**Webhooks**](https://docs.limio.com/developers/webhooks/overview) — Receive HTTP POST notifications for order events, entitlement changes, subscription updates, and error reporting. * [**Limio SDK**](https://docs.limio.com/developers/limio-sdk/getting-started) — React hooks for accessing catalog data, basket state, user context, and checkout flow from within custom components. {% endtab %} {% tab title="AI-assisted development" %} **Works natively with Claude Code, so your engineers build and ship commerce experiences faster.** Limio integrates with Claude Code through a dedicated Skills plugin. Describe what you want in natural language, and get production-ready React components with full SDK integration. **What AI-assisted development enables:** * Generate Custom Component scaffolding (package.json, index.js, componentStaticProps.js, styles, Storybook stories) from a description * Produce components that use the correct Limio SDK hooks for offers, basket, user data, and checkout * Accelerate onboarding for developers new to the Limio component model * Iterate on component logic and layout without manually referencing SDK documentation [Get started with the Claude Code Skill](https://docs.limio.com/developers/custom-components/claude-code-skill) **Limio MCP Server** The Limio MCP (Model Context Protocol) Server connects AI assistants directly to your Limio environment. Query your catalog, create offers, update pricing, and inspect orders in plain language without leaving your editor. ```bash claude mcp add --transport http limio https://your-tenant.your-domain.com/mcp ``` Authentication uses your existing Limio credentials. No separate account or API key needed. [Set up the MCP Server](https://docs.limio.com/ai/mcp-server/setup) {% endtab %} {% endtabs %} ## What you can build Developers use Limio across three categories of work. Each maps to a distinct set of APIs and tools. ### Integrate Limio into your systems Connect Limio to your existing architecture so that orders, subscriptions, and catalog data flow between systems without manual intervention. | Use case | How | Start here | | ---------------------------- | -------------------------------------------------------------------------------------- | --------------------------------------------------------------- | | Send orders from any channel | Submit orders via the Orders API from web, mobile, POS, call centre, or internal tools | [Orders API](https://docs.limio.com/api) | | Sync catalog data | Pull offers, pricing, and product configuration into your CMS, app, or data warehouse | [Catalog API](https://docs.limio.com/api) | | React to commerce events | Receive webhooks when orders are processed, entitlements change, or errors occur | [Webhooks](https://docs.limio.com/developers/webhooks/overview) | | Query subscription state | Read active subscriptions and their history from downstream systems | [Object API](https://docs.limio.com/api) | ### Build custom front-end experiences Create React components that plug into the Limio Page Builder. Business teams configure and deploy them without engineering involvement. | Use case | Example | Start here | | ------------------------ | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | | Custom pricing displays | Pricing matrix, price calculator, comparison tables | [Custom Components](https://docs.limio.com/developers/custom-components/custom-components) | | Personalised offers | Show different offers based on account status, segment, or geography | [Limio SDK](https://docs.limio.com/developers/limio-sdk/getting-started) | | Third-party integrations | Check inventory, validate addresses, or verify identity during checkout | [External Services](https://docs.limio.com/developers/custom-components/connecting-to-external-service) | | Promotional mechanics | Exit-intent popups, bundle-and-save logic, auto-applied promo codes | [Custom Components](https://docs.limio.com/developers/custom-components/custom-components) | ### Connect custom systems Use webhooks and APIs together to keep Limio in sync with proprietary or legacy systems that are specific to your business. | Use case | How | | ------------------------ | ------------------------------------------------------------------------------------- | | Fulfilment orchestration | Listen for order webhooks, trigger provisioning in your fulfilment platform | | Entitlement management | Receive entitlement-change webhooks to grant or revoke access in your app | | Custom billing flows | Preview orders before submission, then route confirmed orders to your billing system | | Error handling | Subscribe to error webhooks for per-step failure visibility across the order pipeline | ## For Salesforce developers If you are building on the Salesforce platform, Limio provides a managed package that integrates subscription commerce directly into your org. {% tabs %} {% tab title="What you get" %} **Limio for Salesforce** (`i42as` namespace) connects Salesforce Cases, Accounts, Contacts, Opportunities, and custom objects to Limio and Zuora through LWC components embedded in Screen Flows. * LWC components for subscription management, offer changes, cancellations, and payment updates * Apex controllers that route requests to Limio and Zuora APIs via Named Credentials * Screen Flow integration so that business users can launch commerce actions from Cases and Accounts * Zuora hosted payment iframe for PCI-compliant payment method capture All Apex classes enforce `with sharing` and use Named Credentials for external calls. No credentials are stored in code. {% endtab %} {% tab title="Getting started" %} **Prerequisites:** * Salesforce org with API version 62.0 or later * Limio for Salesforce managed package installed * Named Credentials configured: `callout:limio`, `callout:limio_new`, `callout:ZuoraRestMI` **Key resources:** * [Salesforce Integration overview](https://docs.limio.com/integrations/salesforce-integration) * [Release notes and changelog](https://docs.limio.com/release-notes/limio-for-salesforce) * Install the package from the Salesforce AppExchange or contact {% endtab %} {% tab title="Architecture" %} ``` Salesforce (Case / Account / Contact / Opportunity / Limio_Quote__c) -> LWC Components (flow* prefix for Screen Flows) -> Apex Controllers (iHubController, zApiController) -> Limio API (callout:limio) / Zuora API (callout:ZuoraRestMI) ``` * **iHubController** — All Limio requests route through `iHubController.sendLimioRequest()` * **zApiController** — All Zuora requests route through this controller * **iAppException** — Centralised error handling; LWC side uses `toastHandler()` utility * JSON responses from Limio use double underscores (`__limio`) which are normalised to single underscores in Apex via `LimioSubscriptionOffers.formatOffersResponse()` {% endtab %} {% endtabs %} ## For IT: authentication and security If you are responsible for connecting Limio to your identity provider or configuring secure API access, start here. ### Authentication integrations Limio integrates with identity providers for customer-facing authentication on shops and self-service portals. If you need to connect Limio to your SSO, OAuth provider, or identity platform, start here. [Authentication Integrations overview](https://docs.limio.com/developers/api-documentation/authentication-overview/oauth-bearer-token) ### API authentication For API key and OAuth token setup, see the [Authentication overview](https://docs.limio.com/developers/api-documentation/authentication-overview). ## Explore the platform ### Build experiences {% content-ref url="limio-sdk/getting-started" %} [getting-started](https://docs.limio.com/developers/limio-sdk/getting-started) {% endcontent-ref %} {% content-ref url="custom-components/custom-components" %} [custom-components](https://docs.limio.com/developers/custom-components/custom-components) {% endcontent-ref %} {% content-ref url="custom-components/development-guidelines" %} [development-guidelines](https://docs.limio.com/developers/custom-components/development-guidelines) {% endcontent-ref %} ### Integrate your systems {% content-ref url="api-documentation/api" %} [api](https://docs.limio.com/developers/api-documentation/api) {% endcontent-ref %} {% content-ref url="webhooks/overview" %} [overview](https://docs.limio.com/developers/webhooks/overview) {% endcontent-ref %} ### Accelerate with AI {% content-ref url="custom-components/claude-code-skill" %} [claude-code-skill](https://docs.limio.com/developers/custom-components/claude-code-skill) {% endcontent-ref %} {% content-ref url="" %} {% endcontent-ref %} ### Platform and security {% content-ref url="api-documentation/authentication-overview" %} [authentication-overview](https://docs.limio.com/developers/api-documentation/authentication-overview) {% endcontent-ref %} {% content-ref url="" %} {% endcontent-ref %} {% content-ref url="" %} {% endcontent-ref %} ## Need help? * **Email:** * **AI assistant:** Use the "Ask Limio AI" button on any docs page * **Troubleshooting:** [Support & Administration](https://docs.limio.com/support)