Order System API | Salesforce Commerce Cloud Implementation

(0 reviews)


This API allows to create and update the order in Salesforce Commerce Cloud, obtain and delete them.

POST /orders/customer/{customerId}
Endpoint to create a new order for customer in Salesforce Commerce Cloud

GET /orders/customer/{customerId}
Endpoint to obtain orders based on Customer identifier.

GET|PUT|DELETE /orders/{id}
Endpoints to obtaining, updating or deleting of order.

PUT /orders/{id}/status
Endpoint to update order status.

Look at the included self-descriptive RAML definition and the corresponding flows to learn more about the flows.

License Agreement

Note that using this template is subject to the conditions of this License Agreement.
Please review the terms of the license before downloading and using this template. In short, you are allowed to use the template for free with Mule ESB Enterprise Edition, CloudHub, or as a trial in Anypoint Studio.


To make this Anypoint Template run, there are certain preconditions that must be considered. Failing to do so could lead to unexpected behavior of the template.

APIs security considerations

This System API is meant to be deployed to CloudHub and managed using the API Platform Manager.

Run it!

Simple steps to get Retail Salesforce Commerce Cloud Orders System API running.
See below.

Running on premise

In this section we detail the way you should run your Anypoint Template on your computer.

Where to Download Anypoint Studio and Mule ESB

First thing to know if you are a newcomer to Mule is where to get the tools.

  • You can download Anypoint Studio from this Location
  • You can download Mule ESB from this Location

Importing an Anypoint Template into Studio

Mule Studio offers several ways to import a project into the workspace, for instance:

  • Anypoint Studio Project from File System
  • Packaged mule application (.jar)

Running on Studio

Once you have imported you Anypoint Template into Anypoint Studio you need to follow these steps to run it:

  • Locate the properties file mule-<env>.properties, in src/main/mule/resources
  • Complete all the properties required as per the examples in the section Properties to be configured
  • Once that is done, right click on you Anypoint Template project folder
  • Hover you mouse over "Run as"
  • Click on "Mule Application"

Running on Mule ESB stand alone

Complete all properties in one of the property files, for example in mule.prod.properties and run your app with the corresponding environment variable to use it. To follow the example, this will be mule.env=prod.

Running on CloudHub

While creating your application on CloudHub (Or you can do it later as a next step), you need to go to "Manage Application" > "Properties" to set all environment variables detailed in Properties to be configured.
Follow other steps defined here and once your app is all set and started, there is no need to do anything else.

Deploying your Anypoint Template on CloudHub

Anypoint Studio provides you with really easy way to deploy your Template directly to CloudHub, for the specific steps to do so please check this link

Properties to be configured (With examples)

In order to use this Mule Anypoint Template you need to configure properties (Credentials, configurations, etc.) either in properties file or in CloudHub as Environment Variables.

Detailed list with examples:

HTTP configuration

  • http.port 8081

Salesforce Commerce Cloud configuration

  • ocapi.host your.host.commercecloud.salesforce.com
  • ocapi.clientId your_client_id
  • ocapi.clientSecret your_client_secret
  • ocapi.tokenUrl https://account.demandware.com/dwsso/oauth2/access_token
  • ocapi.basePathShopApi /s/RefArch/dw/shop/v19_5
  • ocapi.basePathDataApi /s/-/dw/data/v19_5


Published by
MuleSoft Organization
Published onOct 29, 2019
Asset overview

Asset versions for 2.1.x

Asset versions


Industry Vertical
RetailNo values left to add
SalesforceNo values left to add