Jump to content

Twitter API Update Causing Sign-In Integration Errors

Recommended Posts


Twitter have made some changes to their API this week which impacts our WHMCS Sign-In Integrations. More information on the changes Twitter have made are outlined on their community.

In essence, we can no-longer override the Callback URL used by the Twitter App. Instead the Callback URLs settings on the Twitter Developer site now act more like a whitelist. The Callback URL sent by WHMCS must match exactly with the Callback URL specified in the app settings, or the login will fail.

Error presents as:

In WHMCS this manifests itself as an error when attempting to login with Twitter:


We were unable to connect your account. Please contact your system administrator



Or when activating Twitter sign-in for the first time in the admin area:


Invalid details not saved. Please verify your details and try again




Because the Callback URL can take several forms, depending upon the Friendly URLs setting, we  are recommending users configure all three in their Twitter app settings.

  1. Visit https://apps.twitter.com/ 
  2. If not logged in, login to your Twitter account
  3. Select your WHMCS sign-in app from the list
  4. Click the Settings tab
  5. In the Callback URLs section, replace the current single entry with the following three entries:
    1. http://demo.whmcs.com/whmcs/index.php?rp=/auth/provider/twitter_oauth/callback
    2. http://demo.whmcs.com/whmcs/index.php/auth/provider/twitter_oauth/callback
    3. http:///demo.whmcs.com/whmcs/auth/provider/twitter_oauth/callback

      Remember to replace http://demo.whmcs.com/whmcs/ with the actual URL of your WHMCS installation
  6. Click Save Changes

More Information can be found at http://help.whmcs.com/m/troubleshooting/l/914546-troubleshooting-an-invalid-details-not-saved-error-when-configuring-twitter-sign-in-integrations



Share this post

Link to post
Share on other sites
This topic is now closed to further replies.

  • Similar Content

    • By mscholten
      I'm working on making it possible to show a Twitter feed based on the client. That way we can show different feeds for resellers and end-users. When someone isn't logged in I would probably show the end-user Twitter account. Changing the Twitter account for the URLs pointing to Twitter is easy. However with an AJAX (?) call it doesn't work. From WHMCS support I did hear I should be able to create some output on it when using the ClientAreaPage hookpoint. However this doesn't seem to work as the code below doesn't return any content (and that is what I would expect).

      <?php function whmcs_hook_test($vars){ var_dump($vars); } add_hook('ClientAreaPage',10,'whmcs_hook_test');
      Any pointers as where to look? Or should I just create a new PHP file for it that gets the required information from Twitter and call that file using the Javascript?
  • Recently Browsing   0 members

    No registered users viewing this page.


Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated