Add profile_banner_url to v2 User object

[HitomaruKonpaku]

Hi,

As title said, can we have profile_banner_url return in API v2 users lookup?

I saw many people asking for it too. See: https://twittercommunity.com/t/profile-banner-url/155807

[andypiper]

Hi @HitomaruKonpaku - thank you for your suggestion. The process for the Open Evolution repository shows how you can go about having this feature considered by our engineering team. We require a Pull Request to be submitted following the appropriate template before we will initiate a formal internal review process.

This issue is a great start, as a discussion. Can you expand on why this is a useful addition for you / what the wider use case is, and how you might expect to have the data returned from the API?

[HitomaruKonpaku]

Hi @andypiper , thank you for your reply.

As I see in the process, I should make an issue to discuss about it before actually making a PR, so I landed here.

As for the profile_banner_url field, I followed a lot of artist with cool/nice banner profile so I made a bot to check for their profile to look for any change & save them.

I expect to have nullable profile_banner_url under User object (same as v1 User object).

{
  "id": "916156645004029952",
  "username": "hololivetv",
  ...
  "profile_image_url": "..."
  "profile_banner_url": "https://pbs.twimg.com/profile_banners/916156645004029952/1575255602"
}

[metaglobal]

Can't this field be added yet? Everyone needs him so much. Waiting too long? Is the team not working?

[andypiper]

Just a reminder that in order to contribute a feature for direct consideration by the engineering team, there's a workflow via opening a pull request on this repository, that requires a specific format.

As an additional reminder, if you'd like to participate in the discussion please be respectful and follow the Twitter OSS code of conduct. Thank you!

[dickhardt]

created https://github.com/twitterdev/open-evolution/pull/31

[dickhardt]

@metaglobal @HitomaruKonpaku @andypiper see submitted pull request

[andypiper]

Unfortunately I’m no longer able to work on this project.

[dickhardt]

@andypiper too bad for us.

[ktecho]

Any new on this? In 5 days the v1 API will stop working and there is not an alternative in v2?