canonical: https://jentic.com/apis/ringcentral.com/ringcentral

# RingCentral API

RingCentral API specification. The API exposes 487 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically create webinar subscription, list webinar subscriptions. Covers 487 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create Webinar Subscription
- List Webinar Subscriptions
- Get Webinar Subscription
- Update Webinar Subscription
- Cancel Webinar Subscription
- Renew Webinar Subscription

## Use cases

### Developer Tools Operations

Use the RingCentral API to perform developer tools operations programmatically. The API provides 487 endpoints covering core functionality including create webinar subscription, list webinar subscriptions, get webinar subscription.

Example prompt: Call POST `/webinar/notifications/v1/subscriptions` to create webinar subscription

### Automated Registration Management Management

Automate registration management operations by combining multiple RingCentral API endpoints. Agents can list webinar subscriptions and then get webinar subscription in a single workflow.

Example prompt: Call GET `/webinar/notifications/v1/subscriptions` to list webinar subscriptions, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call RingCentral API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'create webinar subscription', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/webinar/notifications/v1/subscriptions` | Create Webinar Subscription |
| GET | `/webinar/notifications/v1/subscriptions` | List Webinar Subscriptions |
| GET | `/webinar/notifications/v1/subscriptions/{subscriptionId}` | Get Webinar Subscription |
| PUT | `/webinar/notifications/v1/subscriptions/{subscriptionId}` | Update Webinar Subscription |
| DELETE | `/webinar/notifications/v1/subscriptions/{subscriptionId}` | Cancel Webinar Subscription |
| POST | `/webinar/notifications/v1/subscriptions/{subscriptionId}/renew` | Renew Webinar Subscription |
| GET | `/webinar/history/v1/webinars/{webinarId}` | Get Historical Webinar |
| GET | `/webinar/history/v1/webinars/{webinarId}/sessions/{sessionId}` | Get Historical Webinar Session |

## Key resources

- **Registration Management** — External APIs for registration flow management
- **Message Exports** — External interface to export user's messages
- **Message Store** — Operations related to Message Store
- **Call Forwarding** — Operations related to Call Forwarding
- **Device SIP Registration** — Operations related to Device SIP Registration

## Why Jentic

- **Setup:** Wiring the RingCentral API by hand means running its OAuth 2.0 authorization-code flow, refreshing access tokens, and picking the right platform or media host across production and sandbox. Through Jentic you install once, import the RingCentral API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** RingCentral puts the resource id in the URL path (`/webinar/notifications/v1/subscriptions/{subscriptionId}`), so a rule can pin your agent to one subscription: it can read and renew that subscription and nothing else. You choose the operations it may call, so destructive ones like deleting a subscription are not included unless you add them.
- **Credential handling:** Your RingCentral OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'subscribe to webinar notifications' or 'get webinar session history', and Jentic returns the matching RingCentral API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the RingCentral API use?

The RingCentral API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create webinar subscription with the RingCentral API?

Yes. Use the POST `/webinar/notifications/v1/subscriptions` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the RingCentral API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create webinar subscription through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create webinar subscription'. Jentic returns the matching RingCentral API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the RingCentral API have?

The RingCentral API exposes 487 endpoints covering registration management, message exports, message store operations.

### Can I limit what my agent is allowed to do with the RingCentral API?

Yes. Because you run Jentic One yourself, your own rules decide which RingCentral operations and credentials the agent may use. Since RingCentral puts the resource id in the URL path, such as `/webinar/notifications/v1/subscriptions/{subscriptionId}`, a rule can pin the agent to a single subscription so it can read and renew that one and nothing else. You choose the operations it may call, so a destructive request like DELETE `/webinar/notifications/v1/subscriptions/{subscriptionId}` to cancel a subscription is excluded unless you add it.