Skip to content
Was this article helpful?


Statistics for sc.


(click to see Operations)

NameData TypePermissionsDescription
clearstats<String>Read-writeClear the statsistics / counters.
Possible values = basic, full
sctotcondtriggered<Double>Read-onlyNumber of times that SureConnect conditions were triggered.
sccondtriggeredrate<Double>Read-onlyRate (/s) counter for sctotcondtriggered
scpolicyurlhits<Double>Read-onlyTotal number of incoming requests that matched configured sureconnect policies.
scpolicyurlhitsrate<Double>Read-onlyRate (/s) counter for scpolicyurlhits
scpopups<Double>Read-onlyTotal number of in-memory java script served which throws the pop-up window.
scpopupsrate<Double>Read-onlyRate (/s) counter for scpopups
sctotreissuedrequests<Double>Read-onlyTotal number of reissued SureConnect requests.
screissuedrequestsrate<Double>Read-onlyRate (/s) counter for sctotreissuedrequests
scsessionreqs<Double>Read-onlyTotal number of requests that were handled in a single SureConnect session.
scsessionreqsrate<Double>Read-onlyRate (/s) counter for scsessionreqs
scaltconturls<Double>Read-onlyTotal number of alternate content served which throws the pop-up window.
scaltconturlsrate<Double>Read-onlyRate (/s) counter for scaltconturls
scpostreqs<Double>Read-onlyTotal number of HTTP POST requests that triggered SureConnect feature.
scpostreqsrate<Double>Read-onlyRate (/s) counter for scpostreqs
scresetstats<Double>Read-onlyToal number of times that SureConnect statistics were reset.
scresetstatsrate<Double>Read-onlyRate (/s) counter for scresetstats
scunsupbrow<Double>Read-onlyTotal number of requests that came from all unsupported browsers.
scunsupbrowrate<Double>Read-onlyRate (/s) counter for scunsupbrow
scfaultycookies<Double>Read-onlyTotal number of corrupted SureConnect cookies.
scfaultycookiesrate<Double>Read-onlyRate (/s) counter for scfaultycookies


(click to see Properties)


Some options that you can use for each operations:

  • Getting warnings in response:NITRO allows you to get warnings in an operation by specifying the "warning" query parameter as "yes". For example, to get warnings while connecting to the Citrix ADC appliance, the URL is as follows:


    If any, the warnings are displayed in the response payload with the HTTP code "209 X-NITRO-WARNING".

  • Authenticated access for individual NITRO operations:NITRO allows you to logon to the Citrix ADC appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,

    To do this, you must specify the username and password in the request header of the NITRO request as follows:



    Note:In such cases, make sure that the request header DOES not include the following:



Mandatory parameters are marked in redand placeholder content is marked in <green>.

get (all)





Use this query-parameter to get sc resources based on additional properties.


Request Headers:

Cookie:NITRO_AUTH_TOKEN=<tokenvalue> Accept:application/json


HTTP Status Code on Success: 200 OK HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for Citrix ADC specific errors). The response payload provides details of the errorResponse Headers:


Response Payload:

{ "sc": [ {
Was this article helpful?