Below are a number of examples to help you decide when and how to use them.
I'm using a 3rd party live chat system and want to add Upscope co-browsing so agents can co-browse with users while chatting
Upscope has a number of integrations with popular live chat products like Intercom, LiveChatinc, Drift and more.
I want to integrate Upscope into our support platform so my support agents can co-browse with customers
Upscope('getWatchLink', cb);) and place that link on your interface. Each link is uniquely generated for each user's screen.
The co-browsing link would take them to Upscope so your support agents would still, in this case, need to have an Upscope login account. If you don't want them to have to sign up to Upscope and wish to manage all support agents within your own app, you'd use the REST API. Typically, companies do this when they have a large number of support agents.
I'm working on a SaaS software where each of my clients have their own support agents who wish to use co-browsing.
I have a live chat solution and I'd like to offer co-browsing to the 1000s of companies using our services
When you're the provider of a software service which companies purchase for their own support agents and you want to add co-browsing as one of your features, you'd need to use the REST API.
Typically, companies fully whitelabel Upscope co-browsing into their platforms by placing the cobrowsing screen itself into an iframe.
Add a co-browse button to your software
Once the support agent clicks the co-browsing button, they see the user's screen in an iframe, within their interface.