I would like to request that the contact profile/avatar URL be included in the webhook payload—similar to how it was implemented for the Instagram webhook—so that we can display it in our inbox conversation list.
Thanks Daniel. We looked into this properly. Meta's WhatsApp Cloud API does not expose a customer's profile picture anywhere: the message webhook only carries the contact's name and wa_id, the coexistence contact sync carries name and phone, and there is no Graph endpoint for it (we tested against our own numbers). Instagram works because Meta's User Profile API returns the picture for an IGSID; WhatsApp has no equivalent.
The only WhatsApp avatars Meta provides are for groups, which we already pass through as participantPicture. If Meta adds it to the Cloud API we will forward it in the same field, so your inbox code would need no change.
Log in to comment and vote
Comments1
Miquel Palet López
Sep 9
Thanks Daniel. We looked into this properly. Meta's WhatsApp Cloud API does not expose a customer's profile picture anywhere: the message webhook only carries the contact's name and wa_id, the coexistence contact sync carries name and phone, and there is no Graph endpoint for it (we tested against our own numbers). Instagram works because Meta's User Profile API returns the picture for an IGSID; WhatsApp has no equivalent.
The only WhatsApp avatars Meta provides are for groups, which we already pass through as
participantPicture. If Meta adds it to the Cloud API we will forward it in the same field, so your inbox code would need no change.