> For the complete documentation index, see [llms.txt](https://docs.developers.symphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.developers.symphony.com/ext-apps/overview-of-extension-api/extension-api-services/commerce-service.md).

# Commerce Service

Apps can offer premium functionality through licensed subscriptions. Use the `commerce` service to identify the products (premium versions) to which a user is subscribed:

```javascript
// To use the commerce service, you must subscribe to it from your application
var commerceService = SYMPHONY.services.subscribe("commerce");
```

## getProducts()

Returns the list of products to which the user is subscribed for your app:

```javascript
function getProducts(serviceName)
```

<table data-header-hidden><thead><tr><th width="151.33333333333331">Parameters</th><th width="92">Type</th><th>Description</th></tr></thead><tbody><tr><td>Parameters</td><td>Type</td><td>Description</td></tr><tr><td>serviceName (optional)</td><td>String</td><td>The name of a local application-implemented service. If passed, the <code>productUpdate</code> event will be fired on that service if the user's product subscriptions change.</td></tr></tbody></table>

This method returns a promise that will be fulfilled with the array of products the user is subscribed to for your app. For each product, the following is returned:

```javascript
{ 
  name: "<name>", 
  type: "premium", 
  sku: "<sku>", 
  subscribed: true/false
}
```

"Premium" is the term used for paid subscription products, while "Standard" represents a freemium app. The name and SKU will be values specified by the application developer when implementing a premium version of their app.

```javascript
commerceService.getProducts('hello:controller').then(function(products) {
  console.log(products);
});
```

## productUpdate

This event is fired when the user's product subscriptions are changed.

Use the [listen](/ext-apps/overview-of-extension-api/extension-api-services/service-interface.md#listen) method on the service specified in `getProducts()` to subscribe to this event and specify a callback that will be executed when the event is fired. The callback should change the contents/features of your application to match the user's updated product subscriptions.


---

# 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.developers.symphony.com/ext-apps/overview-of-extension-api/extension-api-services/commerce-service.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.