Act-On Authenticate a Connector

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

Authenticate Through the UI

Use the UI to authenticate with Act-On and create a connector instance. Because you authenticate with Act-On via OAuth 2.0, all you need to do is add a name for the instance. After you create the instance, you'll log in to Act-On to authorize Axway AMPLIFY to access your account. For more information about authenticating a connector instance, see Authenticate a Connector Instance (UI)

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

Authenticate Through API

Act-On is a Marketing Platform. When you provision an instance, your app will have access to the different functionality offered by the Act-On platform.

Step 1. Get Connectors OAuth Information

  • HTTP Header: None
  • HTTP Verb: GET
  • Request URL: /elements/{keyOrId}/oauth/url
  • Request Body: None
  • Query Parameters:

  • apiKey - the key obtained from registering your app with the provider

  • apiSecret – the secret obtained from registering your app with the provider

  • callbackUrl – the URL that you supplied to the provider when registering your app, state – any custom value that you want to be passed to the callback handler listening at the provided callback URL.


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' \


  "element": "acton",
  "oauthUrl": ""

Handle Callback from the Endpoint: Upon successful authentication and authorization by the user, the endpoint will redirect to the callback URL you provided when you set up your application with the endpoint, in our example, The endpoint will also provide two query string parameters: “state” and “code”. The value for the “state” parameter will be the name of the endpoint; for example, acton in our example, and the value for the “code” parameter is the code required by Axway AMPLIFY to retrieve the OAuth access and refresh tokens from the endpoint. If the user denies authentication and authorization, there will be a query string parameter called “error” instead of the “code” parameter. In this case, your application can handle the error gracefully.

Step 2. Create an Instance

To provision your Act-On 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


A connector token is returned upon the 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:


This instance.json file must be included with your instance request. Please fill your information to provision. The “key” into Act-On is “sfdc”. This will need to be entered in the “key” field below, depending on which connector you wish to instantiate.

  "element": {
    "key": "acton"
  "providerData": {
    "code": "<Code_On_The_Return_URL>"
  "configuration": {
    "oauth.callback.url": "",
    "oauth.api.key": "<Insert_Client_ID>",
    "oauth.api.secret": "<Insert_Client_Secret>"
  "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

If a user does not specify a required config entry, an error will notify them of which entries they are missing.

Below is a successful JSON response:

    "id": 123,
    "name": "test",
    "token": "3sU/S/kZD36BaABPS7EAuSGHF+1wsthT+mvoukiE",
    "element": {
        "id": 39,
        "name": "",
        "key": "acton",
        "description": "The allows you to deliver revolutionary Marketing automation functionality, such as account and contact creation, from anywhere, anytime, on any device.",
        "active": true,
        "deleted": false,
        "typeOauth": true,
        "trialAccount": false,
        "configDescription": "If you do not have a account, you can create one at <a href="" target="_blank"> Signup</a>",
        "signupURL": ""
    "provisionInteractions": [],
    "valid": true,
    "eventsEnabled": true,
    "disabled": false,
    "maxCacheSize": 0,
    "cacheTimeToLive": 0,
    "cachingEnabled": false

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 the 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 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; in other words, its 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.

Related Links