Authorising problem

Support / help / discussion forum for twitter bot
Post Reply
Db949
Posts: 119
Joined: Sat Sep 02, 2017 10:31 am

Authorising problem

Post by Db949 » Sat Jul 14, 2018 11:48 am

Starting: 14/07/2018 12:44 PM
Validating: @Hiphop138387 No Proxy
procauth: authorise.Process
Attempt login
Login: @Hiphop138387: 73849218 No Proxy
UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Login: get: https://apps.twitter.com/
Already logged in: @Hiphop138387
Authorise : @Hiphop138387 No Proxy
request token: API Consumer key: bxNPu5hB7Fqd4UKxB78waPboY API Consumer Secret: vdscKW1c7TveGlQD92LusZ7R9dggMgImObttqYa6EqSYW3qeiC
Generate request: bxNPu5hB7Fqd4UKxB78waPboY vdscKW1c7TveGlQD92LusZ7R9dggMgImObttqYa6EqSYW3qeiC
* WARNING CANNOT AUTHORISE AS NO CALLBACK URL SPECIFIED

Due to a twitter.com the Callback URL of the API APP being authorised must be specified.
Please specify the CALLBACK URL to either the Global API APP details on the SETTINGS tab, or
For the custom API APP details on the account details form

Can you please tell me why I can't authorize my account?

User avatar
martin@rootjazz
Site Admin
Posts: 18502
Joined: Fri Jan 25, 2013 10:06 pm
Location: The Funk
Contact:

Re: Authorising problem

Post by martin@rootjazz » Sat Jul 14, 2018 3:58 pm

* WARNING CANNOT AUTHORISE AS NO CALLBACK URL SPECIFIED

Due to a change in twitter.com the Callback URL of the API APP being authorised must be specified.
Please specify the CALLBACK URL to either the Global API APP details on the SETTINGS tab, or
For the custom API APP details on the account details form
Is this a new API KEY set or old? If old, you will need to go into apps.twitter.com and set / extract the CALLBACK URL and enter it into the program. Either as the global key callback url (if you are using global key) or account specific (if using account specific)

If none of this makes sense, let me know how you created the API KEY (either manually or let the program do it ) and I can provide more indepth instructions

Db949
Posts: 119
Joined: Sat Sep 02, 2017 10:31 am

Re: Authorising problem

Post by Db949 » Sun Jul 15, 2018 5:20 pm

I didn't create it manually, & yes it doesn't make sense to me and I'm confused lol. I authorised the accounts in Twitterdub

User avatar
martin@rootjazz
Site Admin
Posts: 18502
Joined: Fri Jan 25, 2013 10:06 pm
Location: The Funk
Contact:

Re: Authorising problem

Post by martin@rootjazz » Mon Jul 16, 2018 3:55 pm

Db949 wrote:
Sun Jul 15, 2018 5:20 pm
I didn't create it manually, & yes it doesn't make sense to me and I'm confused lol. I authorised the accounts in Twitterdub
Ok, so the program created it before. But recently Twitter changed the rules.

Couple of options.
1) just get the program to create a new API KEY for you.
goto ACCOUNTS tab
check account
click CREATE APP KEY


2) login into the account that created the API APP KEY
apps.twitter.com

Select the API APP key you are using
click SETTINGS TAB
find the CALLBACK URL

Copy this and paste it into the app. Either:
a) SETTINGS TAB: global keys: callback url

b) or if just used for this account:
account details form: callback URL



I think you are probably using a global key, so (a)

Post Reply