Better Contact Search (Secondary Details + Flexible Phone Formats + Case-Insensitive Matching)
S
Scott Heliker
Just noticing that the Search Contacts endpoint only looks at the main email and phone number on a contact. If you try searching by a secondary email or phone, it won’t return anything.
It would also be great if searches were case-insensitive and not limited to exact matches.
For example, searching for john@gmail.com or John@Gmail.com should return the same result.
This should apply across all searchable fields, not just email.
Right now, the phone search is also limited — it only works if the number is in E.164 format (for example, +13145557878).
The older endpoint
used to match all of these formats:
📱 +13145557878
📞 13145557878
☎️ 3145557878
📱 (314) 555-8888
📞 314-555-8888
But the new one
only works if it’s exactly like this:
📱 +13145557878
Would be awesome if the new search:
🔍 Included secondary emails and phone numbers
📱 Accepted any standard phone format
🧩 Supported a case-insensitive operator for all search fields
Log In
J
Jason Tonioli
The phone number search only allows left to right and it doesn't allow you to search a "contains" option for a phone. This has caused a lot of headaches for our support people who have been used to working in KEAP where they can type 4 digits of a phone number and have it pull all the matching "contains" number info.
M
Mark Edmunds
I echo Michael's comment - also upvote....!
M
Michael Herron
Upvote upvote upvote....this is a relatively quick fix and a huge benefit.