# Prerequisites and considerations In order to successfully integrate your Conversation API project and apps with your Salesforce account, you must ensure that the following prerequisites are met. Note: Each Conversation API project (and corresponding project ID) can be associated with, at most, one Omnichannel connector solution/installation link and one Salesforce Marketing Cloud ID. If you plan to set up solutions for sub-organizations or (in the case of resellers) customers, they **cannot** use your parent project ID or Salesforce Marketing Cloud ID. They must provide their own. ## Salesforce prerequisites In order to successfully connect a Conversation API project to a Salesforce account, and use the Omnichannel connector with Marketing Cloud, you must have: - A license for the Salesforce Marketing Cloud service. - A corporate or enterprise edition of Marketing Cloud. - A Marketing Cloud Org set up. - An account with Marketing Cloud **administrator** privileges readily available. Note that, at this time, the Omnichannel Connector app only supports [Multi-Step journeys](https://help.salesforce.com/s/articleView?id=sf.mc_jb_create_multistep_journey.htm&type=5). ## Conversation API prerequisites In order to successfully connect a Conversation API project to a Salesforce account, and use the Omnichannel connector with Marketing Cloud, you must have: - At least one Conversation API app with at least one configured channel. For information on how to create a Conversation API app and configure a channel on that app, see [this Getting started guide](/docs/conversation/getting-started). - At least one [omni-channel template](https://community.sinch.com/t5/Conversation-API/What-is-an-omni-channel-template/ta-p/9914) or [channel-specific template](https://community.sinch.com/t5/Conversation-API/What-is-a-channel-specific-template/ta-p/9915). Templates can be created using the [API](/docs/conversation/api-reference/template/section/overview/) or the [Message Composer](https://community.sinch.com/t5/Conversation-API/How-do-I-use-Message-Composer-to-create-omni-channel-message/ta-p/9890) functionality of the [Sinch Build Dashboard](https://dashboard.sinch.com/convapi/message-composer). Additionally, you may create new omni-channel templates during the configuration of the [Omni Channel message activity](#using-the-omni-channel-message-activity). Omnichannel Connector support for the explicit channel message functionality of the Conversation API is currently under development. - A [Conversation API webhook](https://community.sinch.com/t5/Conversation-API/How-to-add-a-webhook-to-a-Conversation-API-app/ta-p/8100) that is configured to deliver information to the Omnichannel Connector app. This requires that you set the appropriate values for **Target URL** and **Triggers**. - Set the **Target URL** to `https://sfmc-omni-connector.prod.sinch.com/omnientry/webhook/{{MID}}`, where `{{MID}}` is your current Organization ID. Your `MID` is displayed in your accound drop-down menu at the top of your Salesforce Marketing Cloud page. If your organization has sub-organizations, and your Omnichannel Connector solution(s) is/are associated with those sub-organizations, you must set the `{{MID}}` value to the **MID of the sub-organization** (NOT the MID of the parent organization). - Select the `MESSAGE_DELIVERY`, `MESSAGE_INBOUND`, and `CONTACT_CREATE` webhook triggers from the **Triggers** drop-down list. You can create up to five webhooks per Conversation API app. ## Production requirements In order for your Omnichannel Connector app/solution to be available for production use, you must provide Sinch's provisioning service with the following pieces of information: - The name of your organization. - The Marketing Organization ID of your organization's Marketing Cloud solution. Note that this value may be the same as the Enterprise ID. - The Enterprise ID of your organizations's Marketing Cloud solution. Note that this value may be the same as the Marketing Organization ID. - A contact name and email for the account associated with your Marketing Cloud solution. - Your [Sinch Account ID](https://community.sinch.com/t5/Build-Dashboard/Where-do-I-find-my-Account-ID/ta-p/7175). ## Endpoint considerations The Omnichannel Connector app makes use of several of Sinch's endpoints. These include: | Endpoint | Description | Location | | --- | --- | --- | | `https://sfmc-omni-connector.prod.sinch.com` | Primary URL of the Omnichannel Connector | EU | | `https://eu.conversation.api.sinch.com` | Conversation API (EU Production) | EU | | `https://us.conversation.api.sinch.com` | Conversation API (US Production) | US | | `https://br.conversation.api.sinch.com` | Conversation API (BR Production) | BR | | `https://eu.template.api.sinch.com` | Template Management API (EU Production) | EU | | `https://us.template.api.sinch.com` | Template Management API (US Production) | US | | `https://br.template.api.sinch.com` | Template Management API (BR Production) | BR | | `https://provisioning.api.sinch.com` | Provisioning API | EU | | `https://auth.sinch.com/oauth2/token` | OAuth 2.0 access token provision | US |