Scott_Hack reports that their RSS feed from a restricted Discourse forum, accessed via a URL with an API key, is no longer valid according to MailChimp and Mailerlite, despite working fine when loaded manually and passing validation with warnings Scott_Hack. Maiki suggests checking with the email service provider and testing with a validator maiki. Itsbhanusharma theorizes the issue may stem from changes in API authentication, requiring headers instead of URL parameters, and references the Discourse API documentation itsbhanusharma. Scott_Hack confirms the feed works in an incognito window and passes validation but remains puzzled, noting multiple providers reject it Scott_Hack. Maiki reiterates that the issue likely lies with the email provider maiki. Scott_Hack seeks a fix or explanation Scott_Hack. Craigconstantine asks if the issue was resolved, indicating interest in using Discourse RSS feeds in Mailchimp craigconstantine.
I was using an RSS feed of latest.rss pushed into MailChimp to send an email 3 times a week to subscribers… But MailChimp is now saying the RSS Feed Link isn’t valid. Anyone else having trouble?
I am appending the ?api=xxxx key on the end of my URL since my forum is restricted to only logged in users. When I load the RSS feed URL in my browser, it loads up fine. But I tried both MailChimp and Mailerlite to see if I could get the RSS to email setup and both of them say the RSS feed is invalid.
I’m not a 100% sure but this may be related to how API authentication is changed. The API key and username parameter are now required to be supplied in the request headers. Does mailchimp support supplying custom headers to the request for RSS?
This article will help you frame requests appropiately.
Thank you, that post says that it shouldn’t change and the weird thing is when I load the URL manually it does load for me in an incognito window and it also seems to pass validation ( though with a lot of recommendations ) – Hoping I am not the only one that has had this issue…