Connecting a Password-Protected Feed

If your product feed sits behind a username and password, enter them in the feed source dialog rather than putting them in the URL. Renable stores them with the feed and uses them on every import.

Updated November 6, 2026

If a feed needs a username and password, enter them in the feed's source dialog, not in the feed URL. This works for your product feed and any auxiliary feed, on web addresses and SFTP alike.

When Renable tells you the feed needs a sign-in#

Paste the link, and the preview tells you if a sign-in is needed.

  1. Open your catalog and go to Data sources.
  2. Click the feed: your product feed, or one in the list under Auxiliary feeds.
  3. Paste the feed's link into the Feed URL field, without any credentials in it.
  4. If the feed needs a sign-in, Username and Password fields appear below the Feed URL field.
  5. Enter them. Renable checks them as you type, and when they work you see "Signed in as …" and a preview of your feed's columns and example rows.
  6. Click Save, then Publish.

Setting a sign-in up front#

If you already know a feed is private:

  1. Open the feed.
  2. Choose Add a username and password, below the Feed URL field.
  3. Fill in the fields, then Save and Publish.

Checking and changing them later#

Choose Change on the "Signed in as …" line to edit the sign-in. The eye icon at the end of the password field shows the saved password, so you can check it rather than retype it.

  • To replace it, type the new one over the field.
  • To remove it, clear both the username and password fields and save.

If you change the Feed URL to another website, or switch between a web address and SFTP, the fields empty and saving removes the stored sign-in, so it's never sent to the new address. Enter a new one before you save if the new address needs it. Change the address back before you save and the sign-in returns. Moving from http:// to https:// on the same website keeps it. Restoring an earlier version of the catalog restores the sign-in that version had.

Anyone with access to your Renable account can read a saved password, so treat it like any other shared account setting. If your feed provider can issue a dedicated read-only login for Renable, use that instead of your own.

Why not put credentials in the URL?#

A URL such as https://user:password@example.com/feed.xml still works, so existing catalogs keep importing. But URLs appear on screen and in error messages when an import fails, which makes a password in one easy to share by accident in a screenshot or a support message.

If you open a feed that has credentials in its URL, Renable moves them into the fields and shows the URL cleaned up. Save to complete the switch. The same happens if you paste such a URL into a chat with Aimée.

If the feed still won't load#

Find the message you're seeing:

  • This feed needs a username and password. Renable reached the feed, but nothing is saved for it. Add the sign-in in the feed's source dialog, then save and publish.
  • The feed rejected the username and password saved for it. Reveal the password with the eye icon and check it character by character, then try opening the feed in a browser. If your provider gave you a token, put it in the field they specify: some use the token as the username and leave the password empty.
  • The feed's server refused the request without asking for a sign-in. This usually isn't a credentials problem. The server may block automated requests, or the feed address may have expired or been revoked. See My feed import failed for both fixes. If your provider says the feed does need a sign-in, add it with Add a username and password and try again.
  • The feed's server refused the request even with the username and password. The server didn't say they were wrong. They may not grant access to this particular feed, so check with your provider, or the server may block automated requests whatever the sign-in, which My feed import failed covers.
  • The SFTP account is not allowed to read the feed file. The sign-in worked, but the account has no permission for that file or folder. Ask whoever runs the SFTP server for read access, or for the path of a file it can read.
  • That address returned a web page, not a product feed. A sign-in page is a web page too, so a wrong or expired link often shows up this way. Check that you're using the direct feed link, not a login screen or a product listing, then re-check the username and password. My feed import failed lists the other causes.

If the feed redirects to another domain, Renable doesn't send your sign-in there: it goes only to the host you entered. If the destination needs it, the fetch fails with an authorization error, so ask your provider for the direct URL.

Or ask Aimée#

Tell her what changed: "the feed needs a login now, the username is shopfeed and the password is …". She can also read what's saved, so you don't need to send a password again to confirm it.