Summary
We are deprecating two fields, maxAllowedRestorationsForOrg and remainingRestorationsAllowedForOrg, from the API response of a few recording-related APIs. While we are not removing these fields from the API response to avoid significant breaking change, we will return a placeholder value of 10000 for these fields going forward.
Effective Date
Tuesday, August 5, 2025
Details
Previously there was a limit on the number of restored archive recordings for each organization. maxAllowedRestorationsForOrg was set to the value of the limit, and remainingRestorationsAllowedForOrg was used to track how many restorations remained for the organization. Since July 23, 2025, we are no longer enforcing the archival restoration limit to remove the need to open a ticket to increase the limit. As a result, these two fields are no longer in use.
Customer Impact
No action needed from the customer to avoid an outage. If the customer has anything that depends on the value of these fields, they should be aware that these two fields will only hold a large dummy value from now on. The field descriptions have been updated to reflect the change.
Impacted Resources
GET /api/v2/conversations/{conversationId}/recordingmetadata/{recordingId}
GET /api/v2/conversations/{conversationId}/recordingmetadata
GET /api/v2/conversations/{conversationId}/recordings/{recordingId}
PUT /api/v2/conversations/{conversationId}/recordings/{recordingId}
GET /api/v2/conversations/{conversationId}/recordings
Issue References
[REC-7526]
[REC-6922]
Contacts
@Yile Xie
Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.