Reference · built on requestConnectorVoice & contact center

RingCentral

Call log, presence, telephony session events, recordings, and call analytics from the RingCentral REST API.

Request RingCentralAsk about this listing

About

RingCentral is a cloud phone, message, and video platform. Its REST API is organized as Voice, SMS, Team Messaging, Video, Fax, Data, and Analytics APIs. You register an app in the Developer Console to get a Client ID and Client Secret, then authenticate a server app with the JWT flow or a user-facing app with the OAuth authorization code flow. Webhook and WebSocket subscriptions push presence, telephony session, and message store events.

Through Fibric, an operator reads the call log and presence, listens for telephony session events, and proposes a RingOut call or a text. You approve; it runs once; the receipt shows what changed and why.

This is a reference listing. It documents what Fibric would read from RingCentral and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

What it reads

  • Account and extension call log records through /restapi/v1.0/account/{accountId}/call-log, with the ReadCallLog permission
  • Extension presence, including detailedTelephonyState, and Account and Extension Telephony Sessions events over a subscription
  • Message store events for SMS received, voicemail received, and fax received
  • Call recordings by contentUri on media.ringcentral.com, fetched with the access token
  • Calls in progress through the Active Call API, which RingCentral offers instead of polling the call log
  • Call Business Analytics Aggregate and Timeline APIs: origin, direction, answered or unanswered, setup, ringing, IVR, talk, and hold time back 184 days

Proposed actions

  • Target capability: propose a RingOut call through POST /restapi/v1.0/account/~/extension/~/ring-out with from, to, and callerId
  • Target capability: propose a text message through the SMS API
  • Target capability: propose a webhook subscription through POST /restapi/v1.0/subscription with the eventFilters an operator needs

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Return a missed call

    A telephony session that ends unanswered is a call owed. The operator drafts a RingOut from the extension's number and holds it for the owner to approve.

    With Callback Promise

  • Summarize a recorded call

    After the call log shows a recording, the operator fetches it by contentUri, drafts a summary, and proposes it as a note in the system you choose.

    With Call Summary

  • Find what people call about

    Aggregate analytics by direction, answered or unanswered, and hold time set the weekly baseline. The operator proposes the drivers with the query it ran.

    With Contact Drivers

  • Answer an unanswered inbound within the hour

    Message store events for voicemail and SMS received open a clock. The operator proposes a first reply or a return call before it expires.

    With First Response

What it needs

  • A RingCentral account and an app created in the Developer Console with the scopes it needs; some sensitive scopes require a justification
  • The ReadCallLog and ReadPresence permissions for call log and presence reads
  • A public HTTPS endpoint that answers the Validation-Token test within 3000 milliseconds and under 1024 bytes
  • The Call Control app scope, added by RingCentral developer support, before any telephony session control
Authentication
An app registered in the RingCentral Developer Console with a Client ID and Client Secret, using the JWT flow for a service user or the OAuth authorization code flow for individual users.

Limits

  • Rate limits run per user per minute by group: Light 50, Medium 40, Heavy 10, Auth 5; a 429 carries Retry-After and a 60-second penalty
  • The Call Log API is in the Heavy group, long-polling it is unsupported, and a completed call takes 15 to 30 seconds to appear
  • RingCentral does not store call log data indefinitely; archive records you need to keep
  • This listing covers the phone, SMS, and analytics REST API; RingCX contact center data is outside its scope

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request RingCentral

Questions and answers

How do subscriptions work?
POST to /restapi/v1.0/subscription with eventFilters such as /restapi/v1.0/account/~/extension/~/presence?detailedTelephonyState=true and a deliveryMode of WebHook with your address. RingCentral sends a validation test you answer within 3000 milliseconds. Renew with PUT or POST /subscription/{id}/renew. WebSocket transport is also available.
How are RingCentral rate limits grouped?
Each endpoint belongs to a usage plan group. Defaults are Light 50, Medium 40, Heavy 10, and Auth 5 requests per user per minute. A 429 returns Retry-After in seconds, and sending during the penalty interval restarts it. Headers X-Rate-Limit-Group, X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Window report the state.
Which auth flow should a server use?
JWT. RingCentral describes it as suited to a single service user, typically an admin, for apps without a user interface. Apps acting for many individual users use the authorization code flow, with PKCE and refresh tokens to keep sessions alive.
Ask about RingCentral

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with RingCentral through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy