Unable to get user details from yammer API when user name contains period

Question

1.00/5 (3 votes)

See more:

Hi All,

I'm facing a peculiar problem while accessing user details using Yammer REST API.

I'm using the following endpoint to access the user details

https://api.yammer.com/api/v1/oauth/tokens.json?user_id=USERNAME&consumer_key=CONSUMERTOKEN

The problem is when the user name does not contains a period "." (like johns) the API is working fine and not giving any error, but when the user name contains a period (john.s) the API is giving error HTTP 400 bad request.

I'm sending the request like

https://api.yammer.com/api/v1/oauth/tokens.json?user_id=john.s&consumer_key=CONSUMERTOKEN

Am I missing something. I'm using postman to test the API and also tried with C# code to get the result, but ended with a same problem (HTTP 400 Bad request).

What I have tried:

I've used postman to test the API endpoint. Everything is fine when the user name does not contains a period (".") but when the user name contains period (".") the endpoint response is HTTP 400 Bad Request

Posted 24-Aug-17 6:55am

Amlan Sengupta

Updated 24-Aug-17 12:46pm

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2017-08-24T08:48:00

Solution 1

This question should be brought up with Yammer, not some 3rd party website that doesn't support it.

Posted 24-Aug-17 8:48am

Dave Kreskowiak

Graeme_Grant · Answer 2 · 2017-08-24T12:46:00

Solution 2

Quote:
I'm sending the request like

https://api.yammer.com/api/v1/oauth/tokens.json?user_id=john.s&consumer_key=CONSUMERTOKEN

You need to URL encode your QueryString. Please read this: WebUtility.UrlEncode Method (String) (System.Net)[^]

UPDATE: Looking at the Yammer API documentation, OAuth 1.0a is not supported. You need to use OAuth 2.0. REF: OAuth 2: Server & Client-Side Flow · Yammer Developer Site[^]

Quote:
https://www.yammer.com/oauth2/authorize?client_id=[:client_id]&response_type=code&redirect_uri=[:redirect_uri][^]

Posted 24-Aug-17 12:46pm

Graeme_Grant

Updated 25-Aug-17 0:02am

v4

Comments

Amlan Sengupta 25-Aug-17 4:57am

Already done that...without any result

Graeme_Grant 25-Aug-17 5:04am

we have no idea as you have posted no code... The URL samples above say otherwise...

Amlan Sengupta 25-Aug-17 5:06am

I'm using POSTMAN to check the endpoint

Graeme_Grant 25-Aug-17 5:30am

Again, we can't see what you are seeing. HTTP 400 Bad request - this is saying that there is an error with your call. If you are using POSTMAN, or Fiddler for that matter, then what does the inner error response say? Normally returned in the body...

Amlan Sengupta 25-Aug-17 5:39am

In the reply body I'm getting the following text
Unexpected ''

Graeme_Grant 25-Aug-17 5:50am

This is telling you that you are not correctly encoding the QueryString. Check your encoding. show me your encoded call.

Amlan Sengupta 25-Aug-17 5:59am

The encoded URL string is

https%3A%2F%2Fapi.yammer.com%2Fapi%2Fv1%2Foauth%2Ftokens.json%3Fuser_id%3john.s%26consumer_key%CONSUMERKEY

Graeme_Grant 25-Aug-17 6:00am

And that is not how you do it.

Also, have a read of the UPDATE on my solution posting.

Graeme_Grant 25-Aug-17 6:06am

Also, https://api.yammer.com/api/v1/ appears depreciated and replaced with https://www.yammer.com/api/v1/