Skip to main content
Solved

Key Meaning in Notification Add-in WEBHOOK_URL JWT


Hi all,

We are testing out the Notification Add-in type. Within RingCentral Developers, we can install to team to get a preview of what the {{ WEBHOOK_URL }} looks like.
The last URI path is a JWT, and it decodes to be

{
  "ot": "c",
  "oi": "<numericString>,
  "id": "<numericString>
}

May I please ask what each JSON key-value pair represents? Thank you

Best answer by Embbnux1109171020

Hi @Joe Lam I don't think that you need to decode the JWT string. The JWT is different for every user/chat team/installation. Every user with permission can add same add-in installation into a team multiple times.
You can use full string to identify if current is new installation or editing old installation. When user setup old installation, the RingCentral app will send same JWT string to your app

1681177179344.png

View original
Did this thread help you find an answer to your question?

3 replies

PhongVu
Community Manager
Forum|alt.badge.img
  • Community Manager
  • 2331 replies
  • April 10, 2023

Sorry but I don't understand your question. Can you refer to the source of information you get the JSON object from? And what is the JWT related to this?


Hi @Joe Lam I don't think that you need to decode the JWT string. The JWT is different for every user/chat team/installation. Every user with permission can add same add-in installation into a team multiple times.
You can use full string to identify if current is new installation or editing old installation. When user setup old installation, the RingCentral app will send same JWT string to your app

1681177179344.png


  • Author
  • New Participant
  • 1 reply
  • April 13, 2023

Thank you.

This helped us understand the scope of `{{ WEBHOOK_URL }}`

> JWT is different for every user/chat team/installation. Every user with permission can add same add-in installation into a team multiple times


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings