Twilio Voice Conference API Improvements

Starting from September 9, 2019, customers may see some minor behavioral changes with the Twilio Voice Conference REST APIs. As part of an initiative to improve performance and fix bugs, we have discovered some corner cases where the behavior of the Conference REST APIs was either undefined or erroneous. These issues have been resolved and the correct behavior is now documented below.

Read multiple Conference resources

The changes are as follows:

  • The returned list is now sorted by dateCreated. Previously, it was sorted by dateUpdated. For help viewing long lists, see REST API: Twilio's Response - Paging Information.
  • Filter parameters dateCreated and dateUpdated should be in this format:
        YYYY-MM-DD, <=YYYY-MM-DD, >=YYYY-MM-DD

Notice: We do not support the ISO8601 date-time format, e.g. 2019-09-06T03:59:31-0400.  A request using this format will now return 400 Bad Request.

For full details, see Conference Resource: Read Multiple Conference Resources (Twilio Docs).

Fetch a Conference Participant resource

The changes are as follows:

  • The Status field returned is now populated with the correct status value. Previously, it always returned as null.

For full details, see Conference Participant Resource: Fetch a participant (Twilio Docs)

Read multiple Conference Participant resources

The changes are as follows:

  • The returned list is now sorted by dateCreated. Previously, it was sorted by dateUpdated. For help viewing long lists, see REST API: Twilio's Response - Paging Information.
  • The Status field returned is now populated with the correct status value. Previously, it always returned as null.

For full details, see Conference Participant Resource: Read multiple participant resources (Twilio Docs)

Update a Conference Participant Resource

The following section clarifies the responses and error codes received when updating Conference Participant Resource fields via this API. The following are the parameters in question:

Parameters Description
Muted Participant is muted or unmuted
Hold, HoldUrl, HoldMethod Participant is put on hold or unhold
AnnounceUrl, AnnounceMethod To make an announcement to a participant
Coaching, CallSidToCoach Participant is coaching another Call SID

Previously, you could change any combination of these values and receive a 200 OK response. This was misleading, however, as some of these combinations did not work together or resulted in race conditions, producing inconsistent results. We have addressed these issues, and formalized how the REST API responds to incompatible combinations. Below are the responses the API will return going forward with these parameters in POST requests:

hold coach announce New Response Previous Response
    X 200 OK 200 OK
  X   200 OK 200 OK
X     200 OK 200 OK
X X   200 OK 200 OK
  X X 400 - Can’t announce
to a coach
(Error 16002)
200 OK
X   X 400 - Can’t announce
to a participant on
hold
 (Error 16002)
200 OK
X X X 400 - Can’t announce
to a coach
(Error 16002)
200 OK

The following are Error Code changes:

Scenario New Response Previous Response
Participant no longer in-progress 404 - Not Found
(Error 20404)
400 Bad Request
(Error 20001)
Participant never existed 404 - Not Found
(Error 20404)
404 - Not Found
(Error 20404)

For full details, see Conference Participant Resource: Update a participant resource (Twilio Docs)

Additional Resources

Have more questions? Submit a request
Powered by Zendesk