Events

6min

consented
consentRedirect
notConsented
revoked
integrations
consented
The event fires immediately after your user successfully authorizes with an Integration provider
 Example
JS
Tcl
|
$(document).ready(()=>{
	$pinc.events.on("$pinc.oauth","consented",(data)=>{console.log(data)},true);
})

    
$(document).ready(()=>{
	$pinc.events.on("$pinc.oauth","consented",(data)=>{console.log(data)},true);
})

    
﻿
Handler Arguments
JS
|
{    
    provider:"providername"
}

{    
    provider:"providername"
}
﻿
notConsented
The event fires if the user starts the OAuth authorization process but does not complete the authorization successfully or closes the window midway.
Example
JS
|
$(document).ready((){
		$pinc.events.on("$pinc.oauth","notConsented",(data)=>{console.log(data)},true);
	})
    

$(document).ready((){
		$pinc.events.on("$pinc.oauth","notConsented",(data)=>{console.log(data)},true);
	})
    
﻿
Handler Arguments
JS
|
{    
    provider:"providername"
}

{    
    provider:"providername"
}
﻿
integrations
The event fires after configurations are loaded and the $pinc.oauth component is ready to work with.

Updated 03 Mar 2023

Did this page help you?

TABLE OF CONTENTS

consented

notConsented

integrations