To main website
  1. Help Center - Channable
  2. Imports
  3. Import setups

Articles in this section

See more

Importing a password protected feed

Do you want to interactively learn about setting up your import in Channable? Learn how to create a Channacademy account in the Channable app through this Help Center article and start with the Basic Imports course.

Importing a password-protected feed is similar to importing a non-protected feed. The only additional thing you will need to do is configure the authentication.

Step 1 - Choose your feed type

In your project navigate to Setup and click "Setup import". You will be given a few options through which to import your products. Select your type of feed and click "Continue". We support authentication for the following file-based imports:

  • XML
  • CSV
  • JSON
  • Text file (.txt)

PFeed1.png

Note: we do not support importing a protected Google Spreadsheet. A Google Spreadsheet needs to be published online to be imported successfully. See this article for more information.

Step 2 - Fill in the URL

Next, fill in the URL of your feed.

PFeed2.png

Step 3 - Configure your authentication

We support various means of authentication for file-based imports depending on the protocol:

First you need to pick the relevant protocol in the drop-down menu.

PFeed3.png

HTTP and HTTPS

For HTTP and HTTPS protocols we support two authentication types:

  • Username & password (basic auth). Select “Username & password (basic auth)” next to the URL and fill in the username and password. 

PFeed4.png

  • Username & password (digest auth). This is another form of username-password authentication. It works the same as 'basic auth', but is less common.
Note: If you are unsure whether to use 'basic auth' or 'digest auth', consult your server administrator.
  • Authentication header. In this case, we will include an x-api-key header with the request. Select “Authentication header” next to the URL and fill in the header token. 

PFeed5.png

Note: for both "Username & Password" and "Authentication header", HTTP means that your credentials will be transmitted in the clear. To keep your credentials secure, use HTTPS.

FTP

For FTP, we also only support Username & password authentication. You can configure this the same way as for HTTP/HTTPS. 

Note: FTP is an inherently insecure protocol, your credentials will be transmitted in the clear. To keep your credentials secure, use SFTP.


SFTP (SSH File Transfer Protocol)

For SFTP, we currently only support Username & password login. You can configure this the same way as for HTTP/HTTPS. SFTP is secure, your credentials will be transmitted over an encrypted connection.