Refresh token can be set up by giving the following Refresh token (required): Enter a token that can serve as a refresh expired auth token. You can place this token in the body, headers or URL simply by referencing it with the handlebars placeholder {{connection.http.auth.token.refreshToken}}. Multiple layers of protection, including AES 256 encryption, are in place to… Continue reading Configure token refresh in HTTP connection
Tag: celigo connection
Secret URL Verification type in Celigo Webhook Connection
Celigo’s webhook listener typically supports secret URL verification as a security measure to ensure that webhook endpoints are legitimate and owned by the intended recipient. This process involves including a secret key or token in the URL, and the webhook listener verifies this secret before accepting requests. Here’s a general overview of how you might… Continue reading Secret URL Verification type in Celigo Webhook Connection
Setting up Http connection in Celigo
A. Set up an HTTP connection Start establishing the universal, or generic, HTTP connection in either of the following ways: Select Connections from the Resources menu. Next, click + Create connection at the top right. In the resulting Create source panel, select HTTP from the Application list, under the Universal connectors group. While working in a new or existing integration, you can add an application to a flow simply by… Continue reading Setting up Http connection in Celigo
Use the connections of Integration app in custom flow
The connections which are included in any of the pre-built Integration apps cannot be used in custom flows. For custom flows separate connections need to be created. This is by design to limit the load sharing on the Integration App connections. However, multiple connections to same endpoint can be created in any Integration App. By… Continue reading Use the connections of Integration app in custom flow
Switch connection within an integration app from a sandbox to a production instance
The integration apps on the Celigo integrator.io platform are built with fairly heavy components or dependencies on each application and thus switching endpoints or accounts wouldn’t be permitted. Attempting to make changes might impact the overall stability of your integration app and is NOT recommended. If a connection is dependent on a user within the… Continue reading Switch connection within an integration app from a sandbox to a production instance
BigCommerce connection with celigo
To connect BigCommerce with celigo , we need the access token ,Store hash, Client ID. Go to settings in the BigCommerce account . Select the API accounts Click on “create API account“ Add name for the account Make the selection for Oauth Scopes: Store hash is “rxmzgid9dc“ Click Save. The BigCommerce API Credential page is displayed that… Continue reading BigCommerce connection with celigo
Base URI in Multiple Scenarios | Celigo
//Info: JSTN-1308 This common part of an API’s URL is used across all of the HTTP endpoints you invoke. A base URI makes it easier to configure exports and imports.In Celigo, we can define the Base URI in the connection itself and can add a version to it. The Base URI is further called in… Continue reading Base URI in Multiple Scenarios | Celigo