I am using following Mentions Timeline API : -
https://api.twitter.com/1.1/statuses/mentions_timeline.json
I am performing authenticated API call for Mentions and using the application (tokens).
But, getting 403 Forbidden as response when i call authenticated Mentions API. prior of 14 Jan 2014 this Mentions API was working fine. after that it is returning 403 error.
I am getting response when i call following API authenticated with same application tokens: -
https://api.twitter.com/1/users/show.json?screen_name=XXXXX
Can anyone tell me why i am receiving response - 403 Forbidden for Mentions Timeline only not in other API calls
Thanks,
Ketan
Jan 14th is the day Twitter API switched to requiring SSL/TLS. This discussion has the details:
https://dev.twitter.com/discussions/24239
Based on your description, you should check your URLs to ensure they're set to "https://..." instead of "http://...".
Migrate to https://api.twitter.com/1.1/users/show.json
is now work endpoint for GET users/show.
403 Forbidden for Mentions Timeline it error mean invalidate token check authentication it requite oauth.
Related
For A few days, I have suddenly become receiving the 403 Forbidden response from https://www.youtube.com/oembed?url={youtubeURl}.
I have checked documents for Youtube API but I can't find that it has restrictions for getting oembed and has authorization too. I can only see a restriction for Youtube Data API.
Why do I get the 403 Forbidden response from this API...?
Sample sending request:
https://www.youtube.com/oembed?url=https://www.youtube.com/watch?v=qK5tNXJ6Ibo
Are you sure that you are making the requests as https ? The code I have been using is fairly legacy and when I went down through it the requests were http. Once I updated the code to make the call over https it stopped getting 403 errors. Seems this was just recently changed a couple days ago.
Trying to post events to user calendars for our organization. Getting a 401 error.
Azure admins created an app/user, and gave permissions
Delegated Graph Permissions: Calendars.ReadWrite
App graph permissions: Calendars.ReadWrite
I can connect to the OAuth token generation end point, and retrieve a token. Using that token, I can't send my JSON payload and create a series of calendar events, I get a 401. The JSON is known good - I can copy/paste it into the graph explorer tool and get correct results.
I've examined a generated token using jwt.ms and I'm not seeing anything related to permissions, calendars, etc.
Our Azure logins use empIDnumber#example.com and I've been told that is what our userPrincipalName is
I've tried changing the URL end point with no change-
/v1.0/users/empIDnumber#example.com/calendar/events
and
/v1.0/users/empIDnumber#examplecom.onmicrosoft.com/calendar/events
Where should I look next?
Solved.
Slight typo in the content of the JSON I was sending, was only able to find it by doing the POST using postman. Java was throwing an exception, not showing the returned string as well as the exception message, but postman showed the returned JSON with content regarding malformed date/time.
Still got 401 exceptions though, so The Fix Part II was to add an Accept-Encoding property set to application/json to my http client request options array.
Still no claims showing up in my tokens, but that is a non-issue apparently.
Up until today I have been able to use Google's api for exchanging an authorization code for an access token. Haven't had any problems with this for the past year. But now I'm getting a 403 status code. My POST body looks like this:
code=4%2FUwDPiS*********&
redirect_uri=https%3A%2F%2Flocalhost%3A57081&
client_id=123******&
client_secret=123*******&
scope=&
grant_type=authorization_code
The api endpoint is:
https://www.googleapis.com/oauth2/v4/token/
The Google API playground works fine when exchanging authorization tokens.
I thought that maybe Google was getting strict and required https to the redirect (which I did not have originally). But even after adding https, it didn't help. Is it possible that Google is now blocking redirects to localhost? If not, what other problem could it be?
Either Google's OAuth service was down at the time or my limit on calling the api was reached. Have no idea what caused the problem but it worked 24 hours later. In the event that you suspect that your limit was reached, you should check out this link:
https://support.google.com/cloud/answer/9028764
we use the following HTTP GET request to get group's info:
https://graph.microsoft.com/v1.0/groups/{groupId}?$select=visibility,unseencount
Until today (18 Sep 2018) it worked, but today it stopped working. Now Postman returns 403 Forbidden: ErrorAccessDenied (message: Access is denied. Check credentials and try again).
When unseencount is removed from url data is returned successfully with the same bearer token:
https://graph.microsoft.com/v1.0/groups/{groupId}?$select=visibility
Also in our app which uses Sharepoint SPFx and HttpClient it currently returns 400 Bad request for the same url.
I am not seeing that. Have you tried this out in the Graph Explorer signed in as your user (eliminates some mistakes possibly you not seeing in Postman etc.)? http://aka.ms/ge
Is it consistent for all groups? What about ones that the user belongs to?
You will need Group.Read.All to access this property. Ensure that's coming back in your access token.
https://developer.microsoft.com/en-us/graph/docs/api-reference/v1.0/api/group_get
When i am sending BitCoins using the send:to:withNotes:withHandler: method , the failure block gets invoked with error localised description mentioning error 403 forbidden.
A 403 response from the Coinbase API usually means your API key or OAuth token is lacking the required scopes for the specific request you are making.
Based on the name of the method, it sounds like it would be the Send Money request, which requires the wallet:transactions:send scope/permission.
You can check with permissions you have for an API key, or OAuth token using the Show Authorization Info request.