Contacts API 2.0
complete
Z
Zy
complete
🎉 This was long-awaited — Our new-generation API has been released!
List of use cases:
- Create new Contacts and update existing Contacts
- Send a message to Contacts
- Assign or unassign conversations
And more! You can find more information here.
If you have any thoughts on the new API, please share them with us. Your feedback is always appreciated.
S
Shi Hui
in progress
Y
Yugeswaran Vasudevon
Contact API: Unable to assign agent to contact via API call
For now it’s not possible to modify the assignment field by contact api.
Would like to check if we can add field ID to “assignedto” to assign agents to contacts directly via API call?
Add contacts from Google sheets list to respond.io by calling Contact API and assign the agents listed in google sheet as well.
R
Riaan Le Roux
I am shocked to see that there is no option to remove contacts via the API. How are we supposed to manage and sync our CRM with Respond.io without the option of removing users?
Can this feature please be implemented asap?
I find it very strange that a platform this big, only gives you the option of searching for manually and deleting users one by one.
Alternatively, one could search for those needing to be removed and giving them a "DELETE" tag, but that is one big workaround that shouldn't have to be like that.
Until this feature is implemented, we'll have to start looking at an alternative solution to respond.io because this will prevent us from being able to run dainly syncronization between our CRM and Respond.io
Gerardo Salandra
Gerardo Salandra
under review
Gerardo Salandra
Merged in a post:
Api key by space - contacts and messages from all channels
T
Thibaut M
need an api key by space
The main objective is to be able to centralize all contacts from every channels (messenging apps, sms, emails...) and get all the messages.
The current api requires a token per channel which I feel complicate integrations and also failed the objective to centralize all.
I think we must be able to find a contact added to respond.io by custom field or id without specifying the channel,
then it return the contact information (id, custom fields...) and all subscribed channels with their id.
With those information and still the same unique api key we can send/read messages to the desired contact on the specified channel.
so the feature is to have api key(s) per space, and be able to fetch contacts and send/read messages of the specified channel
Gerardo Salandra
Hello Thibaut M, great feedback! This is definitely something we want to work on together with our Contact API 2.0 and Messages API 2.0 scheduled for later this year.
Gerardo Salandra
Load More
→