Any reason why the profile_banner_url field present in the v1.1 user object is not in the api v2 user object?
1 Like
I was thinking about it too. Any updates on the issue?
There are a few requests for this on the API feedback channel - I would recommend adding your requirements and use cases to one of these / upvoting the request so that our product team are aware.