API Token
Last updated
Last updated
Integration Name: Display name for the integration Key: Unique identifier for the integration. This should only contain letters and numbers.
Integration parameters allow you to parameterize the integration when defining a connected account. These parameters can be referenced through any of the custom integration inputs by surrounding the text in curly braces {parameterName}.
For example, if you want to parameterize a query parameter on the Authorization Endpoint, the url would look like the following:
Then, the query parameter would then be accessible when you create the connected account.
Another example for using integration parameters would be for connections where you have different servers for access token endpoints. You could customize the URL string with the following : {serverName}
This could then be used to create multiple connected accounts with the same authentication patterns when using multiple profiles (i.e. DEV, QA, PROD)
Token Parameter Type (required) : Where to pass the token with the HTTP Request data operation. Select between URL Parameter and Header.
Token Parameter Name (required): The name to define how the token is specified (i.e. Authorization).
Token Parameter Value Template (required): The format of how to pass the token, once retrieved. The token is denoted as {token} in the input. For example, if the token is passed in the header of the request, with the format Authorization: Bearer <token>, then this field would look like:
Request parameters are included with every HTTP request that is used in an HTTP Request in Connections Builder.
