Title: Error 32
Last modified: August 22, 2016

---

# Error 32

 *  Resolved [sanjsvet](https://wordpress.org/support/users/sanjsvet/)
 * (@sanjsvet)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/error-32-33/)
 * I have the widget configured per instructions but I get the following error instead
   of Tweets being displayed.
    Error: Could not authenticate you (error code: 32)
 * I even deleted the app on twitter and created new one, updated all the information.
   Only thing I see different is that other plugins ask for consumer key wile this
   plugin requires API key and API secret.
 * Any help will be appreciated.
 * [https://wordpress.org/plugins/wd-twitter-feed/](https://wordpress.org/plugins/wd-twitter-feed/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Askupa Software](https://wordpress.org/support/users/askupa-software/)
 * (@askupa-software)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/error-32-33/#post-5220369)
 * Twitter cannot authenticate your tokens. “Consumer key” is the previous name 
   used by Twitter for what is now called “API key”. Same goes for the API secret.
 * Make sure you are inputting the tokens in the correct place.

Viewing 1 replies (of 1 total)

The topic ‘Error 32’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wd-twitter-feed_87b0b2.svg)
 * [Twitter Feed](https://wordpress.org/plugins/wd-twitter-feed/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wd-twitter-feed/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wd-twitter-feed/)
 * [Active Topics](https://wordpress.org/support/plugin/wd-twitter-feed/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wd-twitter-feed/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wd-twitter-feed/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Askupa Software](https://wordpress.org/support/users/askupa-software/)
 * Last activity: [11 years, 8 months ago](https://wordpress.org/support/topic/error-32-33/#post-5220369)
 * Status: resolved