> ## Documentation Index > Fetch the complete documentation index at: https://docs.launchmystore.io/llms.txt > Use this file to discover all available pages before exploring further. # App Manifest (app.json) > The canonical reference for every field declared in an app.json manifest # App Manifest Every LaunchMyStore app ships a single `app.json` file at the root of the app package. The manifest declares the app's identity (handle, name, version) and every extension surface and function the app contributes. At install time the platform writes the manifest into `extensions/{domainSlug}/{appHandle}/app.json` per merchant. At render time the storefront, checkout, admin, and customer-account hosts read this file (through the local-manifest cache, 60s TTL) to discover which extensions and functions to load. If `app.json` is missing or unparseable, the app is silently skipped. All keys under `extensions` are **camelCase**. Fields prefixed with `_` (underscore) at any depth are reserved for tooling and ignored at install time. ## Top-level fields Lowercase machine name for the app, e.g. `product-reviews-pro`. Must match the directory name under `extensions/{domainSlug}/`. Uniqueness is enforced per merchant. Human-readable name shown in the merchant admin and the marketplace listing. Semver version string (e.g. `1.4.2`). Used by the versioning system to reconcile installed vs. published builds. Short marketing copy displayed on the marketplace card and admin detail page. Absolute URL to a square icon (PNG/SVG, recommended 256×256). Used by the customizer block picker and admin sidebar. Publisher name displayed on the marketplace listing. Public website URL for the publisher. Base URL the merchant is redirected to after install completes (the app's embedded admin entry point). OAuth scopes the app requires (e.g. `read_products`, `write_orders`). See [OAuth scopes](/getting-started/authentication#scopes). Container for every extension/function the app contributes. See the per-key tables below. ### Minimal example ```json theme={null} { "handle": "my-app", "name": "My App", "version": "1.0.0", "extensions": {} } ``` ## Extensions The `extensions` object groups every extensible surface the app contributes. Every key is optional; an app can use as few or as many as it needs. | Key | Type | Purpose | Page | | --------------------------- | ----- | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | | `storefrontBlocks` | array | Liquid blocks merchants drop into theme sections | [Theme Blocks](/extensions/theme-blocks) | | `storefrontSnippets` | array | Reusable Liquid includes (`{% render 'foo' %}`) | [Storefront Snippets](/extensions/storefront-snippets) | | `storefrontEmbeds` | array | Overlay/floating scripts injected at `` or before `` | [Storefront Embeds](/extensions/storefront-embeds) | | `appScripts` | array | JS files auto-injected on every storefront page | [App Scripts](/extensions/app-scripts) | | `checkoutExtensions` | array | Sandboxed iframe at a named slot inside the checkout | [Checkout UI](/extensions/checkout-ui) | | `postPurchaseExtensions` | array | Iframe rendered on the order status (thank-you) page right after checkout | [Post-Purchase](/extensions/post-purchase) | | `adminExtensions` | array | Iframe embedded on admin resource detail pages | [Admin Blocks](/extensions/admin-blocks) | | `adminActions` | array | Button on an admin resource page that opens a modal iframe (install-only — persisted as per-handle schema files) | [Admin Actions](/extensions/admin-actions) | | `printActions` | array | Button that opens a printable view (install-only — persisted as per-handle schema files) | [Admin Print Actions](/extensions/admin-print-actions) | | `customerAccountExtensions` | array | Iframe blocks on the new customer-account pages | [Customer Account](/extensions/customer-account) | | `webPixels` | array | Sandboxed customer-event listener scripts | [Web Pixels](/extensions/web-pixel) | | `posExtensions` | array | Iframe extensions for the Point-of-Sale app | [POS Extensions](/extensions/pos-extensions) | | `functions` | array | Declarative WASM functions (cart transform, discount, shipping, etc.) | [Functions Overview](/functions/overview) | | `orderRoutingRules` | array | JSON matchers that pick a fulfillment location at order placement | [Order Routing](/extensions/order-routing) | | `emailTemplates` | array | Override transactional emails for named events (install-only) | [Email Templates](/extensions/email-templates) | `adminActions`, `printActions`, and `emailTemplates` are accepted by the install endpoint but are **not** stored inline in `app.json` after install — they are persisted as per-handle schema files under `admin-actions/`, `print-actions/`, and `email-templates/` respectively, and surfaced through the `admin-extensions` API. ### storefrontBlocks Liquid blocks merchants insert into theme sections via the customizer. Each entry produces a `blocks/{handle}.aqua` template and a `blocks/{handle}.schema.json` block schema. ```json theme={null} "storefrontBlocks": [ { "handle": "product-reviews", "title": "Product Reviews", "target": "product", "schema": { "name": "Product Reviews", "settings": [ { "id": "limit", "type": "range", "min": 1, "max": 50, "default": 10, "label": "Reviews per page" } ] } } ] ``` | Field | Type | Purpose | | -------- | ------ | ------------------------------------------------------------------------------ | | `handle` | string | Required. Block machine name. Becomes the filename (`blocks/{handle}.aqua`). | | `title` | string | Display label in the customizer block picker. | | `target` | string | Template the block can be inserted into (`product`, `index`, `collection`, …). | | `schema` | object | Theme-block schema (`name`, `settings[]`, `presets[]`). | See [Theme Blocks](/extensions/theme-blocks) for the full block schema spec, supported setting types, and target reference. ### storefrontSnippets Reusable Liquid partials any theme block or section can `{% render %}`. Snippet handles share a single global namespace across all installed apps — the install endpoint logs a warning when two apps register the same handle and the filesystem-order winner is unpredictable. Prefix your handles with the app handle to be safe. ```json theme={null} "storefrontSnippets": [ { "handle": "my-app-stars", "description": "Renders a 5-star rating" } ] ``` | Field | Type | Purpose | | ------------- | ------ | --------------------------------------------------- | | `handle` | string | Required. `{% render 'my-app-stars' %}` invokes it. | | `description` | string | Optional documentation displayed in the admin. | ### storefrontEmbeds Overlay/floating scripts (chat widgets, cookie banners, A/B tools) injected at ``, `body`, or `compliance_head` based on the `target` field. Merchants toggle each embed on/off in the customizer "App embeds" tray. ```json theme={null} "storefrontEmbeds": [ { "handle": "review-popup", "title": "Review Popup", "target": "body", "scriptSrc": "https://my-app.example.com/embed.js", "schema": { "name": "Review Popup", "settings": [] } } ] ``` | Field | Type | Purpose | | ------------- | ------ | ------------------------------------------------------------------------------- | | `handle` | string | Required. Unique per app. | | `target` | string | `head` \| `body` \| `compliance_head`. Default `body`. | | `scriptSrc` | string | Absolute URL to a JS file (loaded with `