Commercetools Connector Configuration

The OAuth2 scope(s) used in requests to the commercetools.

This value is a combination of multiple scopes for various features of the commercetools. The commercetools endpoints may provide various scopes to grants API access within a project. See commercetools HTTP API and related API documentation for detail.

If a list of field names is specified as a comma separated string, then extra custom fields are extracted from the product item in the JSON response and included in the the GraphQL response like the following example:

{
  "data": {
    "findItemsByKeyword": {
      //...
      "items": [
        {
          //...
          "customAttrs": [
            { "name": "hasStagedChanges", "values": [ "false" ] },
            { "name": "lastModifiedAt", "values": [ "2018-01-29T20:20:50.328Z" ] },
            { "name": "slug", "values": [ "{\"en\":\"thanksgiving-activity-book-1476365028138\"}" ] }
          ]
        },
        //...
      ]
    }
  }
}

The URL of the trusted email service.

In the case of customer's password reset, commercetools does not automatically send the password reset email. However, the brX GraphQL Service is able to retrieve to customer reset token and send it  - together with the customer details - to the trusted email service. 

The email service implementation (e.g. REST service) must be able to process the request triggered by the brX GraphQL Service. The request body has the following structure:

{
  "customer": {
    "email": "...",
    "firstName": "...",
    "middleName": "...",
    "lastName": "...",
    "title": "...",
    "salutation": "...",
    "locale": "..."
  },
  "token": "XXX"
}