Undocumented fields in user object

[mpickering]

An "in the wild" user object contains a few more fields which aren't documented in the documentation.

• status
• real_name_normalized
• is_bot
• title
• tz, tz_label, tz_offset

has_files also doesn't appear in the response.

skype and phone are also repeated in the user object and profile object. Which one takes priority and why are they repeated?

[paulhammond]

Thanks for pointing this out. We'll get the extra properties documented soon.

The repeated "skype" and "phone" properties will always be the same - and you should prefer the ones in the profile object. The other ones are only returned for backwards compatibility with older clients.

[awalla]

Hello! As a quick update to this, we do still have these changes to our documentation on our to-do list—we've not forgotten about them. Thanks for your patience!

[drawks]

I'm confused why this issue is closed... I don't see any changes to address these issues.

[matthewmueller]

+1 it's unclear when tz is null and when it's set

[gasi]

👍 to documenting real_name_normalized vs real_name. Thanks.

[tyson-kubota]

The page https://api.slack.com/bot-users (all the way down) even contains instructions on using user.is_bot to ascertain bot status:

You can tell if a user object returned by our API is a bot user by checking the is_bot property.

It might be nice to update the user object doc at https://api.slack.com/types/user accordingly.