Etsy is an eCommerce Platform. When you provision an instance, your app will have access to the different functionality offered by the Etsy platform.
Query Parameters:
key - etsy
apiKey– - KEYSTRING
apiSecret – SHARED SECRET
callbackUrl – the URL that you supplied to the provider when registering your app
Description: The result of this API invocation returns a requestToken and Secret from the endpoint, which are used to retrieve the redirect URL. The requestToken is used in the GET /elements/{keyOrId}/oauth/url call.
Each of the OAuth API calls will be shown below.
Example cURL Command:
curl -X GET
-H 'Content-Type: application/json'
'https://api.cloud-elements.com:443/elements/api-v2/elements/etsy/oauth/token?apiKey=insert_fake_api_key&apiSecret=insert_fake_api_secret&callbackUrl=https%3A%2F%2Ffakecallbackurl.com%2Fauth'
Response:
{
"token": "qyprd1Twij60MH06lKGUZTJwx7tbzpPQx6aZnvKe0xI7",
"secret": "9tsIbAHUevF"
}
Etsy expects a token and secret. These are contained in the response to the initial GET request. Please make note of the token and secret. The token is needed in the GET /elements/{keyOrId}/oauth/url call which is shown below.
HTTP Header: None HTTP Verb: GET Request URL: /elements/{keyOrId}/oauth/url Request Body: None Query Parameters:
Description: The result of this API invocation is an OAuth redirect URL from the endpoint. Your application should now redirect to this URL, which in turn will present the OAuth authentication and authorization page to the user. When the provided callback URL is executed, a code value will be returned, which is required for the Create Instance API.
Example cURL Command:
curl -X GET
-H 'Content-Type: application/json'
'https://api.cloud-elements.com/elements/api-v2/elements/etsy/oauth/url?apiKey=insert_fake_api_key&apiSecret=insert_fake_api_secret&callbackUrl=https%3A%2F%2Ffakecallbackurl.com%2Fauth&requestToken=insert_fake_request_token&state=etsy'
Response:
{
"oauthUrl": "https://www.etsy.com/oauth/signin?oauth_token=insert_fake_request_token&oauth_callback=https%3A%2F%2Ffakecallbackurl.com%2Fauth%3Fstate%3Detsy",
"element": "etsy"
}
Your application should now redirect to the oauthUrl returned in step 2, which in turn will present the OAuth authentication and authorization page to the user.
HANDLE CALLBACK FROM THE ENDPOINT
After the user successfully authenticates, the provided callback URL is executed. The callback URL will contain several parameters, listed below. These additional parameters, along with the original API key and API secret are required for the Create Instance API.
The parameters that you will need to parse from the callback URL are listed below, along with an example of what the callback URL should look like. oauth_token oauth_verifier
To provision your Etsy Element, use the /instances API.
Below is an example of the provisioning API call.
Description: An Element token is returned upon successful execution of this API. This token needs to be retained by the application for all subsequent requests involving this element 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 Cloud Elements Etsy is “etsy”. This will need to be entered in the “key” field below depending on which Element you wish to instantiate.
{
"element": {
"key": "etsy"
},
"providerData": {
"secret": "<From Step 1>",
"oauth_token": "<From Return URL>",
"oauth_verifier": "<From Return URL>"
},
"configuration": {
"shop.id": "<INSERT_SHOP_NAME>",
"oauth.api.key": "<INSERT_KEYSTRING>",
"oauth.api.secret": "<INSERT_SHARED_SECRET>",
"oauth.request.url": "https://openapi.etsy.com/v2/oauth/request_token",
"oauth.callback.url": "<INSERT_CALLBACK_URL>"
},
"tags": [
"<INSERT_TAGS>"
],
"name": "<INSERT_INSTANCE_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.cloud-elements.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": "eOzXnENuA9k2Br6t4ECaDj+Fh5HTdFY=",
"element": {
"id": 91,
"name": "etsy",
"key": "etsy",
"description": "The leading e-commerce platform for web professionals.",
"image": "https://pbs.twimg.com/profile_images/378800000573228864/b159f3cb6e857b063ad7f0cd665b10d0_400x400.png",
"active": true,
"deleted": false,
"typeOauth": false,
"trialAccount": false,
"transformationsEnabled": true,
"authentication": {
"type": "oauth2"
},
"hub": "ecommerce"
},
"provisionInteractions": [],
"valid": true,
"disabled": false,
"maxCacheSize": 0,
"cacheTimeToLive": 0,
"eventsEnabled": false,
"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.
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 element is being instantiated. However, some configuration properties are common to all elements and available to be configured for all elements. 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 element instance. This property defaults to false.event.vendor.type: When event.notification.enabled property is set to true, this property determines the mechanism for Cloud Elements to use to receive or fetch changed events from the service endpoint. The supported values are webhook and polling. Most elements support one mechanism or the other, but some elements, e.g., 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 element 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 element 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 Cloud Element 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.