Third-party developer guides, SDK examples, and legacy documentation cite specific endpoints or nested schema paths for call queue overflow settings (such as queue-to-queue overflow and overflow routing rules) that do not exist or return errors in the live REST API. We request updating the official RingCentral Developer API reference with an authoritative guide and schema specification for retrieving and managing call queue overflow settings programmatically.

Current Problem:
When building automated configuration auditing and reporting scripts across hundreds of call queues, developers encountering overflow settings in third-party guides find discrepancies against the live API. It is currently ambiguous in the documentation which endpoint, query parameters, feature entitlements, or schema objects officially support call queue overflow inspection.

Proposed Solution:
Update the Developer Guide and API reference for Call Queues and Answering Rules to clearly document the exact supported endpoint and JSON payload structure for call queue overflow settings, specify any required feature entitlements such as CallQueueToCallQueue, and clarify any deprecated or invalid paths referenced in external documentation.

Business Impact:
Accurate and clear documentation reduces development and troubleshooting time, prevents misconfigured API integration scripts, and provides clarity on how enterprise call queue overflow configurations can be audited via the API.