oAuth 1.0, Advanced Rest Client, Twitter API, Not Working
up vote
-1
down vote
favorite
I've done all the developer.twitter.com setup (created an app and a dev environment). In ARC, I have filled in the Authorization section, choosing oAuth 1.0, filled in the consumer key, consumer secret, token, token secret, and token auth URL. ARC created the timestamp and nonce, and I chose the HMAC-SHA1 realm. When I click "authorize", it just hangs; never comes back. When I try a simple GET on api.twitter.com/1.1/followers/ids.json?screen_name=< my screen name >, I get the 400 "Bad authentication data" with code 215 response. What am I missing? I've both created and consumed many REST APIs but never had a problem using ARC for them before.
twitter-oauth twitter-rest-api advanced-rest-client
add a comment |
up vote
-1
down vote
favorite
I've done all the developer.twitter.com setup (created an app and a dev environment). In ARC, I have filled in the Authorization section, choosing oAuth 1.0, filled in the consumer key, consumer secret, token, token secret, and token auth URL. ARC created the timestamp and nonce, and I chose the HMAC-SHA1 realm. When I click "authorize", it just hangs; never comes back. When I try a simple GET on api.twitter.com/1.1/followers/ids.json?screen_name=< my screen name >, I get the 400 "Bad authentication data" with code 215 response. What am I missing? I've both created and consumed many REST APIs but never had a problem using ARC for them before.
twitter-oauth twitter-rest-api advanced-rest-client
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I've done all the developer.twitter.com setup (created an app and a dev environment). In ARC, I have filled in the Authorization section, choosing oAuth 1.0, filled in the consumer key, consumer secret, token, token secret, and token auth URL. ARC created the timestamp and nonce, and I chose the HMAC-SHA1 realm. When I click "authorize", it just hangs; never comes back. When I try a simple GET on api.twitter.com/1.1/followers/ids.json?screen_name=< my screen name >, I get the 400 "Bad authentication data" with code 215 response. What am I missing? I've both created and consumed many REST APIs but never had a problem using ARC for them before.
twitter-oauth twitter-rest-api advanced-rest-client
I've done all the developer.twitter.com setup (created an app and a dev environment). In ARC, I have filled in the Authorization section, choosing oAuth 1.0, filled in the consumer key, consumer secret, token, token secret, and token auth URL. ARC created the timestamp and nonce, and I chose the HMAC-SHA1 realm. When I click "authorize", it just hangs; never comes back. When I try a simple GET on api.twitter.com/1.1/followers/ids.json?screen_name=< my screen name >, I get the 400 "Bad authentication data" with code 215 response. What am I missing? I've both created and consumed many REST APIs but never had a problem using ARC for them before.
twitter-oauth twitter-rest-api advanced-rest-client
twitter-oauth twitter-rest-api advanced-rest-client
asked Nov 10 at 18:42
JenVander
127110
127110
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The answer is, Advanced Rest Client just plain doesn't work with the Twitter API. I used Insomnia instead, and it worked with the exact same inputs that I gave to ARC. ARC has been a great tool for me for the past decade, so it's disappointing.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The answer is, Advanced Rest Client just plain doesn't work with the Twitter API. I used Insomnia instead, and it worked with the exact same inputs that I gave to ARC. ARC has been a great tool for me for the past decade, so it's disappointing.
add a comment |
up vote
0
down vote
The answer is, Advanced Rest Client just plain doesn't work with the Twitter API. I used Insomnia instead, and it worked with the exact same inputs that I gave to ARC. ARC has been a great tool for me for the past decade, so it's disappointing.
add a comment |
up vote
0
down vote
up vote
0
down vote
The answer is, Advanced Rest Client just plain doesn't work with the Twitter API. I used Insomnia instead, and it worked with the exact same inputs that I gave to ARC. ARC has been a great tool for me for the past decade, so it's disappointing.
The answer is, Advanced Rest Client just plain doesn't work with the Twitter API. I used Insomnia instead, and it worked with the exact same inputs that I gave to ARC. ARC has been a great tool for me for the past decade, so it's disappointing.
answered Nov 11 at 3:32
JenVander
127110
127110
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242237%2foauth-1-0-advanced-rest-client-twitter-api-not-working%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown