You can authenticate with Volusion to create your own instance of the Volusion connector through the UI or through APIs. Once authenticated, you can use the connector instance to access the different functionality offered by the Volusion platform.

Authenticate Through the UI

Use the UI to authenticate with Volusion and create a connector instance. You will need the credentials you identified in Volusion API Provider Setup.

After successfully authenticating, we give you several options for next steps. Make requests using the API docs associated with the instance, map the instance to a common resource, or use it in a formula template.

Authenticate Through API

Below is an example of how to create an instance with the Volusion connector. The create-instance file contains the data needed to create the connector Instance. In the case of Volusion, you will need to copy the encrypted password from the URL and insert it into the the JSON file. You will also need your Volusion store URL – this is located at the beginning section of the URL copied in the previous step. Lastly, you will need your Email Login. This is obtained when running any type of order. To view how get this URL, please see Volusion Endpoint Setup. An example of the URL can be seen below:

http://otnqw.rakrt.servertrust.com/net/WebService.aspx?Login=volusion@acmedata.com&EncryptedPassword=64F3C0572DB54C7200391418E79AC678214B366FBD4EName=GenericOrders

The beginning portion of the URL is your store URL – http://otnqw.rakrt.servertrust.com. Then the login email – volusion@acmedata.com, and finally the EncryptedPassword – 64F3C0572DB54C7200391418E79AC678214B366FBD4E

Step 1. Create an Instance

To provision your Volusion connector, use the /instances API.

Below is an example of the provisioning API call.

• HTTP Headers: Authorization- User , Organization
• HTTP Verb: POST
• Request URL: /instances
• Request Body: Required – see below
• Query Parameters: none

Description: token is returned upon successful execution of this API. This token needs to be retained by the application for all subsequent requests involving this connector instance.

A sample request illustrating the /instances API is shown below.

HTTP Headers:

Authorization: User <INSERT_USER_SECRET>, Organization <INSERT_ORGANIZATION_SECRET>

This instance.json file must be included with your instance request. Please fill your information to provision. The “key” into SAP Open Connectors Volusion is “volusion”. This will need to be entered in the “key” field below depending on which connector you wish to instantiate.

{
  "element": {
    "key": "volusion"
  },
  "configuration": {
    "volusion.store.url": "<INSERT_VOLUSION_STORE_URL>",
    "volusion.login.email": "<INSERT_VOLUSION_LOGIN_EMAIL>",
    "volusion.encrypted.password": "<INSERT_ECRYPTED_PASSWORD>"
  },
  "name": "<INSERT_NAME>"
}

Here is an example cURL command to create an instance using /instances API.

Example Request:

curl -X POST
-H 'Authorization: User <INSERT_USER_SECRET>, Organization <INSERT_ORGANIZATION_SECRET>'
-H 'Content-Type: application/json'
-d @instance.json
'https://api.openconnectors.us2.ext.hana.ondemand.com/elements/api-v2/instances'

If the user does not specify a required config entry, an error will result notifying her of which entries she is missing.

Below is a successful JSON response:

{
    "id": 1234,
    "name": "Test",
    "token": "3sU/S/kZD36BaABPS7EAuSGHF+1wstvoukiEHkI=",
    "element": {
        "id": 14,
        "name": "Volusion",
        "key": "volusion",
        "description": "Volusion is everything you need to sell anywhere.",
        "active": true,
        "deleted": false,
        "typeOauth": false,
        "trialAccount": false,
"existingAccountDescription": "Give your application access to your existing Volusion account.  Enter your credentials and details for your Volusion Account",
        "configDescription": "If you do not have a Volusion account, you can create one at <a href="http://www.volusion.com" target="_blank">Volusion Signup</a>",
        "signupURL": "http://www.volusion.com"
    },
    "provisionInteractions": [],
    "valid": true,
    "disabled": false,
    "maxCacheSize": 0,
    "cacheTimeToLive": 0,
    "cachingEnabled": false
}

Note: Make sure you have straight quotes in your JSON files and cURL commands. Please use plain text formatting in your code. Make sure you do not have spaces after the in the cURL command.

Instance Configuration

The content in the configuration section or nested object in the body posted to the POST /instances or PUT /instances/{id} APIs varies depending on which connector is being instantiated. However, some configuration properties are common to all connectors and available to be configured for all connectors. These properties are -

• event.notification.enabled: This property is a boolean property, and determines if event reception (via webhook or polling) is enabled for the connector instance. This property defaults to false.
• event.vendor.type: When event.notification.enabled property is set to true, this property determines the mechanism to use to receive or fetch changed events from the service endpoint. The supported values are webhook and polling. Most connectors support one mechanism or the other, but some like Salesforce.com support both mechanisms. This property is optional.
• event.notification.type: This property can be used to determine how an event notification should be sent to the consumer of the connector instance, in most cases your application. Currently, webhook is the only supported value for this property. This means that when an event is received by the connector instance, it will get forwarded to the provided event.notification.callback.url via a webhook to you. This property is optional.
• event.notification.callback.url: As mentioned above, the value of this property is an http or https URL to which we will post the event for consumption by your application. This property is optional.
• filter.response.nulls: This property defaults to true, i.e., it's boolean property, and determines if null values in the response JSON should or should not be filtered from the response returned to the consuming application. By default, all null values are filtered from the response before sending the response to the consuming application.