Jump to content

Webhooks- Call for Requests!


Recommended Posts

Richard,

We use webhooks as a temporary workaround until websockets are released. Here is some data we would like webhooks to pass that it currently does not:

- account_id (currently we just add this as custom data since it's static, but it would be nice not to have to worry about adding it in each time) / also, realm would suffice too if you'd rather do this instead of account_id...either or works for us

- call duration passed on channel_destroy events (we can calculate this on our end, but it's significantly increasing server load when we test it with a high volume of calls so we would really prefer if the data is just passed directly)

- device_id passed on all applicable devices (currently we have to use owner_id)


I would also like to see https support and some form of authentication support.
Link to comment
Share on other sites

We second everything Karl said, in particular the device_id which is how we track what device is doing what.
But we would also like to see channel_hold event for when a call gets put on hold.

And if possible, a channel_park event for when a call gets parked, and what slot it was parked to.
Link to comment
Share on other sites

Our use case is strange... http://getweave.com
Our desktop software shows each call and its status, along with the data from the CRM. So if a call gets put on hold, we reflect that in UI. For parking, we want them to be able to see the customer name in the park slot in our software and click it if they want to pick up that call. But real-time updating is essential.
Link to comment
Share on other sites

×
×
  • Create New...