Webhook Subscriptions Set Up By Users Who Have Left are Still Sending Data

Question

question

Addison Cahill asked Jul 24, '23 Phong Vu answered Jul 25, '23

Webhook Subscriptions Set Up By Users Who Have Left are Still Sending Data

Hello All,

Apologies for the verbose title but I wanted it to articulate my companies issue clearly. Here is what's happening:

Our company integrates with RC for many of our customers in order to obtain and track their telephony data. To accomplish this, we create webhook subscriptions for each account on behalf of a user from the account. The issue with this approach is that when that user leaves, a new user must authenticate with RC and thus, another subscription is created. The new webhook subscription itself is not the issue but rather, the old subscription which isn't deleted. Since the old subscription was made by a user we no longer track in our system, we cannot view or delete the old subscription via the RC API (https://platform.ringcentral.com/restapi/v1.0/subscription).

Is there a way for us to be able to view all webhook subscriptions for an account if we only have a specific users access token? If so, how can we delete the 'old' subscriptions? Perhaps there is a response we can return when the webhook sends us updates that would cancel the subscription - almost similar to getting our endpoint blacklisted except in this case, we would want the subscription to be deleted.

Please ask any clarifying questions needed and thanks in advance.

webhooks auth

1 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

Using the RingCentral Phone for Desktop, you can dial or receive test calls, send and receive test SMS or Fax messages in your sandbox environment.

Download RingCentral Phone for Desktop:

Tip: switch to the "sandbox mode" before logging in the app:

On MacOS: press "fn + command + f2" keys
On Windows: press "Ctrl + F2" keys

Answer 1 · 2023-07-25T15:22:04Z

Phong Vu answered Jul 25, '23

Unfortunately, right now we don't have a solution for this. We are considering to provide a capability for a super admin to mange subscriptions for other extension tthough.

For now, the first thing to do is to prevent this by deleting the current subscription (using the subscription owner access token) before creating a new subscription with a new user's access token.

For those orphaned subscriptions that send unexpected events, detect the subscription id from the events and submit a dev support ticket to ask the support team delete them for you.

1 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

question