So, ‘profile_location’ is returned by users/lookup in addition to all the fields returned by users/show.
Is this just an oversight/hangover from old code/whatever so that it can be ignored, or does it have a useful distinct usage?
I’m fairly certain that this is something that has come up before, and that yes, it’s a result of a couple of different code paths hydrating the user object differently when the bulk users/lookup endpoint is used. I’ll make a note to double-check this internally and get the documentation updated to clarify.
users/lookup
… apparently I made a note to do this a number of months ago, so I can only apologise that we haven’t tidied this up yet!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
