Skip to main content

Blip Portal - Evolution in Contact Structure

  • Updated

Index

  1. Overview

  2. New Contact Views in the Desk

  3. New Contact Filters

 

⚠️ The behaviors below represent the current design of the functionality and may evolve until the final release. 
 

Overview

The platform evolution includes new views in the contact structure and also in related sections to display all the IDs listed below:

  • BSUID

  • Username

  • Parent BSUID

  • WaId (phone number)

  • New filters

  • New contact properties

The new fields will be filled only if provided by Meta and will be available for viewing and reference on the platform. Manual editing of these fields is NOT allowed.

It is worth noting that the new WaId property does not replace the current contact phone number field, which continues to exist as an editable field and is still referenced by the variable contact.phonenumber. This field will not undergo any changes or updates and will maintain its current behavior. 

 

In the Desk (evolution)

Coming soon!

The contact view in the Desk will start to include Blip ID and BSUID information.

 

Contact Filters in the Blip Portal

Coming soon!

The contact search filters will allow searches by WhatsApp ID, Username, and BSUID, with the conditions described below.

Property Filter Condition
WhatsApp ID (waId) Same conditions as for Phone Number
Username Equality
BSUID Equality

 

Via Blip API - GET /contacts

Live now!

The endpoint GET /contacts is already enabled to return the new IDs linked to the WhatsApp usernames rollout. The request object does not change. The new fields are read-only and are returned only if filled, provided Meta has sent this data.

Example: 

{
    "type": "application/vnd.lime.contact+json",
    "resource": {
        "name": "Contact Name",
        "lastMessageDate": "2026-04-30T01:25:20.859Z",
        "lastUpdateDate": "2026-06-11T19:16:35.548Z",
        "identity": "4911ae5f-ba7d-464c-bd86-c5ed60f1aa8d@wa.gw.msging.net",
        "phoneNumber": "51991234567",
        "extras": {
            "field1": "value",
            "field2": "value2"
        },
       "whatsAppBsuid": "BR.123456789",
        "whatsAppWaId": 51991234567,
        "whatsAppUserName": "myContact",
        "whatsAppParentId": "BR.ENT.987654321"
    },
    "method": "get",
    "status": "success",
    "id": "27de23e8-2f6c-4ce3-9e34-0518c0ca2bd7",
    "from": "postmaster@crm.msging.net/#msging-application-crm-85f5c8bf8b-k5gmt",
    "to": "botname@msging.net/!msging-server-5f4c66d546-prf7k-s740zrjx",
    "metadata": {
        "traceparent": "00-ee3744050b891d7ee855eba6896276f6-4e4d38a6426bcb28-01",
        "#command.uri": "lime://botname@msging.net/contacts/4911ae5f-ba7d-464c-bd86-c5ed60f1aa8d@wa.gw.msging.net"
    }}

 

Contact Filters via API

Now you have more ways to find a customer. In the CRM search, you can search directly by Meta Identifier, Username, or WhatsApp ID, with only whatsAppBsuid able to be associated with other Contact properties in the search. This makes it easier to locate contacts even when the phone number is not available.

Example 1: Filter contact by a BSUID

POST https://{{contract_id}}.http.msging.net/commands HTTP/1.1
Content-Type: application/json
Authorization: Key {YOUR_TOKEN}
{  
  "id": "{{$guid}}",
  "to": "postmaster@crm.msging.net",
  "method": "get",
  "uri": "/contacts?$take=100&$filter=(whatsAppBsuid%20eq%20'BR.123456789')"
}

Example 2: Filter contact by a username

POST https://{{contract_id}}.http.msging.net/commands HTTP/1.1
Content-Type: application/json
Authorization: Key {YOUR_TOKEN}
{  
  "id": "{{$guid}}",
  "to": "postmaster@crm.msging.net",
  "method": "get",
  "uri": "/contacts?$take=100&$filter=(whatsAppUserName%20eq%20'myContact')"
}

Example 3: Filter contact by a waId

POST https://{{contract_id}}.http.msging.net/commands HTTP/1.1
Content-Type: application/json
Authorization: Key {YOUR_TOKEN}
{  
  "id": "{{$guid}}",
  "to": "postmaster@crm.msging.net",
  "method": "get",
  "uri": "/contacts?$take=20&$filter=(startswith(whatsAppWaId%2C'51991234'))%20and%20(source%20ne%20'blip.ai')%20and%20(lastmessagedate%20ge%20datetimeoffset'2026-01-02T03%3A00%3A00.000Z')%20%20and%20(lastmessagedate%20le%20datetimeoffset'2026-06-11T02%3A59%3A00.000Z')%20"
}


 

Need more help? Explore our content at Blip Academy or Blip Community, watch tutorials on our YouTube channel, or get your questions answered in our support channel 😃

Related articles