> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/limio-commerce-release-notes/limio-commerce-release-notes/releases.md).

# Release Change Log (118+)

Every customer-facing change to Limio Commerce, newest first. Subscribe with the RSS button at the top of this page to get each release as it ships.

{% updates format="full" %}
{% update date="2026-11-09" tags="Fix" %}

## v118.0.87

**Fix** — **Clearing or swapping items on a partner checkout page failed.** On a partner page, the SDK's clear-basket and swap-offer calls sent the request to the standard shop route instead of the partner route. The shop route rejected them with a `422` error, so the basket could not be changed. Both calls now go to the partner route and succeed.

**Fix** — **A security vulnerability in the add\_charge order handler has been closed.** The `add_charge` order type contained a flaw in which the ownership check ran against one subscription while the charge schedule was written to a different one. The order type has been removed. The admin button and the charge-schedule job had already been removed in early 2024.

**Fix** — **The chat agent incorrectly said a checkout link was below in a follow-up message.** After giving a checkout link in one message, the agent sometimes told the customer in a later message that the link appeared below — when no link was present. The agent no longer makes this incorrect reference.
{% endupdate %}

{% update date="2026-11-09" tags="Feature,Improvement,Fix" %}

## v118.0.85

**Feature** — **Salesforce connections can use your own OAuth client.** When you configure a Salesforce integration, you can now supply your own OAuth client credentials instead of the shared Limio client. Enter the endpoint, Consumer Key and Consumer Secret in the connection form. Existing connections are unaffected and continue to use the shared client.

**Improvement** — **The Salesforce connection test reports the connected user.** A successful connection test now names the Salesforce user the integration connects as. You can confirm the account without leaving the form.

**Fix** — **Salesforce orders could fail silently when refresh-token rotation was enabled.** If your Salesforce org used single-use refresh tokens, a re-authentication in the same request sometimes sent the already-consumed token. Salesforce rejected it and the order failed without an error. An admin then had to reconnect the integration to restore it. The token is now read from storage on each refresh, so the correct token is always sent.

**Fix** — **Field layout and the Confirm action in the page builder component editor were misaligned.** Form fields in the component editor panels did not line up correctly, and Confirm was not shown as the primary action. The fields now align correctly and Confirm is the main action.
{% endupdate %}

{% update date="2026-11-06" tags="Feature,Improvement,Fix,API" %}

## v118.0.84

**Feature** — **Create and edit promo codes on the catalog item page.** Promo codes can now be created, viewed, and edited directly from a product's catalog item page in the admin app. The rate plan picker in the promo code form now loads all rate plans for a product, not only the first page.

**Feature** — **Synced subscription checkout: renew onto a different offer, or change offer during the term.** At the checkout for a synced subscription, a customer can now renew onto an offer with a different term. They can also switch to a different offer during the active term. In-term changes are queued and take effect at the next billing date.

**Improvement** — **Renewal checkout shows the billing date for each charge.** The renewal preview now shows the billing date for each charge, so a customer can see when each payment will be collected. The offer editor also gains a billing target attribute for configuring when each charge falls.

**Improvement** — **Security update.** A third-party library was upgraded to address a reported vulnerability. No action is needed.

**Fix** — **Promo code discounts could be overridden at checkout.** The order submit step accepted the discount amount from the basket, which an external caller could modify. The discount is now calculated on the server from the promo code record and cannot be changed by the caller.

**Fix** — **The admin order preview showed the wrong discount when a promo code was applied.** The discount in the admin preview was read from the submitted basket rather than from the promo code record, so it did not reflect the correct amount. The preview now reads the discount from the promo code record.

**Fix** — **US and Canadian billing addresses were sent to Zuora without a state.** When a change-offer or change-payment event created or updated a Zuora contact, US and Canadian addresses were sent without a state field. Zuora rejected these updates. The state is now included and sent correctly.

**Fix** — **PayPal showed only an error when the billing country was not available.** At a PayPal-powered checkout, the payment token request was sent before the billing country was confirmed. The request included an empty country and PayPal returned an error. The billing country is now confirmed before the token request is sent.

**Fix** — **Logging out via SSO threw an error when the session cookie was absent.** Calling the SSO logout endpoint without the session cookie caused an unhandled error rather than a clean logout. Logout now completes without error in this case.

**Fix** — **Apple Pay selected the wrong payment gateway.** The Apple Pay gateway was resolved from the admin user's country instead of the shopper's payment country. This could route payments to the wrong gateway. The gateway is now selected from the payment country.

**Fix** — **Shop API requests returned 503 errors after a CloudFront runtime upgrade.** A CloudFront Function that adds request headers contained syntax that the cloudfront-js-2.0 runtime does not accept. All shop `/api/*` requests failed with a 503. The function has been corrected and requests now reach the backend.

**Fix** — **Custom order types were not applied on the shop order route.** The module that resolves custom order types was loaded from an incorrect path. Tenants with custom order type configuration processed orders without the custom logic applied. The module is now loaded from the correct path, and the shop route now accepts custom order types correctly.

**Fix** — **The Salesforce integration could not run connection tests, refresh tokens, or complete PKCE authentication.** The Salesforce connector failed to run a connection test, did not rotate refresh tokens correctly, and could not complete PKCE-based authentication. All three are now resolved.

**Fix** — **Service user accounts can now search the order event index with event read access alone.** `GET /search/elasticEvents` can now be called by a service user that holds event read access, without also requiring the analytics application permission. Previously, the analytics permission was required, which prevented service-user integrations from reading event data. See [Reporting API](https://docs.limio.com/api/reporting-api) in the API reference.
{% endupdate %}

{% update date="2026-10-30" tags="Breaking,Feature,Improvement,Fix,API" %}

## v118.0.76

{% hint style="danger" %}

#### Breaking changes

* The MCP server no longer provides the dedicated offer, page and order tools. If your agents use these tools, update them to use the API search and call tools before you upgrade.
* `GET /search/elasticEvents` now requires the analytics application permission in addition to events read access. A caller whose role lacks analytics access now receives 403. Grant the permission before you upgrade.
  {% endhint %}

**Breaking** — **The dedicated MCP offer, page and order tools have been removed.** The API search and call tools, available since v118.0.59, replace them. Agents configured to use the old offer, page or order MCP tools must be updated to use the API discovery tools instead.

**Breaking** — `GET /search/elasticEvents` now requires both events read access (`object:event:*:read`) and the analytics application permission (`app:subscriptions:analytics`). A caller whose role has events read access but not analytics access now receives `403`. See [Reporting API](https://docs.limio.com/api/reporting-api) in the API reference.

**Feature** — **Limio sends a webhook when you publish the catalog.** After each publish, unpublish or republish, Limio fires a `catalog.publish` webhook. The payload lists each changed item: its record type, identifier, action (`published` or `unpublished`) and version. The webhook fires only after the new index is live, so a read that follows it returns the updated items. Configure the destination URL at Settings > General Settings > Webhooks > Catalog > Catalog Publish.

**Fix** — **The renewal checkout did not send billing details to the Zuora account.** After a renewal checkout, the billing address the customer provided was recorded in Limio but was not sent to Zuora. The Zuora account kept its previous billing details.

**Fix** — **A renewal checkout did not save the new payment method to the Zuora subscription.** When a customer paid a renewal with a new payment method, the method was not saved on the subscription in Zuora. Future automated renewals charged the old method instead.
{% endupdate %}

{% update date="2026-10-28" tags="Feature,Improvement,Fix" %}

## v118.0.74

**Feature** — **Apple Pay now works in non-Safari browsers.** Shoppers can now pay with Apple Pay at checkout in any browser where Apple Pay is available for the device and payment provider. Previously, the Apple Pay button appeared only in Safari.

**Feature** — **Stripe: promo codes at checkout.** Shoppers at a Stripe-powered checkout can now apply a promo code during the purchase flow.

**Improvement** — **Security updates.** Several third-party libraries were upgraded to close reported vulnerabilities, including a critical Brotli vulnerability in the Node runtime. No action is needed.

**Fix** — **A guest order could be linked to an existing customer's account.** During a guest checkout, the order email address was matched to an existing customer account. This put order data on the wrong account. Each guest order now gets its own identity, and the payment-token step verifies basket ownership before it proceeds.

**Fix** — **The shop order route accepted orders that bypassed payment.** A gap in the route allowed an external request to create a subscription and activate entitlements without a completed payment. The route now rejects these requests.

**Fix** — **Offer attributes with long names could not be removed from the table view.** In the catalog table view, a long attribute name overflowed its column and covered the remove button, so the column could not be deselected. Long names now wrap inside the column picker.

**Fix** — **Some interactive components lost their styles on certain design systems.** On design systems that did not include the shared Tailwind tokens, tooltips, radio buttons, and selector cards rendered without their styles. The tokens are now included in all affected design systems.
{% endupdate %}

{% update date="2026-10-21" tags="Feature,Improvement,Fix" %}

## v118.0.68

**Feature** — **Stripe: update your address at checkout.** At a Stripe checkout, you can now update your address before you confirm the order. Previously there was no way to change the address once the checkout started.

**Improvement** — **The settings sidebar now scrolls when the list is too long.** If the settings sidebar holds more items than the screen height, it now scrolls. Previously, items at the bottom were cut off and were not reachable.

**Improvement** — **Security update.** A third-party library was upgraded to close a reported vulnerability. No action is needed.

**Fix** — **The Payments Table stopped working after a Limio upgrade, before the shop was rebuilt.** A page built before Limio 112 caused the Payments Table to fail at checkout after an upgrade. The table now reads its data correctly from pages built in earlier versions.

**Fix** — **The order complete page showed the same subscription number for every item when one order created several subscriptions.** Each item now shows its own subscription number.

**Fix** — **Concurrent shop builds caused 503 errors at the edge.** When two shop builds ran at the same time, they shared a version prefix for page hashes. The edge returned a 503 for any page that a later build overwrote. Each build now uses its own version prefix.

**Fix** — **The admin session was lost when the browser restarted.** The admin session cookie expired when the browser closed, which signed you out on the next browser restart. The session now persists for 30 days.

**Fix** — **Subscriptions synced from Zuora did not renew.** When a subscription was imported into Limio from Zuora, the renewal link was not recorded. The renewal checkout did not identify the subscription and showed no valid options. The link is now recorded at sync time and renewal works correctly.

**Fix** — **Long tags in the Journeys editor overflowed into the next column.** A long Starting point or Fallback tag chip extended past the edge of its column and covered the remove button of the adjacent column. Tags now stay inside their column.

**Fix** — **Form field messages showed the wrong text colour for warning, info and success states.** A FieldMessage in the warning, info or success tone showed the default text colour instead of the colour for that tone. Each tone now shows its correct colour.
{% endupdate %}

{% update date="2026-10-15" tags="Fix" %}

## v118.0.62

**Fix** — **The admin app froze when offer labels were edited.** Changing offer labels on the offer page made the page unresponsive. The offer label table now stays responsive when labels are changed.
{% endupdate %}

{% update date="2026-10-14" tags="Fix" %}

## v118.0.60

**Fix** — **Invoice orders failed at Stripe-powered checkouts.** When a shopper chose the Invoice payment option at a Stripe checkout, the order failed at the payment processing step and no subscription was created. Invoice orders at Stripe checkouts now complete correctly.
{% endupdate %}

{% update date="2026-10-14" tags="Feature,Improvement,Fix" %}

## v118.0.59

**Feature** — **Stripe: saved payment methods, offer payment methods, and add payment method.** The Stripe checkout now shows all payment options that Stripe makes available for your account. Returning shoppers can select a saved card or add a new payment method without leaving the checkout.

**Feature** — **Limio Agents can call the Limio API through MCP.** An agent can now discover available Limio API endpoints through the MCP server and call them directly. This lets you build agents that read and act on your subscription data without a custom integration.

**Feature** — **Agent instructions: formatted view with preview, toolbar, and full-screen editor.** The instructions field in the agent editor now shows formatted Markdown in a preview mode, with a toolbar and a full-screen option. You can switch between the source view and the formatted view at any time.

**Improvement** — **Admin navigation reorganised into a single Settings area.** Settings-related pages are now grouped under a single Settings area in the Limio app navigation, so related configuration is in one place.

**Improvement** — **Journeys screens rebuilt.** The Journeys section of the admin app has been rebuilt to match the current design system, with an updated layout and controls throughout.

**Improvement** — **Chat: agent narration kept as the agent's own messages.** The AI agent now posts its narration as its own messages in the conversation, so the reply thread is easier to follow.

**Improvement** — **Security updates.** Findings from the recent penetration test are resolved. The Viewer and Editor roles had access to several endpoints that their permissions did not cover. These included the order event log, checkout analytics, the permission change audit log, tenant settings, external service keys, and asset uploads. The platform now restricts each to the correct role. The partner organisation logo URL field now rejects non-HTTPS URLs. Limio Agents now refuse out-of-scope requests and do not disclose their underlying model. Third-party libraries were also upgraded to address reported vulnerabilities. No action is needed.

**Fix** — **Page Builder components did not render after a recent update.** A change to source-map injection invalidated the integrity hashes used to load page builder components, so the canvas was blank. Components now load correctly.

**Fix** — **Some users could not sign in after a recent update.** Admin users who signed in with a password were logged out by the device tracking session check. The shop token refresh also used the wrong auth-provider configuration, which caused authentication failures on return visits. Both are now resolved.

**Fix** — **Renewal checkout showed no payment types for Zuora subscriptions.** A subscription created in Zuora showed no payment types at the renewal checkout screen, which stopped the renewal from completing. Payment types now appear correctly.

**Fix** — **Offer labels did not expand and appeared without colour.** The minimised offer label group did not open when clicked, and label colours were not shown. Labels now expand and display in their assigned colours.

**Fix** — **Rate plan and product picklist attributes showed the attribute name twice.** Each name appeared in the column header and again inside the cell on the offer page. Attribute names now appear once.

**Fix** — **A gift code refund was accepted when the code was already used or refunded.** The refund flow did not check whether the code had been redeemed or previously refunded. The check is now in place and the refund is correctly rejected.

**Fix** — **Generating developer credentials could lock SSO admins out of the app.** Saving new developer credentials overwrote the admin user's own email address. An admin who used SSO found that their login no longer worked. The credential save no longer changes user fields it does not own.

**Fix** — **Several Limio Agents chat issues were corrected.** A long URL in a chat reply overflowed the message bubble instead of wrapping. A dropped stream connection caused an error message to appear even though the reply arrived on the server a few seconds later. The agent named its internal tools when a shopper asked how it works. Chat agent preview failed when no search service URL was configured. MCP connector tools failed in live chat when the connector secret could not be read.

**Fix** — **Catalog history was slow to load for items with many commits.** Opening the catalog history triggered a full pack load for each commit, which made the view slow. History now loads without a pack load per commit.
{% endupdate %}

{% update date="2026-09-30" %}

## v118.0.43

**Improvement** — **Browser tab titles.** Every page in the Limio app now sets its own browser tab title, so you can tell tabs apart when several are open.

**Improvement** — **Security update.** The cookies Limio sets are now marked so that JavaScript running on the page cannot read them. No action is needed.

**Fix** — **The Style Editor opened unstyled and covered the page builder header.** In the page builder, the Style Editor rendered without its styles until you clicked Full Screen, and in full screen the page builder header stayed visible behind it. The editor now opens styled, and full screen fills the screen.

**Fix** — **The page builder previewed with the wrong styles.** Components built with CSS modules rendered unstyled, and the page builder loaded the default design system instead of your own. Previews now use your design system and your components' own styles.

**Fix** — **Custom component builds failed.** A build failed for every component when the root tsconfig extended a package the builder does not install, and a bundle failed to load when one of its dependencies required an external package. Both now build and load.

**Fix** — **A shop build stopped on a missing component file.** If a catalog asset URL named a component file that no longer exists, the shop build stopped instead of continuing.

**Fix** — **A template family page showed an error in place of its content.** Opening a template family reported that permissionScope is not defined. The page now loads.

**Fix** — **A dropdown was unreadable on a coloured background.** Form controls took their text colour from whatever sat behind them, so a select on a coloured bar could disappear. Form controls now set their own text colour.
{% endupdate %}

{% update date="2026-09-21" tags="Feature,Improvement,Fix" %}

## v118.0.39

**Feature — Stripe payment provider.** Checkouts can now be routed to Stripe. Select the Stripe integration in your config set and the correct payment path is chosen automatically at runtime.

**Feature — Delete permission.** A delete permission level is now available in data permissions. It is off for every role until you grant it, so existing access is unchanged.

**Feature — Order API: structured failure detail.** When an order fails, the admin order API now returns a structured breakdown of the reason — payment failure detail or risk decision — alongside the status. This makes it easier to surface a clear message to the customer and to route failures programmatically.

**Improvement — Admin session stability.** Admin users were logged out every 30 to 60 minutes due to a session fingerprint mismatch. Sessions now stay valid for the expected duration. The device, network, and location used at sign-in are also recorded, giving your team better visibility when a session behaves unexpectedly.

**Improvement — Created and updated timestamps on user records.** The date each management user record was created and last updated is now recorded and shown in the admin app.

**Improvement — Account avatar in the app header.** Your account avatar now appears in the Limio app header.

**Improvement — Security updates.** A wildcard injection vulnerability in the catalog API location search was closed. Several third-party libraries were also upgraded to address reported vulnerabilities. No action is needed.

**Fix — Shop pages failed to render after rebuild.** After a shop was rebuilt or republished, pages often loaded with no components visible, and the checkout form did not appear on certain design systems. Both issues are resolved and shops now render correctly after every build.

**Fix — Partner checkout page was blank.** The partner checkout displayed a blank page because a basket permission check returned a 403 error. The check is now correct and the page loads.

**Fix — Catalog filter bar picklist.** The picklist dropdown in the catalog filter bar appeared outside the bar, and selected values appeared below the input rather than inside it. Both now render in the correct position.

**Fix — AI Agents list was capped at 25 entries.** The agents list showed only 25 agents in no order and had no way to reach the rest. The list now returns all agents.

**Fix — Deleting an agent did not remove it.** The delete action returned a success response but left the agent in place. The agent is now removed correctly.

**Fix — Rate Plan and Product Code fields did not show the selected value.** Selecting a rate plan or product code in the admin app left the field looking empty. The selected value now appears.

**Fix — Catalog URLs containing placeholders were rejected.** Saving a catalog item was rejected when the checkout URL contained a Handlebars placeholder. Placeholder syntax is now accepted.

**Fix — Missing country codes on payment pages.** Several countries were absent from the payment page country selector, so shoppers from those countries could not complete a purchase. The missing codes are now present.

**Fix — Selected quantity was lost during an upsell swap.** When a shopper swapped an item in the cart, the quantity they had selected was reset. The selected quantity is now carried across the swap.

**Fix — Future-dated subscription offers returned malformed.** Fetching a subscription that included future-dated offers returned a malformed response. Future-dated offers are now included correctly.

**Fix — Order preview failed with unpriced add-ons.** Previewing an order that included an unpriced add-on returned an error. Unpriced items are now excluded from the currency check and the preview completes.

**Fix — Agent outcome editor kept deleted tools active.** Removing a tool from an agent's steps left the tool still applied to the outcome. Deleted tools no longer apply after they are removed.

**Fix — Several checkout journey errors were corrected.** Errors in the purchase link flow, subscription switch flow, and partner checkout flow could prevent a customer from completing their purchase. All three have been corrected.
{% endupdate %}

{% update date="2026-09-02" %}

## v118.0.29

This release contains internal maintenance changes only. No customer-facing behaviour changed in this version.
{% endupdate %}

{% update date="2026-08-28" %}

## v118.0.26

This release contains internal maintenance changes only. No customer-facing behaviour changed in this version.
{% endupdate %}

{% update date="2026-08-28" tags="Improvement,Fix" %}

## v118.0.25

**Improvement** — **AI agent response speed.** Limio Agents now responds to messages faster. Each message no longer waits for background telemetry to flush before the agent sends its response.

**Fix** — **Page Builder block components.** When you added a Block component to a page, the canvas became unresponsive and you were unable to select or edit other components. Block component overlays now stay inside the canvas.

**Fix** — **Catalog offer updates.** Changes made to offers were not applied to the catalog index, so published changes did not appear in the catalog. The catalog indexer now applies offer updates correctly.

**Fix** — **Admin login.** The username field on the admin login screen was labelled "Email" and rejected entries that were not email addresses. The field is now labelled "Username" and accepts any valid username.

**Fix** — **Checkout events.** The `checkout.initiated` event was not recorded when a shopper started a checkout, because the write ran without the required permissions. The event is now recorded correctly.

**Fix** — **Agent editor tab counts.** The item counts on the tabs in the agent editor were not visible. The counts now appear on every tab.
{% endupdate %}

{% update date="2026-08-24" tags="Breaking,Feature,Fix,Improvement" %}

## v118.0.19

#### New Features

**More granular permissions**

Permissions have been rebuilt, so you can be precise about what each role is allowed to do.

* **Choose which parts of Limio a role can reach.** A role no longer sees a page it has no access to
* **Set read and write separately** on each type of record, rather than in bundled groups
* **Scope partners to their own data.** Each partner organisation sees only its own subscriptions and orders
* **The same rules apply everywhere** — the product catalog, publishing, bulk edit, catalog jobs and search, over the API, and through the MCP server, which runs as the user's own login

Your existing access carries over, so every user keeps what they have today.

**Create catalog items from your own systems**

Offers, products, add-ons, discounts and pages can now be created in Limio directly from your own systems, in a single call.

Limio checks each item against your own catalog templates before saving it, so a request that is not valid is refused with a clear reason and nothing half-made is saved.

Previously every item had to be entered by hand. If you add products in volume, this saves a considerable amount of time.

**Limio Agents can take a shopper through to checkout**

* **Hand a shopper a real checkout.** An agent can build a basket for the offer they chose and give them a secure link, so the order ties back to the conversation. Previously the link created nothing in Limio and the sale could not be attributed
* **Set tool behaviour per outcome,** so an agent works differently depending on what a conversation is trying to achieve
* **Conversations survive navigation.** Moving between pages or refreshing no longer loses the thread, so a visitor never re-explains what they want

#### Improvements

**Sign in on your own domain**

Signing in to the Limio app now happens on a Limio-branded page on your own domain.

Previously it used a page hosted by Amazon on a different domain, which password managers treated as a separate site, so credentials were often not saved or filled. Nothing changes in how your team signs in, including single sign-on.

**A dedicated API for placing and previewing orders on a customer's behalf**

Two new endpoints, `/admin/order` and `/admin/order/preview`, let your own systems place an order for a customer and see what it will cost first. Each call runs with the permissions the caller actually holds.

**A corrected API reference**

The published API reference now matches what the API actually does. Request and response shapes, required fields and error responses were wrong or missing in places.

**Consistent tables throughout the Limio app**

Lists and tables across the Limio app now share one frame and spacing. An empty table says so, where previously it showed a header row with nothing beneath it.

**The Team field has been removed from user settings**

The Team field and its dropdowns are gone from the user screens. Nothing in Limio read it — access has always been decided by a user's role.

**Strengthened platform security**

Following our latest penetration test, Limio applies stricter ownership checks to account data, and several third-party components have been updated.

#### Bug Fixes

**A £0 order paid by card now completes**

A fully discounted or compensation offer can now be bought through the standard card checkout. Previously the order failed during processing, no subscription was created, and the customer saw a failed checkout.

**External prices now appear in the cart total**

Items with an externally set price are now included in the cart total and on preview invoices. Previously they were left out of both, so the total a customer saw was too low.

**Cooling-off cancellations work for Direct Debit orders**

Cancelling within the cooling-off period now works for a Direct Debit order with nothing yet to refund. Previously the refund step failed and blocked the cancellation.

**A refused basket can be recovered**

Where a basket is refused, trying again now works. Previously the next page load picked the same refused basket back up, so the customer met the same failure.

A dropped connection no longer discards a basket either, so a customer on a poor connection does not lose one they spent time filling.

**An abandoned order no longer blocks a subscription claim**

A customer who previously abandoned an order can now claim their subscription. Previously the leftover order counted as a second subscription and the claim was refused.

**User details save without a Team**

Editing a user in the Limio app now saves without selecting a Team. Previously the save was rejected for any user who had never been given one.

*Please remember to perform a hard refresh in your browser after upgrading your environment.*
{% endupdate %}
{% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limio.com/limio-commerce-release-notes/limio-commerce-release-notes/releases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.