# REST V2 Gap - Quick Search **URL:** \ **Category:** API Q&A\ **Tags:** api\ **Created:** [May 3, 2026, 3:44am UTC](https://integration.keap.com/t/rest-v2-gap-quick-search/94040 "2026-05-03T03:44:01Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Dustin\_Lunt](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/dustin_lunt/32/15037_2.png) [@Dustin\_Lunt](https://integration.keap.com/u/Dustin_Lunt)\ **Post date:** [May 3, 2026, 3:44am UTC](https://integration.keap.com/t/rest-v2-gap-quick-search/94040/1 "2026-05-03T03:44:01Z")
Right now we can use the quick search to search for contacts, companies, orders opportunities, tasks, subscriptions and affiliates. For contacts it’s super helpful that you can send just a partial contact name to search to pull up a list of contacts starting with that name. Phone numbers also work better in the quick search. Right now unless you’re going to expand all the filters or search abilities to not force a equals for the searching right now you have to type the entire first name. Also on the phone fields searching this is another thing that is frustrating that we have to query the whole phone number and have it formatted however it might be inside Keap which could be many different ways. Why can’t we just pass the E.164 formatted number and on your end you query the potential formats? Mainly wondering if either the quick search is coming in V2 or search with wildcards is coming? ---
**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\ **Post date:** [May 5, 2026, 1:37pm UTC](https://integration.keap.com/t/rest-v2-gap-quick-search/94040/2 "2026-05-05T13:37:10Z")
Hi @Dustin_Lunt. Really appreciate you sharing this. I’ll make sure to bring this feedback up internally. We’re currently working on expanding filtering capabilities across most of our list endpoints, including adding support for more flexible options like wildcard filtering wherever it’s feasible. Your points about partial name matching and phone number normalization (like accepting E.164 format regardless of how it’s stored) are spot on, and I’ll make sure those are included in the conversation. I don’t have a specific timeline to share yet around a Quick Search V2, but this is something the team is looking into. ---
**Author:** ![Pav](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/pav/32/124_2.png) [@Pav](https://integration.keap.com/u/Pav)\ **Post date:** [May 6, 2026, 3:15pm UTC](https://integration.keap.com/t/rest-v2-gap-quick-search/94040/3 "2026-05-06T15:15:36Z")
@Dustin_Lunt, for your reference. > [@Searching for Contacts via any phone # using API](https://integration.keap.com/t/searching-for-contacts-via-any-phone-using-api/93887/13): > > I have been using the Keap MCP to test what is actually available via the REST v2. It exposes the deficiencies which I hope Thryv will fix. If you want to try the Keap MCP, this is the URL: [https://api.keap.com/mcp](https://api.keap.com/mcp) Just now, I tried to search for my own phone number in Claude via the MCP and got this. > [@REST v2 - List Contacts - Lack of Wildcard Support](https://integration.keap.com/t/rest-v2-list-contacts-lack-of-wildcard-support/94035): > > @OmarAlmonte, I understand that there is no wildcard support with these endpoints, is this decision going to change in the future? In a piece of code that I have got written for the XMl-RPC API, it allows me to do wildcard searches on a name which is helpful to track down contacts. Migrating it to REST v2 does not allow me to do any wildcard searches, which now limits the search results. What do we do now? Just to add you are implementing the Filter By Phone under Issue #2. Not sure how you… The planned wildcard pattern will not be the same as XML-RPC.