API3
flint at January 16th, 2015 13:49 — #1
In the documentation I see a way to return a contact based on email, url, name, and company but not by phone. It's also not possible to create a filter on the phone field. Is there a way to return all contacts with a certain phone number?
pete_onepagecrm at January 20th, 2015 04:01 — #2
Hi @flint, sorry for the delay in replying.
At the moment, you can't filter by contacts by phone using the API.
We can look at adding this filter to the API if you really need it for your integration.
Can you tell us a bit more about the feature you have planned so we can come up with the best way for it to work.
Thanks, Peter
flint at January 20th, 2015 10:35 — #3
@Pete_OnePageCRM
Before adding a new customer/Contact we do a check for duplicate fields (email, domain, phone#). I think phone-search would be a solid addition to your api since Custom Filters seem to cover all fields (including custom fields) except phone.
In the mean time I may have to create a custom field for phone so I can search by it. When the default Phone field is changed from within the web-app, the webhook would then update the custom phone field. This may work as a temporary fix, but it becomes more complicated when our contacts have multiple phone numbers.
Thanks for the reply
pete_onepagecrm at January 20th, 2015 11:35 — #4
Hi @flint, sounds like a solid use case and I can't see any reason why we enable search by emails and not by phones.
I'll take a look and try to sneak it into the development plan.
I'll update you with any progress.
flint at January 20th, 2015 11:49 — #5
Thanks @Pete_OnePageCRM, I'm sure many future users will appreciate it as well.
pete_onepagecrm at May 28th, 2015 09:36 — #6
Hi @flint we recently updated the API with the option to search by phone. The feature is still in beta, so you won't find it in the api docs yet.
Try a call to api/v3/contacts.json?phone=123
to check it out.
I'd really appreciate your feedback on this feature, and if everything is working ok after beta testing, I'll soon add it to the documentation.
Powered by Discourse, best viewed with JavaScript enabled