-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
send_message
returns 400 error always.
#22
Comments
Me too got same bug. any update? |
The same to mine, others work well but |
@codeboxanvo I used linkedin rest API it works for me. There is problem in this gem for sending message. data = {subject: 'subject', body: 'body', recipients: {values: [uid].map{|profile_path| {person: {_path: "/people/#{profile_path}"}} } }} HTTParty.post("https://api.linkedin.com/v1/people/~/mailbox", headers: { 'Content-Type' => 'application/json'}, query: {oauth2_access_token: 'xxxxxxxxxxxxxxx'}, body: data.to_json) |
From latest code, it seems the same data format with linkedin documents |
@codeboxanvo yes same format but some data is missing in request. tats y it return 400. |
Just in case, yes I have configured the gem with my app_id, app_secret, and I'm getting user tokens through the oauth2 login process using omniauth.
Other endpoints, like
#connections
are working fine and returning data, but not#send_message
.Is possible
#send_message
is outdated? Can I put Faraday on verbose mode so I can debug this?The text was updated successfully, but these errors were encountered: