RingCentral

RingCentral

RingCentral organizes telephony under Account and Extension (user/line). Company-level settings (queues, business hours) and extension-level settings (forwarding, call blocking) are separate.

Operational order

1. Account extensions — read extensions for the account (use ~ for the authenticated account) and take each row's id before any extension-scoped call.
2. Company-level reads — call queues, monitoring groups, business hours, call handling rules, call recording settings.
3. Extension-scoped reads — forwarding numbers, caller blocking, business hours, active calls, call history per extension.
4. Writes — only after confirming the target extension or queue id from a read. Extensions, forwarding numbers, blocked numbers, business hours, call queues, and handling rules support create/update/delete where noted in tool copy; dictionary assets (fax cover, IVR prompts), monitoring groups, and active calls are read-only upstream.

Data model

• Account — organization; contains extensions and company settings.
• Extension — user or phone line; has call handling, forwarding, business hours.
• Call Queues — hunt groups for incoming calls.
• Call Monitoring Groups — supervisor groups for monitoring agents (read-only).
• Business Hours — when calls are routed; company and per-extension.
• Call Handling Rules — routing rules (forward, voicemail, etc.).
• Blocked/Allowed Numbers — per-extension allow/deny lists.
• Call Records — call history and CDR data.
• IVR Prompts — auto-attendant audio from the dictionary (list-only).
• Fax Cover — fax cover page templates from the dictionary (list-only).

Tool shape

Reads collapse list and single fetch: omit resource ids to page, pass ids from prior rows for one record. Dictionary reads paginate only. Writes use upsert semantics (omit id to create, pass id to update) and explicit delete tools for destructive removes.

Gotchas

• Read extensions before extension-scoped calls: The REST id is not the dialable extension number.
• Default extension: Omit extension_id (or pass ~) to use the authenticated user's own extension on call-log and related tools.
• Never pass extensionNumber: Values like 101 or 46 are dialable numbers, not REST ids — read account extensions and use each row's id.
• account_id and extension_id: Most operations need account_id; extension-scoped reads also accept extension_id. Use ~ for the authenticated account or extension when appropriate.
• REST app permissions: Call queues need ReadAccounts; per-extension call logs need ReadCallLog. Writes need the matching edit scopes on the private REST app (for example extension settings, call handling, or queue admin).