Endpoint Configuration

Endpoint configuration can differ from each connector but were going to go over a few specific connectors to help understand what exactly these endpoints are for, and how we can set them up to use them in our jobs. To start off lets take a look at our Contentful Connector endpoint here we have Four properties to set up -Token: the content mangaement token to use Contentful's API. (Ex: this is where we would put our contentful token for each individual space that we want to connect to) -Space: The space that should be searched for content and content should be synced to. (Ex: This is the space ID that we would enter to have impulse access and identify where the space is in the contentful instance) -Environment: This is the environment ID that your contentful space uses, this is what we use in addition to the space and token to connect to the contentful space in order to find the content, so you can have multiple environments without impulse syncing content from each environment. -rateLimitperSecond: This is used to control the rate at which certain operations can be executed to prevent excessive usage or abuse of resources, this can be set at 7 this is the default rate limit for most endpoints and connectors.

Additionally to each custom connector configuration there is also a source and destination part to set up. It's the same config as if you were to set a source endpoint and its good practice to set up both source and destination config when creating an endpoint. Now that we have our endpoint set we can use them in what we call our jobs. Make sure to click the ACTIVE checkmark otherwise we will not be able to use the endpoint when setting up our jobs.

To demonstrate how to set up another endpoint lets take a look at the one we will be using through this walkthrough we'll be using a Strapi endpoint to start lets take a look at what we need to enter for the configuration

-StrapiURL: This is the url that impulse will use to connect I am running a local version of strapi so my screenshot will be different but the principles are the same, the url that you need to connect impulse connects through a series of requests so we need these requests to go to strapi itself. For exmaple we will be adding the value "http://strapi-source:1337" -user: This is the user that you will login with to your strapi environment with permissions to edit content. -password: This is the user that you will login with to your strapi environment with permissions to edit content. -rateLimitperSecond: This is used to control the rate at which certain operations can be executed to prevent excessive usage or abuse of resources, this can be set at 7 this is the default rate limit for most endpoints and connectors.

For example this would be a standard endpoint set up: (loginUser and loginPassword are not required for this demo, the source and destination properties are the same for this demo)

in addition using this same principles we can add endpoint configuration to our Source endpoint from dotcms