API Terminology difference with Twitter

  • Hi Folks,

    Newbie question but I was trying to do the setup and the terminology used for this plugin is different than what Twitter gave me when creating the app (assuming I did it right).
    The plugin is asking for:

    • Twitter API Consumer Key
    • Twitter API Consumer Secret
    • Twitter API Access Token
    • Twitter API Access Token Secret

    However, when I created the Twitter app it gave me different names and I have not been able to make them match up (Error: Twitter API Access Token not correctly formatted.), so any guidance would be appreciated. I know the instructions said I did not need a “Callback URL” but Twitter said it was required, not sure it that gave me anything different.
    The Twitter page is giving me:

    • API Key
    • API Key Secret
    • Bearer Key
    • Client ID
    • Client Secret

    Thanks, Nigel

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Martin Tod

    (@mpntod)

    The changes to Twitter mean that the section that calls off data is going to need to be rewritten.

    I’m planning to take out the necessary $100/month subscription (just to test it!) and give it a go.

    Hi Martin, any news on this? Do you think it may work again? Appreciate you creating this plugin.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘API Terminology difference with Twitter’ is closed to new replies.

Tags