I wanted to fetch the messages that was sent to the other connected linkedin users.
I found a code sample to send the message in this site
https://developer.linkedin.com/documents/sample-code-sending-message
But, I did not any sample to fetch the messages.
However, when I tried to fetch the message with the query "/people/~/mailbox", I got the error
"The remote server returned an error: (403) Forbidden."
In detail error message, I got "Access to mailbox denied".
These 2 documentations has listed only the Primary Endpoints "POST /people/~/mailbox" but has not mentioned about GET.
https://developer.linkedin.com/oauth-10a-overview
https://developer.linkedin.com/documents/authentication#oauth2-redirect-uri
Is there any way to fetch the message? Or Is there any workaround?
Any insights or help will be highly appreciated.
Thanks
I don't think Linkedin Inbox is supported any longer through their API. As per this answer on quora,
API is not publicly available but has been made available to several
partners. The best thing to do is contact LinkedIn's BD team for
access.
I was not able to see any specific mention to this type of access in their documentation.
Furthermore, check out APIGEE Snapshot for LinkedIn's 3 main API categories
Related
We are trying to download attachments from RingCentral (Glip), however, we have noticed that the download URL has been changed during the last couple of days. We have tried using the Bearer Token with the new download URL to download the files, however, we have received an error with response code 503.
ERROR
503 ERROR
The request could not be satisfied.
The Lambda function associated with the CloudFront distribution is invalid or doesn't have the required permissions. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by CloudFront (CloudFront)
Request URL
dl.mvp.devtest.ringcentral.com/file/105660426
The only change necessary for the recent auth change is to add the Bearer Token to the URL. This can be seen in the update notice:
What do I need to do?
To eliminate or minimize the impact of this change, developers will need to modify their application to attach authentication credentials to all file download requests. See downloading protected content in the Media content section of the RingCentral Developer Guide.
https://medium.com/ringcentral-developers/important-changes-to-how-team-messaging-files-are-downloaded-bb13c97b3c89
A 503 HTTP Status Code is a temporary sever-side error so there's generally nothing to be done on your end but the problem should go away on its own. If you cannot wait or it's taking a long time to resolve itself, please create a support case so the team can communicate the status to you.
Here's some information on 503 errors from MDN:
503 Service Unavailable
The HyperText Transfer Protocol (HTTP) 503 Service Unavailable server error response code indicates that the server is not ready to handle the request.
Common causes are a server that is down for maintenance or that is overloaded. This response should be used for temporary conditions and the Retry-After HTTP header should, if possible, contain the estimated time for the recovery of the service.
Caching-related headers that are sent along with this response should be taken care of, as a 503 status is often a temporary condition and responses shouldn't usually be cached.
I'm attempting to access the LinkedIn API's so I can post some text to a page via c# but I'm running into the titled error when attempting to retrieve the user handle.
I've followed the guides that have me set up an application, verify that application, get the auth code (approved), get an access token, and now I"m stuck on retrieving the handle.
I've tried using both the liteprofile and the basic profile. Whenever I attempt to use the liteprofile I get the "unauthorized_scope_error" message in my redirect url. When I use the basicprofile I get the authorization code but then run into the permission error.
I've also been reading about how liteprofile is the profile that "should" be used right now but that it also has its disadvantages.
I'll try to add some code while also removing some of the personal stuff (the removed code will be in {}).
Here's my Postman GET that gives me a successful redirect and auth code:
GET https://www.linkedin.com/oauth/v2/authorization?response_type=code&client_id={client_id}&redirect_uri=https://www.linkedin.com/company/{removed}/admin/&state=fooobar&scope=r_basicprofile%20r_emailaddress%20
Here's my POST (using the auth code from the previous GET) to retrieve my access token:
POST https://www.linkedin.com/oauth/v2/accessToken?grant_type=authorization_code&code={code}&redirect_uri={redirect_url}&client_id={client_id}&client_secret={client_secret}
Here's my Postman GET that should be giving me the handle but instead is returning the error:
GET https://api.linkedin.com/v2/emailAddress?q=members&projection=(elements*(handle~))&oauth2_access_token={access_token}
And the error:
{
"serviceErrorCode": 100,
"message": "Not enough permissions to access: GET-members /emailAddress",
"status": 403
}
I would like to get the handle for the linked in page but instead I'm receiving the titled error message in the response body.
Issue with oAuth 2.0 LinkedIn Upgrade API Web Service it Seems.
Please refer this
https://github.com/laravel/socialite/pull/310
When I run the "Getting Started" C# project of DESIRE2LEARN, I always get
The remote server returned an error: (403) Forbidden.
I don't provide values for UserId and UserKey fields for "Get Version" method, I only set Host, AppId, AppKey values for the new server, but it is not working still.
Then, I thought this could be related to wrong port#. I set it 443, but do not know what it is exactly. I set the port# wrong for D2L test-server in the working project file, and I got a different error:
"Unable to connect to the remote server".
So, I do not think it is about port#. My guess is that this is about API-related permission issue in the server. Do you think that the administrator need to change the settings in the server accordingly, so that access through API could be possible? Have you ever needed to configure the server for allowing access through API?
If you're retrieving a 403 (No Permission) error, it seems unlikely that your LMS has all support for the Valence Extensibility turned off (as it's likely that the API service layer itself is returning this error). It could be possible that the AppID/AppKey credentials that you're using are not recognized by your LMS. I suggest you open an issue with the Valence issue tracker, and work through the issue there. They may want your LMS admins to open a customer support ticket with Desire2Learn, in order to investigate the configuration of your LMS to ensure everything is properly set up.
I am using a C# .NET 2.0 winform in 2010, I have added the ability for a user to log in and post comments. I copied the .NET developer guide in how to post comments but I am getting random but frequent exceptions when trying to post comments. At first I thought it might be because there is some issue with using a google e-mail instead of the youtube log in name, to get around this when a user succesfully logs in I request the profile, get the user name and create a new youtube settings class and give the appropriate credentials with the users profile name. This however hasn't resolved the issue, the comments still work sporadically. Here is the code that basically handles logging in.
youtubeService.setUserCredentials(userBox.Text, passwordBox.Text);
try
{
String strAuth = youtubeService.QueryClientLoginToken();
}
catch (Exception ex)
{
}
The above code is in a seperate form, the form that hosts the youtube video basically looks to see if this process has been completed and grabs the username, password used to log in and sets the new settings:
m_LoggedInSettings = new YouTubeRequestSettings(myappname, mydevkey, username, password);
m_LoggedInRequest = new YouTubeRequest(m_LoggedInSettings);
This then used to add a comment:
Comment userComment = new Comment();
userComment.Content = commentText;
m_LoggedInRequest.AddComment(youtubevideo, userComment);
When it fails I get the following:
{"Execution of request failed: https://gdata.youtube.com/feeds/api/videos/t-8K8Hj8bxE/comments"}
With the following info:
{"The remote server returned an error: (403) Forbidden."}
Status code:
System.Net.HttpStatusCode.Forbidden
Status description:
Forbidden
A few things come to mind, I do not have a proper log out that sends anything to youtube implimented at the minute (is this needed?), so it may be that I've logged in multiple times and that is somehow flagging on youtubes side? It could also be that I am essentially creating new settings and request objects that weren't used to get the video/comments and maybe the video taken from the normal settings file (with no log in) is giving problems or something like that? To be honest, I haven't got a clue what is wrong and any help would be greatly appriecated.
Okay, so I figured out that the reason they were erroring is because I was trying to post consecutive comments too fast, however I don't know what the timeout is for being able to post more comments.
I need to find the mailbox size for the particular account and i have used c# coding with webdav But i am getting error when i used the code .
Please find the error message
The remote server returned an error: (440) Login Timeout.
Please find the reference link which i have used for code.
http://msdn.microsoft.com/en-us/library/ms877932%28EXCHG.65%29.aspx
Could anyone please help me to solve this issue?
When a HTTP or WebDAV request is issued agains an Exchange 2003 or 2007 public folder or mailbox folder, the server returns a HTTP/1.1 440 Login Timeout error if Form Based authentication is enabled.
See the sample code at http://www.infinitec.de/post/2004/12/Access-the-Exchange-store-via-WebDAV-with-Form-Based-Authentication-turned-on-Updated.aspx