Connector Builder- Information Tab

When you create a connector using Connector Builder, the first step is to provide some basic information about the connector. To build the connector, we need to know how you identify the connector, the hub it belongs to, the type of service to connect to, the authentication type of the connector, and information about the API provider.

Connector Information Setup

To complete the connector information:

  1. Name and describe the connector:

    • Connector Name — The name appears on the connector card and should identify the API provider associated with it.
    • Connector Key — Generated from the Connector Name by default, but you can enter any text. API requests use the connector key, so make sure that it identifies the connector.
    • Description — The description helps to clarify the purpose of the connector. The description appears in the response when you authenticate an instance of the connector.
  2. Choose the hub associated with the new connector —or enter a name for a new hub, and then click Create Option {Hub Name}. Make sure that you choose an accurate hub because you can leverage existing hub resources when you add resources to the connector.
  3. Select the API type used by the API provider. You can find the API type in an Overview or Introduction section of the API documentation.
    • REST API — Select if the API is a REST or RESTful API.
    • SOAP API — Select if the API is a SOAP API.
    • Database — Select of the API is for a database application.
  4. Select the type of authentication needed to connect with the API provider. You can typically find this information in an Authorization or Authentication section of the provider's API documentation.


    Your authentication selection affects the configuration values that you will need to complete when you configure the connector.

  5. Add reference information that you will need while building the connector:

    • Documentation URL — Add a link to the API documentation. You will reference this throughout the connector building process.
    • Vendor API Version — Add a version number here if available, so you always know what version of the API for which the connector was built.
  6. Optionally upload an image to associate with the connector.


    Axway AMPLIFY accepts .jpg, jpeg, .png, and .gif image files.

  7. Click Save & Next.

Continue to the next step, Connector Builder Properties.

Connector Information Parameters

Parameter Description Required
Connector Name The name of the connector. This helps form the default Connector Key. Y
Connector Key A unique identifier for the connector. The Connector Key must be alphanumeric and lower case. The default comes from the Connector Name. The Connector Key is used in /elements endpoints that require {keyOrId}. Y
Hub The hub to which the connector belongs. A collection of connectors where the APIs of those connectors have been normalized to a standard defined by the Hub. N
Service type Identifies the kind of connector that you are building, either REST, SOAP, or database Y
  SOAP/XML — for SOAP APIs  
  Database — for APIs provided by database applications.  
Authentication Type The authorization type used by the API provider. Find this in the API docs under Authorization or Authentication. Y
  Basic — Integrations authenticate with the API provider via user name and password.  
  OAuth 1.0 — Integrations authenticate with the API provider via OAuth 1.0. OAuth 1.0 does not require users to expose their credentials. OAuth 1.0 is a three-step authentication process. The OAuth 1.0 protocol involves signing the payload on every request and thus is used by many financial services. While OAuth 1.0 provides a standard way to authenticate, many cloud services implement it in unique ways. Axway AMPLIFY implements OAuth 1.0 to the specification defined at OAuth 1.0 specification.  
  OAuth 2.0 — The OAuth 2.0 protocol lets external applications — your application or Axway AMPLIFY — request authorization to access and update a user's data without asking users for sensitive user names and passwords. OAuth 2.0 is not strongly specified, and many API providers implement it differently, so make sure that you read the API provider's documentation. Axway AMPLIFY implements OAuth 2.0 to the specification defined at OAuth 2.0 specification.  
  AWS V2 — Amazon Web Services Signature Version 2 for older AWS resources.  
  AWS V4 — Amazon Web Services Signature Version 4 for the latest AWS resources.  
  Custom — For user-defined authentications, such as passing an API key in the header or login requests made during authentication where tokens are passed. Because OAuth 1.0 and 2.0 are implemented differently at different cloud services, you might need to choose Custom.  
Documentation URL The URL to the API provider's API documentation. N
Vendor API version Some vendors offer multiple versions of their API. Enter the version that you are building the connector for here. N
Base URL Endpoints are appended to the base URL. So, with an endpoint like, the base URL is Many API providers explicitly state the base URL, but in some cases, you can find it by looking at examples in the API documentation. Y
Pagination Max The maximum number of records the API provider returns in a response. Y
Pagination Type How the API provider provides pages of data. Find the pagination types in a Pagination section of the API documentation. Y
  The page starts with n — Pagination begins with either 1 or 0.  
  Offset — A numeric offset identifies the first page.  
  Cursor — A unique key connector identifies the first-page entry.  

Related Links