opschain admin jsm-connections show

integrations:jira-service-management

Shows one JSM connection: site base URL, authentication shape (basic with the account email, or a Data Center bearer PAT), the pinned api_token_ref (an address — never token material), project scope, the provisioned webhook link and health.

opschain admin jsm-connections show limepoint-jsm
Code:          limepoint-jsm
Base URL:      https://limepoint.atlassian.net
Auth:          basic (support-bot@limepoint.example)
API token ref: secret-vault://jsm-connections/limepoint-jsm/credential
Projects:      SUP
Webhook:       jsm-limepoint-jsm (/api/hooks/jsm-limepoint-jsm)
Enabled:       true
Health:        ok

Flags

Flag	Meaning
--server <url>	Server base URL (default: the active context / OPSCHAIN_SERVER).
--auth-token <token>	Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login).

See also

• opschain docs cli/admin-jsm-connections-test — recording the record's health.