@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 your team have implemented that solution, because their is no consistent format on how phone numbers are stored. Something similar could be done for Names as well.
And no, a Saved Search will not help here, because the query needs to be modified.
@Pav, wildcard filtering for Contacts will be supported, but only for prefix-based searches.
This is being tracked in item #8 and is currently in the testing phase. The idea is to allow patterns like foo* , meaning prefix matching only (not full wildcard support like in XML-RPC).
Regarding phone numbers, that’s already implemented and the documentation has been updated to reflect the changes: Keap REST API
@OmarAlmonte, will the wildcard filtering going to be supported for other endpoints as well?
In a piece of code that i have got it is doing a search for tag names with a prefix and “%” symbol after it to give me a list. Migrating this to REST means I would have to search through all the tags to find the particular names, which will consume more API calls.
I see item #38 covers Tags, but what about the other List endpoints?
@Pav Wildcard filtering will be considered across all the items in the tracker that refer to extending filtering capabilities, not just the Tags endpoint. That said, this doesn’t guarantee it will be implemented everywhere, it means the team will review and evaluate it as part of those items.