### App Installation Redirect URL Source: https://developers.29next.com/docs/apps/oauth/getting-started After a user authorizes the app installation, they are redirected to this URL. It includes the network domain of the store and the authorization code. ```URL https://yourapp.com/setup/authorize/?store={network_domain}&code={authorization_code} ``` -------------------------------- ### Storefront Extension Apps Guide Source: https://developers.29next.com/docs/tags/guide Get started building apps that extend storefront functionality by understanding core app framework concepts and their usage. -------------------------------- ### Reusable Partials Include Example Source: https://developers.29next.com/docs/storefront/themes Demonstrates how to include reusable code snippets (partials) like a footer into another template using the `include` template tag. ```html {%include"partials/footer.html"%} ``` -------------------------------- ### Install App Kit using pip Source: https://developers.29next.com/docs/apps/app-kit This command installs the App Kit Python package from PyPi, assuming you have Python and pip installed. It's the primary method for getting the tool onto your system. ```shell pip install next-app-kit ``` -------------------------------- ### Partials Directory Structure Source: https://developers.29next.com/docs/storefront/themes Illustrates the `partials` directory, which stores reusable template fragments like headers, footers, and pagination components. ```tree partials ├── header.html ├── footer.html └── pagination.html ``` -------------------------------- ### Locale Translation Files Source: https://developers.29next.com/docs/storefront/themes Provides an example of the `locales` directory structure, containing JSON files for theme translations, named according to ISO 639-1 language codes, with a `.default` suffix for the fallback language. ```tree locales ├── en.default.json ├── de.json ├── es.json ├── it.json └── fr.json ``` -------------------------------- ### Response with Access Token Source: https://developers.29next.com/docs/apps/oauth/getting-started This is a successful response from the token endpoint, containing the access token, token type, expiration time, scope, and refresh token. ```JSON { "access_token":"{access_token}", "expires_in":15778476000, "token_type":"Bearer", "scope":"{scopes}", "refresh_token":"{refresh_token}" } ``` -------------------------------- ### Server to Server App OAuth Configuration Example Source: https://developers.29next.com/docs/apps/guides/server-to-server-apps This snippet demonstrates how to configure OAuth 2.0 URLs for a Server to Server app. It involves setting the App URL and Redirect URL to a debugger to simulate the app installation flow. ```text In **App > Settings** add `https://oauthdebugger.com/debug` as your App URL and Redirect URL to configure you app to use oauth debugger. ``` -------------------------------- ### Example Admin API Request Source: https://developers.29next.com/docs/api/admin An example cURL command to make a GET request to the Admin API. It includes the necessary Authorization header with an access token and the X-29Next-Api-Version header. ```bash curl -X GET "https://{store}.29next.store/api/admin/" \ -H "Authorization: Bearer " \ -H "X-29Next-Api-Version: 2024-04-01" ``` -------------------------------- ### Asset URL Filter Example Source: https://developers.29next.com/docs/storefront/themes Demonstrates how to use the `asset_url` template filter to generate the correct path for static asset files like CSS within your theme templates. ```html {{'css/style.css'|asset_url}} ``` -------------------------------- ### Theme Settings Configuration Source: https://developers.29next.com/docs/storefront/themes Illustrates the configuration files used for theme settings: `settings_schema.json` for generating the settings form and `settings_data.json` for storing the actual settings. ```tree configs ├── settings_data.json └── settings_schema.json ``` -------------------------------- ### Install Theme Kit Source: https://developers.29next.com/docs/storefront/themes/theme-kit Installs the Theme Kit Python package using pip. Ensure you have Python and pip installed. ```Shell pip install next-theme-kit ``` -------------------------------- ### Checkout Customization Source: https://developers.29next.com/docs/storefront/themes Shows the directory structure for customizing the checkout process by overriding the default `checkout.html` template. ```tree checkout └── checkout.html ``` -------------------------------- ### Storefront Theme Structure Source: https://developers.29next.com/docs/storefront/themes This outlines the standard directory structure for a Storefront theme, organizing assets, checkout files, configurations, layouts, locale translations, reusable partials, templates, and SCSS files. ```tree theme ├── assets ├── checkout ├── configs ├── layouts ├── locales ├── partials ├── sass └── templates ``` -------------------------------- ### OAuth Authorization URL Source: https://developers.29next.com/docs/apps/oauth/getting-started This URL is used to initiate the OAuth 2.0 authorization flow. It includes parameters for response type, client ID, redirect URI, and requested scopes. ```URL https://{network_domain}/oauth2/authorize/?response_type=code&client_id={client_id}&redirect_uri={redirect_uri}&scope={scopes} ``` -------------------------------- ### Theme Templates Directory Structure Source: https://developers.29next.com/docs/storefront/themes Displays the comprehensive structure of the `templates` directory, organizing HTML files for various pages like blog posts, product pages, cart, search, and support articles. ```tree templates ├── 403.html ├── 404.html ├── 500.html ├── blog │ ├── index.html │ └── post.html ├── cart.html ├── catalogue │ ├── category.html │ ├── index.html │ └── product.html ├── index.html ├── pages │ └── page.html ├── reviews │ ├── form.html │ ├── index.html │ └── review.html ├── search.html └── support ├── article.html ├── category.html └── index.html ``` -------------------------------- ### Base Layout Template Source: https://developers.29next.com/docs/storefront/themes Shows the `layouts` directory containing the `base.html` file, which serves as the foundational template that other view-specific templates can extend. ```tree layouts └── base.html ``` -------------------------------- ### Next Commerce Admin API: Testing Guide Source: https://developers.29next.com/docs/api/admin/guides Learn how to test integrations on the Next Commerce platform. This guide covers creating Test Orders, Transactions, and Subscriptions through the Admin API or storefront checkout flow. ```English Testing your integration is a critical step when developing on the Next Commerce platform. There are two distinct paths to creating Test Orders, Transactions, and Subscriptions through the Admin API or storefront checkout flow. ``` -------------------------------- ### Example manifest.json Configuration Source: https://developers.29next.com/docs/apps/manifest This snippet shows a complete example of a manifest.json file, including storefront event tracker, theme locations for snippets, and schema for app settings. ```json { "storefront_event_tracker": "tracking.js", "locations": { "storefront": { "global_header": "snippets/global-header.html" } }, "settings_schema": [ { "name": "enable_app", "type": "checkbox", "label": "Enable Custom Optimizer App", "help_text": "", "default": false }, { "name": "example_setting", "type": "text", "label": "Example App Text Setting", "default": "", "required": 1, "help_text": "", "max_length": 250 } ] } ``` -------------------------------- ### Custom Product Templates Guide Source: https://developers.29next.com/docs/tags/guide Best practices for creating and managing custom product templates to handle diverse design requirements for products. -------------------------------- ### Product Metadata Guide Source: https://developers.29next.com/docs/tags/guide Add custom data for products using product metadata to enhance theme template customization and provide structured data for storefront display. -------------------------------- ### Custom Page Templates Guide Source: https://developers.29next.com/docs/tags/guide Best practices for creating and managing custom page templates in the storefront dashboard to meet diverse design requirements. -------------------------------- ### Generate Install Link for Private Apps Source: https://developers.29next.com/docs/apps/oauth/install-flows This snippet shows how to construct an install link for private apps. It requires your store's subdomain and your app's client ID. This link initiates the app installation process within a specific store. ```URL https://{store_subdomain}.29next.store/dashboard/apps/install-app/?client_id={client_id} ``` -------------------------------- ### Access Token Response Example Source: https://developers.29next.com/docs/apps/oauth This example shows the JSON response from the Next Commerce store containing the Access Token and its associated details. ```JSON { "access_token": "{access_token}", "token_type": "bearer", "expires_in": 7200, "refresh_token": "{refresh_token}", "scope": "read_products,write_products" } ``` -------------------------------- ### Apple Pay Admin API Guide Source: https://developers.29next.com/docs/tags/guide Integrate Apple Pay for storefront checkout and Admin API transactions. This guide covers the steps to set up Apple Pay for processing customer payments and receiving order information. -------------------------------- ### PayPal Admin API Guide Source: https://developers.29next.com/docs/tags/guide Integrate PayPal for storefront checkout and Admin API transactions. This guide covers the steps for redirecting customers through PayPal and receiving order information. -------------------------------- ### Product Variants Guide Source: https://developers.29next.com/docs/tags/guide Map product variants and their attributes in the storefront product details template to create user-friendly experiences for customers with complex product options. -------------------------------- ### Retrieve Access Token POST Request Body Source: https://developers.29next.com/docs/apps/oauth/getting-started This JSON payload is sent as the body of a POST request to the token endpoint to exchange the authorization code for an access token. It requires grant type, client ID, client secret, redirect URI, and the authorization code. ```JSON { "grant_type":"authorization_code", "client_id":"{client_id}", "client_secret":"{client_secret}", "redirect_uri":"{redirect_uri}", "code":"{authorize_code}" } ``` -------------------------------- ### Next Commerce Admin API: PayPal Integration Guide Source: https://developers.29next.com/docs/api/admin/guides Integrate PayPal with the Admin API. This guide covers the steps for setting up PayPal transactions, which involve a redirect flow and return order information to your application. ```English PayPal is a fully integrated payment app that is supported both in the storefront checkout, and via the Admin API. PayPal transactions send the customer through a PayPal redirect flow, with the resulting order information provided back to your application. Below are the steps needed to get PayPal set up and working on the Admin API. ``` -------------------------------- ### Authorization Link Example Source: https://developers.29next.com/docs/apps/oauth This example demonstrates how to construct an authorization link to request merchant authorization and required scopes for your app. ```URL https://{shop}.nextcommerce.com/oauth/authorize?client_id={client_id}&redirect_uri={redirect_uri}&scope={scopes}&state={state} ``` -------------------------------- ### Admin API Access Example Source: https://developers.29next.com/docs/apps/oauth This example demonstrates how to use the obtained Access Token to make authenticated requests to the Next Commerce Admin API. ```HTTP GET /admin/api/2023-01/products.json Host: {shop}.nextcommerce.com Authorization: Bearer {access_token} ``` -------------------------------- ### Example Customer Created Webhook Payload Source: https://developers.29next.com/docs/webhooks Illustrates a complete webhook payload for a `customer.created` event, showcasing the detailed data structure for customer information. ```JSON { "api_version": "2023-02-10", "data": { "accepts_marketing": true, "addresses": [], "date_joined": "2021-12-17T14:52:53.715787+07:00", "email": "testing@testing.com", "first_name": "Tester", "id": 32234664, "ip": null, "is_blocked": false, "language": "en", "last_name": "Test", "orders_count": 0, "phone_number": null, "subscriptions_count": 0, "tags": [], "total_spent": null, "user_type": "lead" }, "event_id": "f7eb1338-0934-4cda-8128-d6a77761a368", "event_type": "customer.created", "object": "customer", "webhook": { "events": [ "customer.created" ], "id": 39, "store": "storename", "target": "https://webhook.site/6a880c2a-48db-4e28-a575-294dfee934234" } } ``` -------------------------------- ### App Structure Example Source: https://developers.29next.com/docs/apps/assets This example shows a typical directory structure for a Next Commerce app, including an 'assets' folder for static files, a 'snippets' folder for HTML snippets, and the 'manifest.json' file. ```File Structure your-app ├── assets │ └── my-app.js ├── snippets │ └── global-footer.html └── manifest.json ``` -------------------------------- ### Google Pay Admin API Guide Source: https://developers.29next.com/docs/tags/guide Integrate Google Pay for storefront checkout and Admin API transactions. This guide explains how to process customer payments and receive order information via Google Pay. -------------------------------- ### Access Token Request Example Source: https://developers.29next.com/docs/apps/oauth This example illustrates how your app requests an Access Token from the Next Commerce store using the received Authorization Code. ```HTTP POST /oauth/token Host: {shop}.nextcommerce.com Content-Type: application/json { "grant_type": "authorization_code", "client_id": "{client_id}", "client_secret": "{client_secret}", "redirect_uri": "{redirect_uri}", "code": "{authorization_code}" } ``` -------------------------------- ### Authorization Code Example Source: https://developers.29next.com/docs/apps/oauth This example shows the format of the authorization code received after a user authorizes your app. The code is a temporary credential. ```URL https://{redirect_uri}?code={authorization_code}&state={state} ``` -------------------------------- ### Next Commerce Admin API: Subscription Management Guide Source: https://developers.29next.com/docs/api/admin/guides Manage subscriptions via the Admin API to automate business processes and perform bulk operations. ```English Subscriptions management can be done through Admin API to automate business processes and perform bulk operations. ``` -------------------------------- ### Next Commerce Admin API: Apple Pay Integration Guide Source: https://developers.29next.com/docs/api/admin/guides Integrate Apple Pay with the Admin API. This guide outlines the steps needed to set up Apple Pay transactions, which process customers through the Apple Pay flow and return order information. ```English Apple Pay is a fully integrated payment app, supported both in the storefront checkout, and via the Admin API. Apple Pay transactions process the customer through the Apple Pay payment flow, with the resulting order information provided back to your application. Below are the steps needed to get Apple Pay set up and working on the Admin API. ``` -------------------------------- ### Richtext Setting Example Source: https://developers.29next.com/docs/storefront/themes/settings Shows a 'richtext' setting, providing a WYSIWYG editor for formatted text content. The value is returned as a string in templates. This example is for a rich text description input. ```json { "type": "richtext", "name": "richtext_content", "label": "Description Content", "help_text": "Example rich text input field." } ``` -------------------------------- ### Admin API Subscription Management Source: https://developers.29next.com/docs/tags/guide Automate business processes and perform bulk operations for subscription management via the Admin API. -------------------------------- ### Next Commerce Admin API: External Checkout Flow Guide Source: https://developers.29next.com/docs/api/admin/guides This guide explains best practices for building an external checkout flow using the Next Commerce Admin API. It highlights the API's flexibility for data and functionality across the platform and external integrations. ```English This guide covers best practices when building an external checkout flow using the Next Commerce Admin API. Using the API gives you the most flexibility of data and functionality across the platform and external integrations. ``` -------------------------------- ### Radio Setting Example Source: https://developers.29next.com/docs/storefront/themes/settings Demonstrates a 'radio' setting, used for option selection like layout styles. The value is returned as a string in templates. This example shows options for 'Boxed' and 'Full Width' layouts. ```json { "type": "radio", "name": "layout", "label": "Layout Style", "help_text": "Control the layout style.", "options": [ { "name": "Boxed", "value": "boxed" }, { "name": "Full Width", "value": "full" } ], "default": "boxed" } ``` -------------------------------- ### Textarea Setting Example Source: https://developers.29next.com/docs/storefront/themes/settings Explains a 'textarea' setting, providing a multi-line input field for longer text content, such as sub-headings. The value is returned as a string in templates. This example is for a description textarea. ```json { "type": "textarea", "name": "description", "label": "Description", "help_text": "Example input textarea", "default": "Example long multi-line sub-heading text for the banner." } ``` -------------------------------- ### URL Setting Example Source: https://developers.29next.com/docs/storefront/themes/settings Showcases a 'url' setting, which is an input field for fully qualified URLs, usable for relative paths or external links. The value is returned as a string in templates. This example is for a social media link. ```json { "type": "url", "name": "social_link", "label": "Social Media Link", "help_text": "Link to your social media page.", "default": "" } ``` -------------------------------- ### Select Setting Example Source: https://developers.29next.com/docs/storefront/themes/settings Details a 'select' setting, which creates a dropdown for option selection, similar to radio buttons. The value is returned as a string in templates. This example configures header style selection. ```json { "type": "select", "name": "header_style", "label": "Header Style", "help_text": "Choose header layout style.", "options": [ { "name": "Full Width", "value": "full" }, { "name": "Boxed", "value": "boxed" }, { "name": "Overlay", "value": "overlay" } ], "default": "full" } ``` -------------------------------- ### Text Setting Example Source: https://developers.29next.com/docs/storefront/themes/settings Presents a 'text' setting, which is a single-line input field for short text entries like banner headings. The value is returned as a string in templates. This example is for a store name input. ```json { "type": "text", "name": "store_name", "label": "Store Name", "help_text": "Public name for your store.", "max_length": 250, "required": true, "default": "My New Store Name" } ``` -------------------------------- ### App Kit CLI Commands Source: https://developers.29next.com/docs/apps/app-kit These are the core commands for the App Kit CLI. 'nak setup' configures your directory, 'nak build' creates a zip file for your app, and 'nak push' deploys the latest version to the Next Commerce platform. ```shell nak setup nak build nak push ``` -------------------------------- ### Get Last Item from List (Liquid) Source: https://developers.29next.com/docs/storefront/themes/templates/filters The last filter retrieves the final element from a list. The example illustrates getting the last character from a list. ```Liquid {{value|last}} ``` -------------------------------- ### Get Localized Language Name (Liquid) Source: https://developers.29next.com/docs/storefront/themes/templates/filters The language_name_local filter returns the localized name of a given language code. The example shows how to get the French name for 'fr'. ```Liquid {{LANGUAGE_CODE|language_name_local}} ``` -------------------------------- ### Retrieve Order Lines Example Source: https://developers.29next.com/docs/api/admin/guides/order-management An example request to the ordersRetrieve endpoint to fetch order line items. This is the first step in processing order refunds, allowing you to get details like quantity and availability for each line item. ```javascript GET https://{store}.29next.store/api/admin/orders/{number}/ ``` ```json { "lines":[ { "id":1000,// order line item "quantity":3,// quantity in the order "current_quantity":3// quantity available and not yet removed from the order } ] } ``` -------------------------------- ### Get First Item from List (Liquid) Source: https://developers.29next.com/docs/storefront/themes/templates/filters The first filter returns the initial element of a list. The example shows retrieving the first item from a list of characters. ```Liquid {{value|first}} ``` -------------------------------- ### Build App Bundle Command Source: https://developers.29next.com/docs/apps/guides/storefront-extension Demonstrates the command-line instruction using App Kit to create a build of your application files for deployment. ```bash nak build ``` -------------------------------- ### Slice List Elements (Liquid) Source: https://developers.29next.com/docs/storefront/themes/templates/filters The slice filter extracts a portion of a list based on start and end indices. The example shows slicing to the first two elements. ```Liquid {{some_list|slice:":2"}} ``` -------------------------------- ### Theme Kit CLI Commands Source: https://developers.29next.com/docs/storefront/themes/theme-kit Common Theme Kit commands for initializing, listing, checking out, pulling, pushing, watching, and processing Sass files for storefront themes. ```Shell ntk init ntk list ntk checkout ntk pull ntk push ntk watch ntk sass ``` -------------------------------- ### Parse Order Data in Python Source: https://developers.29next.com/docs/api/admin/guides/3ds2 After payment completion, your application receives order data via a POST request. This Python example demonstrates how to parse the JSON data from the 'response' key. ```python import json def order_receiver_view(request): data = json.loads(request.POST.get("response")) ... return HttpResponse(status=201) ``` -------------------------------- ### Receive Order Data - Python Example Source: https://developers.29next.com/docs/api/admin/guides/apple-pay Parses the order data received via a POST request. The data is expected in the 'response' key and is JSON-encoded. Handles successful and unsuccessful payment collection scenarios. ```Python import json def order_receiver_view(request): data = json.loads(request.POST.get("response")) ... return HttpResponse(status=201) ``` -------------------------------- ### Receive Order Data - Python Example Source: https://developers.29next.com/docs/api/admin/guides/stripe-apms Demonstrates how to parse the order data received via a POST request after a customer completes a Stripe APM payment. The data is expected in the 'response' key and is JSON-encoded. ```python import json def order_receiver_view(request): data = json.loads(request.POST.get("response")) ... return HttpResponse(status=201) ``` -------------------------------- ### Parse Google Pay Order Data (Python) Source: https://developers.29next.com/docs/api/admin/guides/google-pay Example Python code demonstrating how to parse the order data received via a POST request after a customer completes a Google Pay payment. The data is expected in the 'response' key and is JSON formatted. ```Python import json def order_receiver_view(request): data = json.loads(request.POST.get("response")) ... return HttpResponse(status=201) ``` -------------------------------- ### Server to Server (S2S) App Development Source: https://developers.29next.com/docs/apps This guide covers server-to-server app development, including OAuth flows, session tokens, remote settings, and webhook setup and verification. It's essential for apps that require backend integration with the Next Commerce platform. ```javascript // Example: OAuth Flow (Conceptual) async function getAccessToken(clientId, clientSecret, authCode) { const response = await fetch('/oauth/token', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ grant_type: 'authorization_code', client_id: clientId, client_secret: clientSecret, code: authCode }) }); const data = await response.json(); return data.access_token; } ``` ```python # Example: Webhook Verification (Conceptual) import hmac import hashlib def verify_webhook(request_body, signature, secret) -> bool: expected_signature = hmac.new(secret.encode('utf-8'), request_body, hashlib.sha256).hexdigest() return hmac.compare_digest(expected_signature, signature) ``` -------------------------------- ### App File Structure Example Source: https://developers.29next.com/docs/apps/guides/storefront-extension Illustrates the basic file structure for a storefront extension app, including the assets directory with a JavaScript file and the manifest.json file. ```bash your-app ├── assets │ └── my-app.js └── manifest.json ``` -------------------------------- ### 3DS2 Admin API Guide Source: https://developers.29next.com/docs/tags/guide Process customer authentication flows for 3DS2 payments using the Admin API. This guide details how to obtain transaction information and results. -------------------------------- ### Server to Server Apps with Admin APIs Source: https://developers.29next.com/docs/tags/guide Leverage the OAuth flow to obtain API access for Server to Server apps, enabling subscription to store event activity using Admin APIs and Webhooks. -------------------------------- ### Stripe APMs Admin API Guide Source: https://developers.29next.com/docs/tags/guide Process customer payments using Stripe Alternative Methods (APMs) via the Admin API. This guide covers redirect flows and receiving order information. -------------------------------- ### Support URL and Template Paths Source: https://developers.29next.com/docs/storefront/themes/templates/urls-and-template-paths Outlines the URL structures and template files for the support section, covering category listings, article listings within categories, and individual article details. It uses slugs for dynamic routing. ```HTML URL Name | URL Path | Template Path ---|---|--- support:cateogry-list | /support/categories/ | templates/support/index.html support:article-list | /support/categories/:category_slug/ | templates/support/category.html support:article-detail | /support/articles/:article_slug/ | templates/support/article.html ``` -------------------------------- ### Next Commerce Admin API: 3DS2 Payments Guide Source: https://developers.29next.com/docs/api/admin/guides Process 3DS2 payments via the Admin API. This guide explains how customers are processed through an authentication flow, with final transaction information provided back to your application. ```English 3DS2 payments are fully supported via the Admin API to process the customer through an authentication flow, with the final transaction information and results provided back to your application. ``` -------------------------------- ### Next Commerce Admin API: Stripe APMs Integration Guide Source: https://developers.29next.com/docs/api/admin/guides Integrate Stripe Alternative Methods (APMs) with the Admin API. This guide covers transactions that process customers through a redirect flow, returning order information to your application. ```English Stripe Alternative Methods (APMs) are a fully integrated payment methods supported both in the storefront checkout and the Admin API. Stripe APM transactions process the customer through a redirect flow with the resulting order information provided back to your application. ``` -------------------------------- ### Blog URL and Template Paths Source: https://developers.29next.com/docs/storefront/themes/templates/urls-and-template-paths Defines the URL structure and corresponding template files for blog listings and individual blog posts. It maps a URL name to a specific URL path and its associated template file. ```HTML URL Name | URL Path & Arguments | Template Path ---|---|--- blog:blog-list | /blog/ | templates/blog/index.html blog:blog-detail | /blog/detail/:post_slug/ | templates/blog/post.html ``` -------------------------------- ### Next Commerce Admin API: Google Pay Integration Guide Source: https://developers.29next.com/docs/api/admin/guides Integrate Google Pay with the Admin API. This guide details the steps for setting up Google Pay transactions, which process customers through the Google Pay flow and provide order information back to your application. ```English Google Pay is a fully integrated payment app, supported both in the storefront checkout, and via the Admin API. Google Pay transactions process the customer through the Google Pay payment flow, with the resulting order information provided back to your application. Below are the steps needed to get Google Pay set up and working on the Admin API. ``` -------------------------------- ### Reviews URL and Template Paths Source: https://developers.29next.com/docs/storefront/themes/templates/urls-and-template-paths Details the URL patterns and template files for managing product reviews, including listing reviews, viewing a specific review, and adding a new review. It utilizes product slugs and review IDs for routing. ```HTML URL Name | URL Path & Arguments | Template Path ---|---|--- catalogue:reviews-list | /catalogue/:product_slug/reviews/ | templates/reviews/index.html catalogue:reviews-detail | /catalogue/:product_slug/reviews/:id/ | templates/reviews/review.html catalogue:reviews-add | /catalogue/:product_slug/reviews/add/ | templates/reviews/form.html ``` -------------------------------- ### Dispute Service Apps Integration Source: https://developers.29next.com/docs/tags/guide Integrate dispute service apps to manage payment dispute processing, including alerts and chargebacks, seamlessly within the platform. -------------------------------- ### Example Context Object (JSON) Source: https://developers.29next.com/docs/storefront/event-tracking Illustrates the structure of a context object used in event tracking, containing data from the parent frame's document, navigator, and window objects. ```json { "context":{ "document":{...},// frame parent document "navigator":{...},// frame parent navigator "window":{...}// frame parent window } } ``` -------------------------------- ### Next Commerce Admin API: Order Management Guide Source: https://developers.29next.com/docs/api/admin/guides Automate order management operations through the Admin API for efficient processing and bulk actions on large quantities of orders. ```English Order management operations can be automated through the Admin API for more efficient operations and bulk actions on large quanities of orders. ``` -------------------------------- ### Admin API Webhook Usage for Events Source: https://developers.29next.com/docs/apps/review This snippet demonstrates the recommended practice of using webhooks to listen for events instead of polling the Admin APIs. It specifically mentions subscribing to the `app.uninstalled` event for cleanup. ```text Your app uses webhooks for listening to events instead of polling the Admin APIs. Your app subscribes to the `app.uninstalled` webhook event for handling uninstall clean up on your end. ```