Get and update a user by Username

Hi Chris Auer , I just did a quick test like this

In my case, the username is "John.Reynolds"

First I tried "user" endpoint with Username Parameter

/api.ashx/v2/user.json?Username=John.Reynolds

=> Returned successful user object as JSON

Next I tried "users" endpoint with Username Parameter

/api.ashx/v2/users.json?Username=John.Reynolds

=> Returned error below

Thanks John, using user instead of Users in Telligent API doco code, returns a 404. So the only way I can find to get a user by username is by calling the username, is by calling the url /api.ashx/v2/user.json?Username=John.Reynolds. 

But I cant get the documented way to get and most importantly Update the user by username.

var host = new ClientCredentialsRestHost(
    communitySettings.Username,
    communitySettings.Endpoint,
    communitySettings.OAuthClientId,
    communitySettings.OAuthSecret);

var response = host.GetToDynamic(2, "user/{username}.json", true, new RestGetOptions
{
    PathParameters = new System.Collections.Specialized.NameValueCollection {
        { "username", username }
    }
});
return response;

If you are dealing with usernames that are all numbers, you will need to retrieve the user record by calling /api.ashx/v2/user.json?Username=12345 and then using the UserId from the record retrieved to update the user. 

What version are you?

11.1.6.14291

Thanks Matt, I'll give that a go. Does that mean the LookupUsername variable from this doco is invalid? community.telligent.com/.../update-user-rest-endpoint

The way I read it, Chris, (without trying it myself) is that you may need both lookupUsername and username to make a Username change.

Thanks John, the username property is only need if you are changing the username. I think its why they needed to come up with the weird "LookupUsername" property.

Are you having an issue with the Update endpoint for usernames that are not numbers only?  That should work fine. 

While you are defining the path like:

var response = host.PutToDynamic(2, "users/{lookupusername}.json", true, new RestPutOptions
{
PathParameters = new NameValueCollection {
{ "lookupusername", username }
},

The system just receives users/12345.json.  It has no idea you called that variable lookupusername.  It just sees the integer value and assumes its a userId.

Mathew D'Amico  Since it is an int, users/12345.json turns into userId = 12345. If it wasn't an int, it would work (I.e. users/1234X.json). So it seems like it does a int.TryParse and if it succeeds, it uses it as a userId else username. Not how I would write my API code.

I think you are right, I need to get the user via username=12345 and then update via that user's true userid. 

Mathew D'Amico  Since it is an int, users/12345.json turns into userId = 12345. If it wasn't an int, it would work (I.e. users/1234X.json). So it seems like it does a int.TryParse and if it succeeds, it uses it as a userId else username. Not how I would write my API code.

I think you are right, I need to get the user via username=12345 and then update via that user's true userid. 

>> Thanks John, the username property is only need if you are changing the username.

Right, but if you are changing a value that you're also using for lookup, then you naturally would have to provide two parameters, one for the lookup (lookupUsername), then one for the new value you're setting (username)

But with that said ...

>> I think you are right, I need to get the user via username=12345 and then update via that user's true userid. 

Yes, I'd recommend the same as a best practice.