---
schema_version: "1"
id: a32b7916d4ce1aa2b8d84c601239297446e381512f87ee5edc0dbdd3d4efa660
title: Enable Loyalty Management Restaurant POS API Powered by MuleSoft Integration
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/industries-integrations/loyalty/guides/enable-mulesoft-restro-pos.md
canonical_url: https://developer.salesforce.com/docs/industries/loyalty/guide/enable-mulesoft-restro-pos.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: b25fffebe27fc78190919caac3bc497f6eb143def560e54a0e25be25e85ee02b
products:
  - Loyalty Management Integrations API
  - Industries Integrations
---
# Enable Loyalty Management Restaurant POS API Powered by MuleSoft Integration

After you set up the unlocked package, enable the Loyalty Management Restaurant POS API Powered by MuleSoft. The integration deploys the app to the AnyPoint Platform, applies policies, and creates named credentials, which are editable.

1. From Setup, in the Quick Find box, enter `Integrations`, and then select **MuleSoft Direct**.
2. From the list of available integrations, select the integration that you want to enable, and then click **Enable**.
3. Select the business group that you want to enable the integration for.
4. Select the environment where you want to enable the integration.
5. Select a deployment target where you want to deploy the integration.
6. Enter an app name that is unique for your MuleSoft instance.
7. Click **Next**.
8. To connect to an external system, select **None** as the Authorization Protocol.
9. Click **Add Additional Parameters**, and enter these keys and values:
   | Keys | Values |
   | ----------- | ----------- |
   | anypoint.mq.client_id | The client ID to connect to the queue. |
   | anypoint.mq.client_secret | The client secret to connect to the queue.|
   | anypoint.mq.orders.destination | The name of the queue that you created to store the incoming order requests from the restaurant’s POS application.|
   | anypoint.mq.url| The URL of the Anypoint MQ. For example, [https://mq-us-east-1.anypoint.mulesoft.com/api/v1]. The URL format is: [https://mq-[region].anypoint.mulesoft.com/api/v1]. For regions, see: <https://docs.mulesoft.com/mq/mq-faq#regions>.|
   | grant_type | The grant_type of the connected app. This parameter is optional, and the default value is `client_credentials`.|
   | loyalty.member-currency-name| The ISO code of the currency, if the loyalty program is set up with multiple currencies. This is an optional parameter, which is used during voucher redemption.|
   | loyalty.program-name | The name of the loyalty program.|
   |loyalty.shopify.enabled | Enable or disable the Retail POS APIs endpoints. The default value is true. This parameter is optional.|
   | loyalty.user-message | An optional message that describes the Loyalty Inquire request response. |
   | mule.authCode | Mandatory parameters. The Restaurants API endpoints use a static API key for authentication, to enable access to set this value with a value that would be passed as an authorization header. The request is validated against this value.|
   | salesforce.connected_app.client_id | The client ID of the connected app.|
   | salesforce.connected_app.client_secret | The client secret of the connected app.|
   | salesforce.domain | The domain address of your Salesforce org, excluding `https://>`.|
   | salesforce.namespace| The namespace of the deployed package. The default value is POSIntegration.|
   | queue.accrue.name| The name of the queue that stores the accrue for processing. The default value is `loyalty-accrue-queue`.|

**note:** If you want to hide the value of the parameter on the Anypoint Runtime Manager for security reasons, click the **Hide value on
Anypoint Platform** checkbox. You can hide the parameter value only if you’re deploying the integration to CloudHub 2.0.

10. Click **Proceed**.

**Next**
[Disable the ClientId Enforcement Policy](https://developer.salesforce.com/docs/industries/loyalty/guide/disable-clientid-enf-policy.md)
