What is the exact reason behind Twitter API 403 statusCode? - twitter

I am getting statusCode 403 from Twitter API call 'statuses/retweet/:id'. The documentation says it is due to rate limit. But I am not RTing too frequently.
The returned message from Twitter is
twitterReply: '{"errors":"sharing is not permissible for this status (Share validations failed)"}'

The "Sharing is not permissible" usually relates to one of the following:
The user has forbidden retweets.
You have already retweeted that tweet.
The tweet has been deleted.
You have been blocked by the user.
The tweet is your own (you cannot retweet yourself).
Are you able to retweet any other tweets?

Related

How to determine when a tweet stops being promoted?

How can you determine when a tweet stops being promoted?
Twitter ads API will return a history of promoted tweets with
<accounts>/:<ad_account>/promoted_tweets
However, as far as I can tell, none of the fields from this endpoint tell us the status of this promotion. Is the tweet still being promoted? Was the tweet deleted? Etc.
This is a problem because if you ask for promoted metrics from the Twitter V2 API on a non-promoted tweet, the entire call fails. The error does not specify why the call failed so we can't recover properly by retrying or calling again without requesting the promoted fields.

Filtering by email addresses and names in SurveyMonkey's API v3

I'm upgrading my application from SurveyMonkey's API v2 to v3 and using the liogi/surveymonkey-api-v3 library to wrap around my API calls and have run into a problem.
The email, first_name, and last_name parameters for such endpoints as GET /surveys/{id}/responses/bulk seem to be ignored. No matter what value I enter for them, no responses get filtered out of my results.
Is this a bug?
Yes adding those as GET parameters in your request should filter responses by that recipient information.
For example:
/v3/surveys/<survey_id>/responses/bulk?email=test#example.com
Will return responses for survey <survey_id> where the recipient had email test#example.com. Note that only collectors of type email invitation have contact information that you can filter by. So responses taken by weblink will never have that data.
I just tested it out on the bulk endpoint and it successfully filtered it to just the one response with the email I used. I would first try to track the request your library is making to make sure it is sending the proper request format, if the request is proper and it still isn't filtering I would contact SurveyMonkey with more details about your request as in that case it'd likely be a bug.

Public/Private Events When Querying Facebook Graph API

I'm building an RoR application that uses the Facebook Graph API, scraping a users events via their user_access token. I'm essentially taking that user token and making a Graph call to the API, getting all the events the user has either given a rsvp, created, declined, maybe and not_replied response to the events they've been invited to. Here is my query...
GraphAPIEndPoint = [created, declined, maybe, not_replied]
GraphAPIEndPoint.each do|endpoint|
data = Koala::Facebook::API.new(access_token)
events = data.get_connections("me", "events/#{endpoint}", fields: ['id',"name","description","place","start_time","end_time","timezone","ticket_uri", "cover"])
end
This query gives me the desired data but I'm unsure whether I'm getting private events from the user, which I don't want. After I've received the data, I've checked some source url's in my browser, which show a Facebook default error page saying, "Sorry this page isn't available". Other Facebook url's I've tested show me their events as public events, only the ones that seem specific to a group of friends or family give me this default error page. Also, if the events were deleted by the author (which could be an answer as to why I'm getting the default error page), why am I still getting the JSON for the event?
My only assumption is that I am, and if so, what are the privacy parameters to prevent this from happening and give me only the public events?(Please no FQL suggestions)
Thanks for your help!

How to fetch the processingDetails,fileDetails,suggestions information from the youtube api

I am unable to fetch the processingDetails,fileDetails,suggestions information from the youtube api call. I had used API key to fetch these details but it's not working
First I tried this API Call mentioned below, It's working
https://www.googleapis.com/youtube/v3/videos?id=Skk6MBoejgU&key={API_KEY}&part=snippet,statistics,contentDetails,player
When I tried to fetch processingDetails,fileDetails,suggestions information, It's throwing error message
https://www.googleapis.com/youtube/v3/videos?id=Skk6MBoejgU&key={API_KEY}&part=processingDetails,fileDetails,suggestions
Error message: forbidden
Can anyone help me to solve this issue ?
Because you need to be connected with your YouTube Channel to get this informations.
In fact, this is private informations, you can only get this informations only from your videos.
We can find this information in the doc of YouTube API V3
forbidden (403) forbidden
The request cannot access user rating information. This error may
occur because the request is not properly authorized to use the
myRating parameter.

Can't use Instagram API to comment in my iOS app

I always get this message "Please visit http://bit.ly/instacomments for commenting access" when I use the endpoint /media/media-id/comments (see http://instagram.com/developer/endpoints/comments/) to post a comment to a friend's post in my iOS app, I requested these scopes from Instagram: scope=likes+comments+relationships.
I visited the web page mentioned in the error message and filled the form, months ago and not only once, but no lucky.
I also sent email to apidevelopers[at]instagram.com for access, still no lucky, and no response.
Anybody knows what w should I do?
You have to make a request to Instagram to get access to posting comments through the API. The email address is in the developer documentation. If you follow the link you are receiving in the error, it will take you to the page to request access.

Resources