Good Afternoon,
We’ve been working through our updates to the API and have noted a few gaps, in terms of functionality within the v2 API. Having said that, it is encouraging to see some gaps on my list get implemented as time goes on (e.g. Complete Goal) hence I am hopeful that most use cases will be fulfilled well in advance of the sunset date.
There are some business critical gaps which we have which are yet to be addressed, hence I felt the need to put these forward to understand whether these are on the roadmap to be addressed or to determine what the alternative solution would be.
-
Retrieve Tags by DateCreated - we use tags for reporting (e.g. time between tags) and as such it is critically important to be able to retrieve the dates when a tag was applied.
Currently this can be efficiently performed via XMLRPC by retrieving tags with a DateCreated after a point in time to get a delta of newly tagged contacts.
Unfortunately the v2 API does not appear to provide the date that a tag was applied to the contact either via the GET /contacts endpoint or GET /tags/{tag_id}/contacts
In addition to this, both of these endpoints would require knowledge of the contactid or tagid to be able to retrieve the information, potentially resulting in 100s of API calls to determine which tags have been applied to which contacts since a certain point in time.
Hence is there any functionality in the /v2 API which can facilitate this, if not, is this currently on the roadmap?
-
Retrieve Contact by Custom Fields - one of our legacy systems currently uses one of our Keap instances to manage subscriptions via tags, with payment notifications for subscriptions coming via webhooks from payment providers (which have their own identifier for the contact which is currently stored in a custom field).
Hence in order to apply a tag, we currently are looking up the contact via the custom field to apply the tag.
Is there currently or is there going to be the ability to search contacts by custom field in the v2 API?
-
Custom Fields on Tasks - We currently use custom fields for storing metadata on tasks, a lot of which is written to the task via an API. The API docs however state that POST and PUT actions do not support custom fields, are there plans to support this as part of the v2 API and if so when is this likely to be available?
Regards,
James Austin