Skip to content

User Phone Numbers in participant Field Are Now Encrypted/Hashed #2035

@vinicius-acruz

Description

@vinicius-acruz

Welcome!

  • Yes, I have searched for similar issues on GitHub and found none.

What did you do?

I was extracting user phone numbers from group messages using the Evolution API webhook messages.upsert, accessing the clear phone number from the key.participant field:

// Previous working code const userNumber = webhook.data.key.participant.split('@')[0]; // Expected result: "5511987654321" (clear phone number)

This pattern worked correctly for identifying users in group conversations and storing user data by phone number.

What did you expect?

The user's actual phone number should be available in the key.participant field in a readable format (e.g., "5511987654321@s.whatsapp.net"), allowing proper user identification and database operations.

What did you observe instead of what you expected?

The key.participant field now contains what appears to be encrypted or hashed values instead of actual phone numbers:

{ "data": { "key": { "participant": "86797614883006@lid" // ← Encrypted/hashed user phone number } } }

Screenshots/Videos

No response

Which version of the API are you using?

v2.2.3 build 171

What is your environment?

Windows

Other environment specifications

No response

If applicable, paste the log output

No response

Additional Notes

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions