--- title: "Connected Apps" slug: "connected-apps" tags: ["Admin", "Blue Yonder", "Border Connect", "Comdata Fuel Cards", "EDI REST API", "PubSub", "Trimble"] updated: 2026-08-03T13:35:30Z published: 2026-08-03T13:35:30Z canonical: "documents.revenova.com/connected-apps" deprecated: true --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # Connected Apps > **Deprecated.** The Salesforce Spring ’26 release removes the ability to create new Connected Apps by default. Instead, create new [External Client Apps](/v1/docs/external-client-apps) for integration partners, as this is the recommended and more secure way to connect applications with Revenova. For existing Connected Apps in your org, [migrate eligible ones to External Client Apps](https://help.salesforce.com/s/articleView?id=xcloud.migrate_connected_app_to_external_client_app.htm&type=5) for a secure, automated process. If you need to create a new Connected App, contact Salesforce Support to have the ability reinstated. Several Revenova-supported integrations require a Salesforce Connected App to communicate data between the TMS and the integration partner. Create a Connected App for each third-party integration the customer uses. Run the Connected App as the API User. For more information, see Salesforce documentation for [Connected Apps](https://help.salesforce.com/s/articleView?id=xcloud.connected_app_overview.htm&type=5). ## **Integration Partners** The following partner integrations require a Connected App to send and receive information with a customer org. The steps below show how to create a new Connected App or to complete the setup of a packaged Connected App. Some Connected Apps are packaged in the TMS. Additional setup is required for these existing Connected Apps before they may be used. See the [Verify Connected App](/v1/docs/connected-apps-1#verify-connected-app) section below to finish the setup of packaged Connected Apps. - [Blue Yonder](/v1/docs/summary) - [Border Connect](/v1/docs/border-connect) - [Comdata Fuel Cards](/v1/docs/comdata-fuel-cards) - [Highway Carrier Onboarding](/v1/docs/highway-carrier-onboarding-and-monitoring) - [Pub/Sub Accounting](/v1/docs/pubsub-api-accounting-integration) - [Trimble Maps](/v1/docs/trimble-maps) - [RevenovaWebService](/v1/docs/revenova-tms-web-services-guide#revenovawebservice) See additional information on Salesforce API integration [here](https://help.salesforce.com/s/articleView?id=platform.integration_user.htm&type=5). ### **EDI Partner VANs** The Revenova TMS uses REST endpoints to allow for EDI Partner VANs to send EDI transactions to each customer org. To successfully receive these EDI transactions, **each** Partner VAN must have a Connected App created. Follow the instructions below to create a Connected App for **each** VAN. The TMS supports transactions from Kleinschmidt, Cleo, and a single Custom EDI/other partner VAN. Multiple connections are supported for a single org, but only with a **single** Custom EDI partner. See additional EDI information [here](/v1/docs/edi-management-1). - Cleo - Custom EDI - Kleinschmidt The time zone used by the REST API process is the automated process user's time zone. Time zones are first determined based on the time zone specified in the EDI Transaction. When a time zone is not specified or a location update does not contain a time zone, the time zone of the API User/context user set for the VAN on the Load is used to determine the time zone. ## **Best Practices** - Create a Connected App for each required integration used in the customer org. - Create 1 API User and apply the appropriate packaged Permission Set(s) to that user for each required integration. - The [RevenovaWebService](/v1/docs/revenova-tms-web-services-guide#revenovawebservice) does not include a packaged Permission Set. Create or add a permission set with the appropriate permissions as needed. - The API User requires a TMS and Salesforce integration license. ## **API User** Create an API User or Users to run the Connected Apps for a customer org. Add only the necessary permission sets for the integrations a customer is using. > [!WARNING] > **Note:** Each EDI Partner VAN/Connected App requires a unique API User/Context User to properly sort and process EDI Transactions. Create an API User for each Partner VAN integration. ### **Create the API User** 1. Navigate to **Setup → Users**, click **New User** and create a User with the following values. 1. First Name: *API* 2. Last Name: *User* 3. Email: Set to the System Administrator’s email address. 4. Username: Automatically generated. Change if necessary. 5. User License: *Salesforce Integration* 6. Profile: *Minimum Access - API Only Integrations* 7. Active: *Checked*. 2. Set the remaining required User fields as desired. 3. Click **Save**. 4. Navigate to the list of Users and select the API User. 5. From the Permission Set Assignments section, click **Edit Assignments**. 6. Select each permission set for all integrations the customer uses. Click the **Add** button to add the permission set(s) to the *Enabled Permission Sets* column. The following permission sets are packaged in the TMS and intended for use with the associated integration in parentheses. 1. Border Connect API User (Border Connect) 2. Comdata API User (Comdata Fuel Cards) 3. Highway API User (Highway Carrier Onboarding) 4. TMS Accounting Integration (Pub/Sub Accounting) 5. TMS Blue Yonder API (Blue Yonder) 6. TMS EDI API (Cleo, Custom EDI, and Kleinschmidt REST EDI integrations) 7. Trimble API User (Trimble Maps) 7. Click **Save**. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - Run As User - 5.jpg) ## **Set up Connected App Access** Connected Apps allow third-party applications to integrate with Salesforce by using APIs with standard protocols to authenticate and authorize these applications. Create a Connected App for each partner integration that requires one. While the API User is used by multiple Connected Apps, a single Connected App does not work for multiple partner integrations. See Salesforce Connected App information [here](https://help.salesforce.com/s/articleView?id=xcloud.connected_app_overview.htm&type=5). Create all required Connected Apps by following the steps below. > [!NOTE] > **Note**: The Blue Yonder integration has additional steps outlined [below](/v1/docs/connected-apps-1#blue-yonder-additional-setup). Complete the additional Blue Yonder setup steps before navigating from the Connected App setup. ### **Step 1: Allow Authorization Code and Credentials Flows** 1. From **Setup** → search and select **OAuth and OpenID Connect Settings**. 2. Set **Allow Authorization Code and Credentials Flows** to *On*. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - OAuth Settings - 1.jpg) ### **Step 2: Enable App Creation** 1. Navigate to **Setup** and search for **External Client Apps** and select the **Settings** link. 2. From the *Connected Apps* section, choose **On** *for Allow creation of connected apps*. 1. Click the **Enable** button on the modal to create Connected Apps. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - OAuth Settings - 2.jpg) ### **Step 3: Create New Connected App** Create a Connected app by following the steps below. (Border Connect is shown as an example.) 1. Click the **New Connected App** button. 2. Enter the following information. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - Create App - 1.jpg) 1. Connected App Name: Border Connect. 2. Contact Email: System Admin's email. 3. Enabled OAuth Setting: *Checked*. 4. Callback URL: https://login.salesforce.com/. 5. Selected OAuth Scopes: Add **Manage user data via APIs (api)**. 6. Enable Client Credentials Flow: *Checked*. 3. Click **Save**. ### **Step 4: Access the Consumer Key and Consumer Secret** Several integrations require the Consumer Key and Consumer Secret to complete setup. Typically, the Consumer Key and Secret must be sent to Revenova along with the 18-character Organization ID to complete setup. See the specific integration documentation to determine if this information is required before completing the following steps. Instructions to find the 18-character Organization ID are provided below. 1. Navigate to **Setup** → **App Manager**. 2. Find the row for the integration and click the drop-down and select **View**. (Border Connect is shown as an example.)![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Border Connect - Connected App - 2(1).jpg) 3. Click the **Manage Consumer Details** button. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Border%20Connect%20-%20Connected%20App%20-%203.jpg) 4. Salesforce sends a verification email to the system admin's email address. Enter this code in the **Verify Your Identity** page. 5. Copy the **Consumer Key** and **Consumer Secret** for later use. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected%20Apps%20-%20Consumer%20Key-Secret%20-%201.jpg) **Copy 18-Character Organization ID** 1. From the **Setup** drop-down, choose *Developer Console*. 2. Select the *Query Editor* tab. 3. Enter *SELECT Id from Organization* into the field. 4. Click the **Execute** button. 5. Copy the 18-character Organization ID for later use. ### **Step 5: Set Client Credentials Flow Run As user** 1. Navigate to **Setup** → **App Manager**. 2. Find the row for the integration and click the arrow and select **View**. (Border Connect is shown as an example.) ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - Run As User - 1.jpg) 3. From the connected app, click the **Manage** button at the top of the page. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - Run As User - 2.jpg) 4. Click the **Edit Policies** button. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - Run As User - 3.jpg) 5. In the *Client Credentials Flow* section, use the search button to set the **Run As** user to the *API User* created [above](/v1/docs/connected-apps-1#create-the-api-user). ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - Run As User - 4.jpg) 6. Click **Save**. ### **Blue Yonder Additional Setup** **Add Trusted IP Range for OAuth Web Server Flow** 1. If you navigated away from the newly created App, go to **Setup → App Manager**. 2. Find the Blue Yonder from the list of apps. 3. From the caret, click **View** on the *Blue Yonder* app. 4. Go to the *Trusted IP Range for OAuth Web Server Flow* section and click **New**. 5. Add the following IP ranges (*repeat step 4 for each IP range*). 1. Start IP Address, End IP Address: 20.122.40.48. 2. Start IP Address, End IP Address: 52.177.14.131. 3. Start IP Address, End IP Address: 52.247.78.106. 6. Click **Save** for each IP range. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - Blue Yonder IP Range - 1.jpg) **Domain URL** The following endpoints are sent to Blue Yonder for setup within their system. Each org must send these endpoints to Blue Yonder to complete setup. Note that “{domain}” can be found under **Setup → My Domain → Current My Domain URL**. 1. OAuth authorization endpoint: https://{domain}/services/oauth2/token 2. Quote request endpoint: https://{domain}/services/apexrest/rtms/blueyonderloadservice 3. Tender request endpoint: https://{domain}/services/apexrest/rtms/blueyondertenderservice ### **Pub/Sub Accounting Additional Setup** The accounting partner requires the domain for setup within their system. Each org must send its domain to the accounting partner to complete the setup. Note that “{domain}” can be found under **Setup → My Domain → Current My Domain URL**. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/My%20Domain%20Settings.jpg) ## **Verify Connected App** Some integrations are included in the TMS package with pre-built Connected Apps (Border Connect, Highway, Trimble Maps, and others). For these existing Connected Apps, complete the following steps required for initial setup. (Border Connect is shown below as an example.) Confirm that Connected Apps are enabled. 1. Navigate to **Setup** → **External Client Apps** and select the **Settings** link. 2. From the *Connected Apps* section, choose **On** *for Allow creation of connected apps*. 1. Click the **On** button to enable the creation of Connected Apps. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected%20Apps%20-%20OAuth%20Settings%20-%202(1).jpg) 1. Navigate to **Setup** → **App Manager** and find the integration Connected App (*Border Connect API Connect*.) 2. Find the integration from the list and choose the caret, select *Edit*. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - Verify App - 1(1).jpg) 3. *Check* the **Enable Client Credentials Flow** box. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - Verify App - 2.jpg) 4. Click **Save**. 5. Return to **Setup** → **App Manager**. 6. Find the Connected App from the list and choose the caret, select *Manage*. (*Border Connect API Connect*.) 7. Choose the **Edit Policies** button. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - Verify App - 3.jpg) 8. In the *Client Credentials Flow* section, find the **Run As** field. 9. Click the **Run As Lookup** button. 10. Select the *API User* created above. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/Connected Apps - Verify App - 4.jpg) 11. Click **Save**.