#42

I can’t seem to reproduce this

#43

@andypiper @IgorBrigadir if i want to subscribe other user’s account, how can i get them access token?

#44

Any one of the ways, using PIN based auth https://developer.twitter.com/en/docs/basics/authentication/oauth-1-0a/pin-based-oauth, or browser or mobile flow here: https://developer.twitter.com/en/docs/basics/authentication/guides/log-in-with-twitter

#45

you like to use “OAuth 1.0a” or " OAuth 2.0" :smiling_face_with_three_hearts:

#46

image
image1428×1024 268 KB
those api link all 404

#47

Oh, that documentation was recently updated, there may be some links still broken. You definitely need “OAuth 1.0a” - the one with user context - here’s an example of login with twitter that might be good: https://github.com/jaakko-sf/twauth-web

#48

A problem bothers me, for example, i want to get user A’s access token, and you know i don’t have his account’s password, Is it going to work？by using twitter’s api? @andypiper @IgorBrigadir

#49

Oh, maybe that part wasn’t clear - any twitter user must explicitly authorize your application in order for you to get their access token - you can’t add arbitrary users to you application without them knowing. To obtain an access token a user must still log in somehow and accept your app. But the OAuth flow doesn’t involve passwords at all - it’s tokens, so you don’t need user passwords.

#50

this api : https://developer.twitter.com/en/docs/basics/authentication/api-reference/authenticate

image
image1071×782 77.2 KB

is this “request_token” is mine developer’s access_token and the “screen_name” is the user who i wanna to get his access token?

#51

no, the request token here is https://developer.twitter.com/en/docs/basics/authentication/api-reference/request_token

screen_name is for the login box if the user is not logged in already, so it’s optional.

#52

image
image2124×972 319 KB

the params has no screen_name define, where it is?

#53

@IgorBrigadir :face_with_monocle:

#54

I think having the overall picture first will help - this is a good page to start with https://developer.twitter.com/en/docs/basics/authentication/guides/log-in-with-twitter or https://developer.twitter.com/en/docs/basics/authentication/oauth-1-0a/obtaining-user-access-tokens, and then go back between that and an example implementation from github for specific parameters and calls

#55

do you know twitter’s webhook event has a rate limit?

#56

yes, there are limits https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/api-reference/aaa-premium

but as far as i know, there aren’t limits on the number of events you can receive in the webhook (you get everything) but the sandbox tier also doesn’t support replays so if there are missing events you won’t be able to recover them.

#57

What is the limit on the number of event push? For example, you can push 100 times a minute at most. Is there any limit? I read the document and didn’t mention it.

#58

also，i saw this api link:https://developer.twitter.com/en/docs/tweets/post-and-engage/api-reference/post-statuses-update, has a limit named “Requests / 3-hour window 300* per user; 300* per app”, is that means i can only use this api to 300 user in 3 hours?

#59

@andypiper

#60

yes

#61

Can I charge money to increase the limit? If so, where is the document written? I haven’t seen the document in the corresponding interface.