Title: 403 Error when calling the RSS feed programatically
Last modified: September 12, 2019

---

# 403 Error when calling the RSS feed programatically

 *  [resetdesigngroup](https://wordpress.org/support/users/resetdesigngroup/)
 * (@resetdesigngroup)
 * [6 years, 8 months ago](https://wordpress.org/support/topic/403-error-when-calling-the-rss-feed-programatically/)
 * Hello,
    We are receiving 403 errors when attempting to access the RSS feed via
   the load function or Curl. If you visit the rss feed manually in a browser it
   works. But, if you attempt to call the feed programatically it breaks. I don’t
   see any way in the settings to stop this from happening. Any thoughts on how 
   to prevent this?
 * Also, I’ve read through, and attempted, all the approaches on the [iThemes documentation](https://ithemeshelp.zendesk.com/hc/en-us/articles/360005892693-Fixing-403-Forbidden-Errors).
 * Thanks,
    Tim
    -  This topic was modified 6 years, 8 months ago by [resetdesigngroup](https://wordpress.org/support/users/resetdesigngroup/).

The topic ‘403 Error when calling the RSS feed programatically’ is closed to new
replies.

 * ![](https://ps.w.org/better-wp-security/assets/icon.svg?rev=3529351)
 * [Kadence Security – Password, Two Factor Authentication, and Brute Force Protection](https://wordpress.org/plugins/better-wp-security/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/better-wp-security/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/better-wp-security/)
 * [Active Topics](https://wordpress.org/support/plugin/better-wp-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/better-wp-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/better-wp-security/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [resetdesigngroup](https://wordpress.org/support/users/resetdesigngroup/)
 * Last activity: [6 years, 8 months ago](https://wordpress.org/support/topic/403-error-when-calling-the-rss-feed-programatically/)
 * Status: not resolved